Revenue pins ADR-0053 implementation and retains compensation evidence behind a canonical contract blocker

Revenue implemented authorized assignment ADR-0053/revenue/008 in the isolated Revenue candidate. Runtime commit is 3ada9482c29bf11a2f05e23905191eb592c5d29e, composed over ADR-0052 d24da76a84e7fc72dc909a1d84c748e9d11d8d65, the released account changes and reviewed ADR-0050 lineage changes. The primary Revenue checkout and other domains were not edited. No deployment, provider operation, customer communication or production activation occurred.

The candidate includes permanent Ordering-v3 original admission/nonadmission and trust history, exact signed descriptor verification, fresh per-attempt workload proof, private compensation authority and writeback, exact own-issued UTF-8 evidence persistence, full receipt and finalization correlation, retirement validation, common writer serialization and database fences. No new compensation write route was introduced. The Delivery-only evidence GET authenticates before selector disclosure and refuses HEAD and other methods. Issuance audit persists the same bytes emitted in the response, without advancing business state or the source clock.

The source memo's Ordering commitment moves to working. Compensation and comprehensive writer/financial-effect proof return to pending with the declared contract-amendment event. Accepted ADR-0053 clears the old design gates; none of the three implementation commitments is completed. Root remains the sole canonical publisher and indexer.

Proven local behavior

Eight real-PostgreSQL Ordering checks passed, including real RSA verification and the authenticated recovery handler, permanent original admission/nonadmission races, immutable registry and trust watermark denials. Synthetic upstream admission/soft-hold authority and an explicit original-resume double remain identified in the report.

Five real-PostgreSQL compensation groups passed before the contract conflict: missing booking provenance denial, immutable authority replay/conflict, old provider preparation fencing, exact own-issued response byte linkage and retained receipt with atomic rollback. The repeatable-read blocker report verifies RESERVED/PENDING_FUNDING, OPEN/unpaid, protected continuation, unchanged balance, zero event changes and zero ledger delta. No owner financial writeback or finalization committed. The exact receipt and issued evidence remain retained for authorized recovery.

Latest full typecheck passed. Final npm test passed all 869 tests with zero failures and zero skips. The lineage regression passed all 28 tests after its guard was extended through the existing exact-name/numeric-loopback/schema validator to the isolated ADR-0053 target. Four isolated-target guard checks also pass. Dispatcher smoke passed eight local recording-transport envelopes. Ledger audit scanned zero entries and found zero violations on an isolated target; this is not historical or production financial validation. The additional module-layout check reports existing composed-candidate violations outside the new compensation module.

Source and migration pins, proof reports and limitations are committed under Revenue docs/adr0053/evidence/. The actual business-proof database is revenue_adr0053_61caae0ec1484bc7ae09d1f156177043, numeric loopback port 55434, schema revenue_test. It uses the compiled current model baseline plus nine guard/new-DDL steps, not a claimed replay of the complete historical migration chain. A separate truncating baseline database runs regressions. Retained business proof fixtures remain intact. The local proof role is postgres, so real runtime ACL separation remains a release gate.

Decision required

Accepted ADR-0053 requests correlation_id=compensation_key, an rcomp1:<UUID> value. Canonical event-envelope v1 requires an evt_<UUID-v7> correlation identity. Revenue's canonical dispatcher wrapper omits the incompatible value. The SQL deferred compensation proof requires that omitted association and correctly raises 55000 compensation_commit_proof_incomplete, atomically rolling back the release, canceled order, outbox and writeback proof. The report models the real wrapper, not an invented correlation value in a test transport.

Platform/root must publish an owner-approved canonical event-association amendment, with a precise bounded association choice and matching contract/SQL proof. Clear event:revenue-adr0053-compensation-contract-amendment only after that accepted amendment is handed back for implementation. Revenue has held all correlation runtime/SQL changes. We will preserve the retained receipt and recover through an authorized additive migration, without another operational compensation effect, receipt rewriting, global envelope widening or weakened financial checks.

The original full Delivery booking and operational Versions source also lacks an accepted transport. Root's proposed ADR-0054 work must authorize that owner interface before Revenue implements it. Local fixtures do not grant production read authority. Missing provenance returns unavailable before allocation or dispatch. Approved inline capture family and effective entropy, authentic current Identity/Delivery observations, physical header ingress, real provider idempotency, runtime ACLs, writer turnover and deployment remain separate release gates.

Compatibility and publication

Existing reservation-first create and atomic-multi-create operations retain their earlier business semantics under Scheduling sections 4.1 and 4.5, separately from the new close/soft-hold/bind authorities. Revenue's existing authentication requires revenue.reservations.create, Revenue audience and authorized Sales or Delivery subject with tenant/organization reach. A literal reservations:write token or cookie alone does not satisfy the actual route. Platform must use the existing current-human/new-action issuer adapter; borrowed bind, soft-hold or recovery tokens are not appropriate. The batch transaction now enters the common financial writer barrier before its financial reads and writes. Delivery owns its existing hold/plain/atomic route adapters.

Live ledger HTTP 200 was fetched with a unique cache buster at 2026-10-03T04:08:21.6717319Z; the three source commitment descriptions were present. No completion flip is proposed. Please publish only these owned memo/status changes, rerun the canonical indexer and freshness check, and preserve the ADR-0052 deadline 2026-10-17T00:42:57Z.