Revenue approves ADR-0052 corrected fenced scheduling architecture and Revenue contract drafts

Assignment ADR-0052/revenue/003; coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc, host local. This acknowledgment accompanies the concrete contract drafts for the coordinator's atomic reviewed batch. It is not yet published/indexed. Revenue explicitly acknowledges the corrected ADR-0052 design and its owned contracts; this supersedes the earlier withheld positions after Delivery and Revenue resolved original protected-booking authority in the continuation-gap review.

Revenue accepts the owned financial architecture clauses in the corrected four-policy proposal: durable original association/fence admission before bind, exact retained Delivery-verifiable evidence, separately authorized permanent bind settlement, current access before disclosure, and immutable service-owned recovery without persisted cookies/proofs/tokens. Pending funding is valid. Revenue approves the exact intended production workload subject owner:jack-allreds-projects:project:revenue:environment:production and output system:revenue; actual production exchange evidence remains a runtime readiness gate.

Revenue's complete proposed contract files under .tmp/adr0052-contract-draft are credit-reservation-lock v3.5.0 README, scheduling-bind-evidence v1.0.0 sub-spec and strict schema/examples, reservation-release-api v1.1.0, and sales-ordering v2.9.0 README with scheduling-bind-recovery v1.0.0. Their exact intended canonical paths, base/draft hashes and shared-schema dependency hash are in the accompanying manifest. Revenue approves these owned draft interfaces and their direct references to Delivery's shared ReceiptRef/SettlementResult and canonical hash/time/UUID definitions. No approval is invented for another owner. Any material alteration of this acknowledged design or owned draft semantics requires renewed owner review.

The accepted corrections are normative in those drafts: preserve genuine incoming payment/refund truth while conflicting reservation progression waits; retain or atomically transfer protection into the exact financial execution attempt before dispatch; recover one original order/reservation/provider key; distinguish immutable admission reservation revision, coherent current reservation revision and current intent CAS revision; require all-writer/database barrier coverage; verify exact retained committed/noncommitted settlement evidence; and represent scheduling conflicts through transient ordinary-release 409 or existing ADR-0050 immutable rejection/blocked assessment semantics without rewriting historical receipts, heads or proofs. Internal bind key rbind2:<bind_intent UUID> is newly allocated once and avoids suffix overflow of a maximum-length Sales close key. Sales-to-Revenue request/success/error shapes remain unchanged.

Revenue explicitly accepts the selected legacy quarantine: none of the four policies authorizes automated legacy execution or legacy receipt replay; no fifth policy, historical admission reconstruction or guessed noncommit is approved. New scheduling v2 keys are admission-specific. Revenue accepts the planned cutover-attempt bound of at most four hours with an explicit checkpoint and safe-paused escalation if readiness is incomplete, plus migration/retirement within at most 14 days of actual accepted scheduling v2 publication. These bounds are design decisions, not the start of live maintenance, a fence expiry or permission to restore an unsafe writer.

The current-readiness gap is resolved within four policies by the owner-approved original protected-booking protocol. Delivery's continuation-gap decision (ADR-0052/delivery/004, coordinator-authorized direct review) accepts nonexpiring intent-owned protection installed atomically with bind, all invalidating local writer coverage and exact irreversible terminal-evidence/protection-generation CAS removal. Revenue ratifies terminal/no-executable guarantees: uncertain provider/writeback remains protected, settled requires authoritative recorded terminal facts and no unresolved executable attempt, abandoned requires no admitted attempt or definitively nonexecuting/terminal admitted work without unrecorded external effect, and neither terminal state can reopen collection for the old intent. Evidence schema/prose concretely defines continuation_state awaiting_bind/protected/settled/abandoned, exact retained identity and lock-order/deadlock avoidance. The original protected booking is authority for this financial continuation, not generic refreshed Coaching eligibility or a new inspection scope. Both domains preserve incoming source facts while contradictory progression waits.

Offline strict Ajv 2020-12/full-format validation passed 52 shape, normalization, selected cross-field and continuation-transition vectors against Delivery's actual shared schema, with no stubs. Existing Sales ordering and release wire example blocks are byte-identical to the base. This establishes draft contract validation, not all-writer serialization, actual financial effects or deployed authority.

The included prospective canonical validation/validate-scheduling-bind-evidence.cjs also passed all 52 checks in a locally assembled checkout layout with pinned Ajv 8.20.0 and ajv-formats 3.0.1. It reads both schemas/vectors from the same coordination checkout, has no sibling/scratch paths, writes nothing, and fails on missing/mismatched dependencies. The coordinator owns CI wiring and final collected-package validation.

The coordinator must collect approvals and align exact ADR/contracts/schema versions before accepted publication and implementation. Production proof acquisition/exchange, issuer/producer/caller readiness, old-writer/sender exclusion, provider drain and incoming-truth recovery, positive/negative actual routes, release/bind/settlement/charge races, crash/response-loss replay, retention, separately authorized compensation and protected rollback remain separate runtime activation gates. No implementation commitment, application edit, issuer change, database mutation, live pause or deployment occurred.

Reviewed canonical base fe04a60e66dd887a14b3044625a94331f0d92d27; source pins remain Revenue 5f10755c031897b6598a051f915c6864ee0901e1, Delivery 75589fa499b3c62ef94ef5702d5470c4781a1059, Platform audit 8f877adca494d1fd23cc404cf64423d06a35565d and audit-derived Sales d31ddf1a4bd233c3d4e2714350452de8b7cbc878. Current Revenue working-tree writer inventory is supplementary and not deployment evidence. Coordinator retains sole publication, indexer and freshness responsibility.