01 / The operating case
What changes in a real workflow?
A parent splits one $20,000 invoice-release task among four children.
- 01Authority origin
- 02Task and grant
- 03Current decision
- 04Observed outcome
02 / Decision contract
What the executor must check
Assign per-child task and target, cap delegation depth, reserve against one aggregate budget and make revocation reach all branches.
InputPrincipal · task · action · target
DecisionGrant ancestry · policy · current state
ResultEnforce · record · verify outcome
03 / Failure and evidence
What goes wrong, and what can be proven?
Failure mode
Each child inherits the full parent budget and collectively spends four times the limit.
Evidence to retain
Keep child edges, fan-out count, reservations, approvals and payment effects.
04 / Canonical scope
Why this reference stands alone
Shared budgets owns atomic accounting; this page owns permission distribution to parallel children.
Illustrative implementation artifact
Fan-out scope partition
parent: read invoices I-1..I-4; budget 20k
child A: read I-1,I-2; no further delegation
child B: read I-3,I-4; no further delegation
all payment release: DENY unless separate grantPrimary references