06 · Delegated authority
Alice’s Agent: Authority by Mandate
Alice and Bob share a Counter Agreement. Alice’s Agent is visible from the beginning but cannot act. Alice creates a separate Mandate, Bob activates it, and the Agent gains only the exact increment operation Alice granted.
The authority graph
Being present is not permission.
The Agent can inspect the Agreement but has no direct owner channel. Its authority comes from a separate Operation Mandate whose actor, target document, operation, exact request, guarantor, and lifecycle state must all match at action time.
Without an eligible active Mandate, no delegated Timeline Entry is appended. A near-match does not become authority by interpretation.
Alice + Bob Counter Agreement
▲ exact target and operation
│
Alice ── creates Operation Mandate
Bob ───── activates as guarantor
│
▼
Alice’s Agent may request increment(+3)
Pending → blocked
Active → exact +3 allowed
Mismatch → blocked
Terminated → blockedRun it
Watch authority change through time.
The Guide deliberately includes denied attempts before, during, and after the grant so the boundary is visible rather than merely asserted.
What this teaches
Authority is exact, attributed, and time-dependent.
The evidence answers not only “was this operation allowed?” but “which living authority revision allowed this actor to make this exact request at that moment?”
Safe Retry shows how atomic admission and durable idempotency prevent one action from taking effect twice.