These synthetic packs show how the Authority / Evidence / Effect / Recovery model changes with the action class. They demonstrate method structure, not customer results.
All three cases are designed worked examples. No customer environment, production execution, private data or external audit result is represented. Each pack keeps assumptions, expected gates and NOT TESTED states explicit.
The invariant method stays fixed while object binding, evidence gates, confirmation and recovery become specific to the external effect.
Update two fields on one matched staging lead.
Internal success without trusted same-object read-back.
False Green / external-effect confirmation gap
Send one approved message to one resolved recipient.
Recipient or approval evidence diverges before send.
Authority mismatch / recipient-binding gap
Change one approved staging configuration key.
Version or environment binding is ambiguous at execution.
Version-context / environment-binding gap
The local Authority Mapper supports CRM/record writes, outbound messages, deployment/config changes and custom external effects. It generates a draft Authority Ledger, Evidence Contract, action-specific failure scenarios and an owner decision posture.
The permission must name the action, target object or environment and the owner of that authority.
Identity, approval, freshness and version context are decision gates, not post-hoc explanations.
A tool acknowledgement alone does not prove the intended external state exists.
Unknown recipient, object, environment, version or external state routes to constrain, reconcile or repair.
A code/config change is not closure; the original decision condition must be replayed.
Primary ambiguity: did the intended record actually reach the intended state?
Primary ambiguity: was the exact approved content sent to the exact authorized recipient?
Primary ambiguity: did the approved change land in the intended environment against the expected baseline?
Map the action first. If the gates remain unresolved, the diagnostic and intake turn those gaps into an audit-ready scope without treating uncertainty as a pass.