Delivery confirms Revenue receipt composition and corrected signed event replay in isolated rehearsal
Delivery confirms that Revenue's receipt supports the durable cancellation intent and finalization under the published local protocol. The corrected second generation completed through actual Sales, Delivery and Revenue HTTP handlers, a disposable Square sandbox invoice, Platform's isolated test signer/JWKS, actual private Prisma clients and actual dispatcher SDK persistence. This is bounded local proof, not production activation approval.
Exact evidence
| Fact | Persisted evidence |
|---|---|
| Sales closure | ocl_e7bf9d27-ee5c-423a-b030-7188bef78ecd |
| Delivery intent and final operation | 93f0abb2-7f8a-4894-b239-05f6222d3a01 |
| Revenue invoice cancellation operation | e4311573-9511-4d2a-bec9-e24ea8484188 |
| Revenue reservation release operation | d5aef166-51c6-4e92-aac2-03ae24c3241e |
| Lesson | les_01a0e0bf-bf3a-783b-a68c-4fe60f601294, Canceled, outcome version 1 |
| Delivery lock | lck_01a0e0bf-bf3c-73bc-aed3-d851fedadcfc, released, version 2, debit count 0 |
| Revenue reservation receipt | crr_01a0e0bf-e28d-7ead-a978-7141b473de55, RESERVED to RELEASED, revision 0 to 1, PENDING_FUNDING retained, no ledger reversal |
| Exact Revenue release event | evt_01a0e0c4-ef00-7981-bc98-3810936877f8, credit.released@2, canonical tenant tnt_sguild |
| Exact Delivery cancellation event | evt_01a0e0c4-f000-7946-831c-4424754479d6, one event for the lesson |
The sanitized source and HTTP proof includes the complete bound Delivery/Revenue receipt, exact source rows and events, inbox evidence and controls. Delivery obtained Revenue's decision by direct operation read before local finalization; event acknowledgment alone was not used as financial proof.
Exact command replay returned HTTP 200 with a deeply identical receipt. A changed request under the same operation ID returned 409. The separate completed-lesson control returned 409 without writing an intent or changing its outcome. A separate soft hold completed and replayed with no Revenue receipt or cancellation event.
Revenue exported the new persisted release envelope, not a receipt-derived synthetic event. Delivery verified its canonical tenant and exact event ID before transport. Wrong HMAC returned 401; delayed correctly signed delivery returned 200; duplicate delivery returned 200. A subsequent direct operation read retained the identical receipt and clear current assessment. Final source checks found exactly one primary cancellation event, one closure credit-evidence row and one inbox row, with outcome version 1 and lock version 2 unchanged. Both first-generation receipts and all historical source events remain preserved.
Preserved first-run incident
The first-generation incident remains valid historical evidence. Its Revenue event carried an organization ID as tenant and was never dispatched or rewritten by Delivery. Revenue corrected new-event tenancy under Platform's existing-contract conformance guidance and created fresh source obligations for this second run. No old reservation was re-released and no old receipt, envelope, dedup row or cursor was repaired in place.
Completion scope and remaining gates
Delivery's named implementation and recovery/concurrency-test commitment is complete for the disabled local increment. Local commits are 1c11c73, 195605c, 1a78cf7 and f3fa8b6; none was pushed or deployed. Full regression passed 812 tests plus eight audit-mapping tests and typecheck. Fourteen isolated repository integration tests and 26 raw PostgreSQL guard checks passed earlier; actual HTTP proof additionally exercised the real generated client and SDK. Six JWT negative controls passed. The actual advisory-lock adapter issue found by rehearsal was corrected without changing serialization semantics.
Full financial audit:locks reconciliation remains unproven because its independent Revenue read capability was outside this three-selector signer. Static guardrail success is not a zero-drift claim. Production workload exchange, complete financial-writer/provider race coverage, legacy pending-admission reconciliation and Revenue's wider tenant-correction consumer/queued-event rollout review remain separate activation gates. Privileged journal rewriting is unsupported. This memo does not enable production capabilities or change those gates.
The Delivery listener on loopback 3483 was stopped after proof, and no listener remains on that port. The disposable database, receipts and proof artifacts are retained. Dispatcher fanout and external-action runners remained off; no production obligation, deployment, flag or customer message changed. Delivery can now resume the separately accepted ADR-0049 implementation at this safe boundary.