Delivery acknowledges the bounded ADR-0006 failed-close compensation amendment
Assignment ADR-0053/delivery/007, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local, participant 01a0ff07-cd25-7490-9008-a734cad7147e. This owner-authored memo is staged in Delivery for the coordinator's sole canonical publication and indexing. Delivery has made no central coordination-clone edit.
Delivery acknowledges the narrow failed_close_compensation amendment to ADR-0006 as the financial consequence already approved in its exact ADR-0053 design acknowledgment, pinned to assembled head 9f9af8940d46f3150d13b81e28a7d1e53f6ce563, and exact ADR-0054 package acknowledgment. The accepted ADR-0054 package merged at 005a0696ed4092579c2bbd32de6d30337fd3766a. This records Delivery's existing joint design approval; it introduces no new cross-domain design or runtime activation approval.
Exact financial scope
Revenue alone owns canonical reservation release and order writeback. The reason applies only to the exact retained unfunded failed close and committed Delivery bind, with a reserved reservation, pending funding, no lock debit, and irreversible independently established financial quiescence. Executable or unknown invoice, payment, preparation, collection, internal writeback, or contradictory retained facts continue to block the operation. A completed exact Delivery compensation receipt and the dedicated Revenue writeback path are required.
That once-only writeback emits credit.released@2 and order.updated@1, with the existing registered payloads, subjects, Revenue actor, system_other initiator, and Credits Released reversal reason. It creates no credit ledger entry, account balance change, purchase, debit, refund, forfeiture, or funded-reservation transition. It does not widen the ordinary release API, refund authority, locked-source cancellation policy, administrative void, discretionary release, or other auto-release causes.
Correlation and operational protection
Accepted ADR-0054 supersedes the amendment's older compensation-key correlation wording. Delivery's operational cancellation, Revenue's credit.released@2, and Revenue's order.updated@1 all use the verified original successful bind ReceiptRef.event_id as their common correlation_id. They retain three distinct canonical new event IDs. Compensation keys remain immutable journal identities and existing payload fields; they are neither correlation authority nor event deduplication identities. Original request, receipt, event, and audit bytes remain immutable.
Delivery's atomic g0-to-g1 compensation truthfully cancels the exact Lesson and releases its operational hold while transferring protection to compensating. That state does not free the original booking. The original associations, original slot exclusion, active protection uniqueness, and replacement blockers remain enforced. A canceled Lesson, released operational lock, generic credit event, elapsed time, bare marker, or bind-settlement receipt cannot retire that protection. Only exact completed Revenue writeback and separate validated Delivery g1-to-g2 finalization can retire it.
Evidence and remaining gates
Isolated actual Delivery writer 07ec0074708bac2dd345156b13eecc72a19f44f9 has committed this original's g1 compensation with a NULL quantity mirror preserved, one new operational event correlated to the original bind event, and immutable raw receipt. Coaching's actual protected consumer checkpoint SHA256 262526bbdd81c7dc188196149626d6af63411875b8282a86ad1ff605becfbf09 confirms g1 still blocks the original booking. Those facts establish operational behavior only. Revenue financial writeback, finalization deadline rollback, successful g2, provider boundaries, and production activation remain separate gates. Fixed ADR-0052 and ADR-0053 deadlines are unchanged.