Skip to main content

Structured outputs, evidence and freshness

Home · Structured outputs, evidence and freshness

Structured output example

Annotated structured-output review flow: summary, decisions, evidence, freshness, confidence, missing information and downstream actions

Goal

This page explains how to review an agent structured output before using it in a decision, PM Document, publication or governed action.

Read a structured output

  1. Read the Summary.
  2. Read Findings and Decisions.
  3. Open Evidence and citations.
  4. Check Source freshness.
  5. Read Confidence and Missing information.
  6. Decide whether the output stays exploratory, becomes a PM Document or needs escalation.

Decision table

SituationRiskRecommended decision
No evidenceResult cannot be justifiedDo not publish; add context or source
stale sourceSource is too oldRefresh, reimport or confirm manually
conflicting sourceSources disagreeHuman arbitration required
unavailable sourceEvidence could not be retrievedTreat as an alert, not a proof
Low confidenceResult is uncertainKeep exploratory or request review
External action proposedImpact outside ProPM AgentUse Actions and approvals
Shareable deliverableVersioning and governance neededOpen PM Documents and artifacts

Human review

AI outputs require human review before publication, sponsor decision, external communication, customer notification, ticket creation or governed action. Confidence is not approval.

Downstream flow

The recommended flow is run → structured output → artifact → version → PM Document → Download / Publish / Add to knowledge.

Support and audit IDs

Fields such as Trace ID, Structured output ID and Context snapshot ID are useful for support and audit. They do not replace business evidence review. Use AI Log and Support diagnostics for investigations.