Review ADR-0052 scoped scheduling workload authority
The ADR-0050 soft-hold rehearsal found that the reviewed Sales soft-create and Revenue bind paths do not forward an authenticated human session or accepted scheduling workload token. Delivery's reviewed handlers lack the authentication check required by scheduling section 8.5. This is a source finding, not a verified production exposure claim. Closure capabilities remain deliberately narrower than scheduling authority.
ADR-0052 proposes separate exact-route workload policies for Sales soft creation and Revenue reservation binding. The alternative is explicitly bounded human-session propagation, with the limitations of session expiry and unattended recovery. No new policy, implementation or activation is approved by filing this request.
The user authorized four separate owner-review chats. Each is scoped to ADR-0052; existing ADR-0050 implementation assignments and shared release ownership remain intact. The coordinator is Platform chat 01a0e095-f279-7fd0-a8ef-92ce8f9547fc, host local. Each owner should return one self-contained position, identifying approval, objections, required exact contract changes and acceptance criteria. A formal approval memo must include acknowledges: [ADR-0052]. Do not acknowledge unresolved resource or authority semantics merely to unblock the rehearsal.
Platform owns exact workload identity, selectors and claims. Delivery owns route and resource enforcement. Sales owns operator admission and durable replay. Revenue owns bind authority and canonical reservation/order/lesson evidence. Each domain authors only its own position and commitments. No acknowledgment or implementation commitment has been invented for another domain.
Prepare domain response memos in the permitted domain coordination clone. The coordinator will publish one coherent reviewed batch after collecting exact paths; do not independently race publication or indexers. Architecture approval must precede implementation. If eligibility authorization changes, explicitly add Coaching to the decision rather than assuming the local substitute proves its authority.
The held-closure recovery remains a separate ADR-0050 proof. ADR-0049's existing release owner retains its pre-lineage production sequence; this proposal does not add new scheduling changes to that release.
Source review: Platform local candidate 8f877ad, docs/adr0050-scheduling-session-boundary.md and docs/adr0050-soft-hold-auth-requirements.md; Delivery 75589fa, Sales d31ddf1, Revenue 5f10755. Canonical basis: ADR-0001, ADR-0036, ADR-0039, service-auth and sales-scheduling-surface section 8.5.
Collected contract review
The request now covers the four-policy design in the revised ADR: soft-create, bind, exact Revenue bind evidence and bind settlement. Review the collected scheduling v2 contract, workload and settlement sub-spec, compatibility and release annex, service-auth amendment, Revenue bind evidence, release interface and ordering recovery together.
Exact-contract review adds intent-owned Delivery continuation protection and irreversible Revenue terminal evidence, closing the gap between historical bind receipt and financial continuation. Each owner must review the assembled schemas, normalization vectors, all-writer protection and retirement semantics before its formal acknowledgment. The package includes reproducible offline checks via npm run validate:scheduling-contracts; these do not establish runtime readiness. The original request's implementation and activation gates remain open until their separate evidence is complete.