Uncertainty can disappear when one agent summarises another’s output. Preserve whether a statement is observed, caller-reported, inferred, disputed, or unresolved instead of compressing every claim into a confident sentence.
Summary chains can strengthen claims accidentally
An uncertainty-preserving summary carries both useful facts and their evidence status. Repeated summarisation can omit qualifiers, lose attribution, and turn a recommendation into a decision even when no agent intentionally invents a fact.
For a proposed claim record, include source reference, assertion, verification category, relevant version, and unresolved question. Confidence numbers alone are insufficient when they do not explain what is known or why.
Do not assume every hedge is important. Preserve qualifiers that change authority, commitment, or the next action. Remove unnecessary verbosity without changing the operational meaning.
Trace a fictional complaint through three agents
The caller says a technician never arrived. The intake agent records “caller reports missed visit; dispatch status not verified.” A summariser writes “missed appointment,” and a planning agent proposes compensation as if fault were established.
The evaluation should identify the first unsupported upgrade. The final agent needs the original attribution and uncertainty to recommend staff review rather than present compensation as approved. No amount of polished wording repairs the missing evidence boundary.
| Source status | Required summary meaning |
|---|---|
| Caller-reported allegation | Keep the attribution |
| Tool outcome unknown | Do not call the action failed or completed |
| Proposed remedy | Do not call it approved |
| Conflicting sources | Preserve the unresolved conflict |
| Verified completed action | Include authoritative result reference |
Build a fixture that passes the same packet through several summary stages. Compare consequential claims at every hop, not only the final prose, so the mechanism is diagnosable.
Keep source evidence accessible
A compact summary can link to controlled source spans for authorised review. If the source expires or access is denied, show that limit rather than silently treating the last summary as primary evidence.
More structured qualifiers increase message size and schema work. Focus on claims that affect decisions, permissions, or customer promises. Human review can calibrate whether a shorter formulation preserves the intended meaning in the workflow’s language.
This summary contract is proposed. The voice platform case study describes relevant retrieval and workflow work. Pair it with call-summary evaluation.
Uncertainty summary FAQ
Is a numerical confidence score enough?
No. Preserve evidence source, verification category, and unresolved conditions that change the decision.
Can a later agent remove qualifiers for brevity?
Only when doing so preserves the actual meaning and authority boundary.
What should a test inspect?
Track unsupported upgrades, missing attribution, lost corrections, and recommendations presented as completed actions at each handoff.