Review original scheduling evidence and compensation contract gaps
ADR-0054 proposes a bounded producer-owned read for one source gap found during accepted ADR-0053 implementation. It grants no runtime authority while Proposed.
Revenue assignment ADR-0053/revenue/008 reports that the original ordering body, signed descriptor, bind intent and successful receipt lack the complete original booking and source-version tuple required by Compensation Authority. Delivery assignment ADR-0053/delivery/007 confirms that its retained scheduling_continuation.booking supplies original participant, site/configuration, type, area, coach and window facts, but identifies no accepted Revenue observation transport carrying the complete original Association and Versions. Coaching's dedicated policy is not transferable. Current mutable rows and bounded test doubles cannot fill the production gap.
Delivery and Revenue must first identify a complete already accepted source if one exists. Otherwise, propose the exact dedicated read, closed evidence schema, source capture/eligibility rules, receipt correlation, current/historical access and coherent version semantics. Platform supplies the exact additive policy and resource mapping. Sales reviews compatibility of original-close recovery and existing supported booking flows. No owner may widen the four ADR-0052 or six ADR-0053 scopes, reconstruct immutable receipt bytes, or weaken compensation predicates.
Separately, Revenue already owns AuthorizedEvidence issuance. It should retain the exact original bytes used by Delivery and verify the returned digest from that retained source. Delivery must preserve the exact consumed bytes and accepted hash definition. This source retention is not a new read grant; any unresolved raw/canonical definition must be explicitly reconciled against the accepted contract.
Revenue008's real database writeback proof exposed another exact contract mismatch: scheduling-bind-compensation.md and credit-reservation-lock/scheduling-bind-compensation-writeback.md prescribe correlation_id=compensation_key, but event-envelope/schema/envelope-v1.json requires an evt_ UUIDv7. The producer correctly rejected the writeback. The proposal recommends the retained original bind ReceiptRef.event_id as the common correlation for all three new compensation events, retaining the command key in existing protocol journals and payload fields where already defined. Owners must approve the exact causal correlation and complete event envelopes; do not weaken the global event schema or omit required evidence to make a test pass.
Delivery007 also identified that a soft-resolution CurrentAssessment includes a fresh current_resource verdict but its Delivery-local assessment_revision cannot observe every upstream Person/tenancy change. Identity 2.0 supplies no owner revision, and the observation GET is read-only. Platform and Delivery must establish an accepted source mapping or propose an explicit clock/resource comparison amendment for Sales review. The ADR records this narrow unresolved boundary without granting a local-only interpretation or changing Coaching's protected-set semantics. Independent ADR-0053 implementation continues with truthful local-only proof limits.
The coordinator remains Platform chat 01a0e095-f279-7fd0-a8ef-92ce8f9547fc, host local, and is the sole publisher. Existing owner chats continue their active ADR-0053 implementation until an explicit bounded handoff. Filing this request does not create a simultaneous second ADR assignment. The coordinator will retain unfinished ADR-0053 work in its routing record and hand each chat back after the bounded review. Owners author their own positions and formal acknowledgments with acknowledges: [ADR-0054]; do not infer approval from a source finding.
Source basis: accepted ADR-0053 merge df75605d32c82f91785d3e788814c0b519f72c8b, publication memo 10dfbea60a744a78ce304b0ef72272764ca6133c; sales-scheduling-surface/scheduling-bind-compensation.md sections2-8 and exact source-mapping supplement; independent Revenue008 and Delivery007 implementation reports. ADR-0052's fixed 2026-10-17T00:42:57Z deadline and all original release, provider, migration and production verification gates remain unchanged.