01 / The operating case
What changes in a real workflow?
An account is disabled after several agents exchange a ticket and a tool call times out.
- 01Origin grant
- 02Parent agent
- 03Narrow child grant
- 04Action boundary
02 / Decision boundary
Put the check where it can stop the effect.
Join task creation, delegation edges, approvals, action decisions and executor records by stable IDs; preserve unknown outcomes.
03 / Failure and evidence
What goes wrong, and what can be proven?
A plausible text transcript is treated as proof of what was authorized or executed.
Origin grant, chain, policy version, approvals, attempted effect and independently observed account state.
04 / Canonical scope
Why this reference stands alone
Delegation receipts describe one edge; reconstruction joins the full chain after an incident.
Technical artifact
Timeline joins authority and effect
t0 U7 creates task T t1 A delegates to B, receipt R2 t2 B requests account.disable, decision D=ALLOW t3 executor timeout, outcome UNKNOWN t4 account state observed disabled incident conclusion uses t4, not D alone
Run the denial test
Drop the executor response after a successful account change. Reconstruction must preserve UNKNOWN until an independent state check and avoid claiming a failed operation.
Primary references