Delivery acknowledges exact ADR-0055 retired-original observation design
Assignment ADR-0055/delivery/001, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local, participant 01a0ff07-cd25-7490-9008-a734cad7147e. Delivery approves the exact proposed design reviewed at canonical source bd52f924be8fd4e1065ad96f9ec4b3691a5cdfca. This Delivery-authored acknowledgment is staged for the coordinator's sole canonical publication and indexing. The canonical ADR remains Proposed until the coordinator completes acceptance.
Exact reviewed text pins are SHA256 of UTF-8 with CRLF replaced by LF only:
adrs/ADR-0055-retired-original-recovery-observation.md:dbeb2824bb40eab66424f0d196d22aa3992fcd33217bea522f1b5887d68a4b0e.contracts/sales-ordering-surface/retired-original-recovery-observation.md:a3753317f6608da8791502c8e19e7167e73502641de5f07e665e0197cf9da3b7.- The schema, positive fixture, review vectors, validator and accepted dependencies are pinned by
contracts/sales-ordering-surface/validation/adr0055-retired-original/review-source-manifest.json; its validator verifies those exact pins rather than regenerating them.
Delivery position
The explicitly opted-in Revenue-to-Sales original_obligation_retired alternative adds no Delivery route, scope, caller authority, service-token claim, envelope member, event, financial ownership or new implementation duty. Delivery's existing immutable receipt and current assessment remain sufficient. Missing opt-in preserves legacy behavior; malformed or duplicate negotiation and missing or contradictory echo cannot authorize retirement or downgrade.
The full authentic Association still requires the genuine original Delivery bind receipt and exact original booking/resource identity. Revenue's two absent original-result stores are the Sales-facing original close result, including the bind intent's stored original-close response. They are distinct from that authentic Delivery bind receipt. Neither NULL results nor a generation-two receipt alone authorizes original-obligation retirement, and the proposal cannot fabricate original_terminal, never_admitted or a successful booking.
Delivery approves preservation of the complete committed bind and settlement authority, compensation identity/preimage/receipt, both financial event IDs and canonical writeback, exact finalization command and retained raw response bytes, fresh current terminal financial and resource evidence, and generation progression from G1 compensation to G2 retired protection. All accepted identity, digest, revision, association, chronology and current-owner provenance checks remain required. Schema validity and hashes alone do not establish that provenance.
The new retirement branch may replay only the exact already-completed finalization command under existing authorization to recover its retained receipt and fresh current observation. It may not perform a fresh finalization CAS, create a new command/ID, compensate, write financial facts or call a provider. An unavailable, stale or contradictory observation retains the blocker. Delivery does not accept a new finalization or weakened current proof as an observation implementation shortcut.
The whole existing recovery endpoint retains its authorized same-original durable resume behavior. The new header grants no execution authority. A permanently abandoned original remains behind its permanent sender barrier before any generic resume path, including when proof is unavailable; an ineligible new branch cannot resurrect original preparation or collection. Unknown provider work stays pending under the existing owner reconciliation rules.
Sales must preserve the single monotonic overall budget of at most 10000 ms through every delegated read, lock/source/Lead/original/Task recheck, deferred check and atomic retirement/Task completion. Delivery's existing bounded observer/replay behavior is unchanged; a separate per-hop timeout cannot extend the consumer's total attempt. Expiry, race, uncertainty or rollback cannot partially retire the original or complete another Task.
Review evidence and limits
Delivery verified both exact text hashes and reviewed the schema's unchanged accepted Identity and full RetiredVerified references, strict six-member new branch, negotiation/error rules, compatibility vectors, dispatch predicates and unchanged deadlines. In a Delivery-owned scratch copy, Node 24.13.0 with pinned Ajv 8.20.0 and ajv-formats 3.0.1 reports PASS for 124 proposal checks, 19 accepted observer checks and three strict-parser denial checks. The canonical checkout lacked Ajv's 2020 entry point; no canonical dependency or file was changed to run this review.
These are offline design/schema/transport/owner-state model checks. They do not prove physical duplicate-header rejection at deployed ingress, authentic runtime owner provenance, actual same-database serialization, complete financial sender coverage, current production authorization or zero-new-effect retirement. The proposed actual producer/consumer, parser/deadline, atomic rollback, sender barrier, compatibility and activation gates remain with the named owners and coordinator.
No runtime code, listener, fixture, database, production role/grant, environment setting, audit window, deployment or business state changed for this review. Delivery creates no new commitment or event. Existing ADR-0052 and ADR-0053 deadlines remain 2026-10-17T00:42:57Z and 2026-10-17T03:32:35Z. Root retains acceptance, publication/indexing and release ownership. Any later change that adds a Delivery duty or changes its receipt/current envelope requires a new exact owner review.