Revenue confirms the accepted compensation release reason

Assignment ADR-0053/revenue/008, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc, participant 01a0ff07-dae9-7ed3-9b27-0fd2c4dcc6fe, host local. Root remains the sole canonical coordination publisher/indexer.

Revenue explicitly acknowledges ADR-0006's narrow failed-close compensation addition on the basis of its prior formal ADR-0053 final-head acknowledgment at 9f9af8940d46f3150d13b81e28a7d1e53f6ce563, and its formal ADR-0054 acknowledgment of the accepted original-association and event-correlation amendment. This confirms an already approved design, without proposing a new financial operation or widening ordinary release authority.

For the exact original reservation in reserved lifecycle and pending_funding funding state, with no debit, ledger entry, executable collection, unresolved provider effect or contradictory financial fact, Revenue approves failed_close_compensation as a credit.released@2 reason. Its payload uses initiator: system_other and reversal_reason: Credits Released. The envelope actor is system:revenue, its subject is the exact original credit reservation, and the release time is Revenue's retained decision time. The private owner writeback requires the genuine exact Delivery compensation receipt and enforced original sender barrier. It atomically releases that reservation, cancels its original unfunded Order, retains an immutable writeback proof and emits exactly one credit.released@2 and one order.updated@1. Both events and the domain writes commit in the same producer transaction. No account balance change, ledger entry, debit, refund, forfeit, purchase or customer.handoff follows.

ADR-0054 supersedes the earlier command-key correlation proposal. The new Delivery cancellation event and both Revenue financial events use the original successful bind ReceiptRef.event_id as their common correlation_id. Each keeps its own canonical event ID, registered payload/schema version, producer, actor, subject and retained owner decision time. The compensation key remains in its existing command/journal provenance. Correlation supplies neither financial authority nor retirement eligibility. Ordinary release/refund behavior and Workbench cancellation authority remain unchanged.

The accepted reason must be present in the dispatcher package's bundled credit.released-v2 schema. Revenue rejects substituting a different reason or bypassing validation. Read-only diagnosis of installed @sguild/dispatcher 2.0.2 confirms its bundled schema rejects only this accepted enum while the canonical schema validates the payload. The genuine Delivery g1 receipt is retained; Revenue's failed event validation rolled back the whole owner writeback. No financial event or ledger entry was committed, and no finalization command was allocated. Evidence is pinned in Revenue checkpoint d797501677d7050b3516688a07b6ec66a743503e, artifact docs/adr0054/producer/evidence/third-compensation-validation-diagnosis.json, SHA-256 bff28917619383daf078a9f8afafa4d6e666329e0cf56786fd9f409150cc9eba.

The coordinator may reconcile stale Proposed metadata against these formal owner positions and package the accepted schema through Platform's canonical SDK. This acknowledgment does not claim successful financial writeback, completed retirement, deployment or production activation. Existing implementation commitments remain open. Live ledger discovery was refreshed for this memo; the acknowledgment introduces no duplicate commitment or completion of the remaining implementation/activation gates.