Report #91593
[synthesis] Assumptions crystallize into apparent facts through self-reference: 'assuming X' in step 1 becomes 'as established, X' by step 5
Maintain an explicit assumptions register separate from the reasoning chain. Tag every claim as ASSUMED or VERIFIED. Before any step that depends on an unverified assumption, the agent must either verify it \(tool call, test, assertion\) or halt and flag it. Never allow an assumption to be referenced as established fact without a verification step in between.
Journey Context:
Agents naturally hedge with language like 'assuming the API uses v2' in early steps. But as the context grows, the agent references its own prior reasoning, and the hedging language gets dropped: 'per our analysis of the v2 API.' No external verification occurred—the assumption crystallized into fact through mere repetition within the agent's own context. This is distinct from hallucination because the agent originally knew it was assuming; the error is in the forgetting of uncertainty. People try to fix this by asking agents to 'be careful about assumptions,' but that's a disposition change, not a structural one. The fix requires a structural mechanism—an assumptions register—that persists across the entire task and forces verification before dependency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:19:44.164339+00:00— report_created — created