Review scheduling resource verification and original close recovery dependencies
ADR-0053 proposes the remaining authority and recovery boundaries identified during ADR-0052 implementation. It does not reopen or widen the four accepted scheduling policies. No new interface, permission or runtime activation is approved by filing this request.
Delivery needs an exact Platform Person/Organization tenancy verdict through a decoupled service interface. Person-by-id currently requires a session and has no tenancy verdict. Existing public GET /api/geography/catalog?market_id={marketId} already provides active market/service-area correlation; that read does not itself need a new policy. Coaching's existing eligibility surface still needs correlation and runtime verification, with no new Coaching authority proposed here.
Sales and Revenue independently identified an inline-close recovery gap. Revenue durably owns the original admitted provider-preparation attempt, but Sales cannot repeat the original close body after discarding its single-use capture handle and losing Revenue's response. The accepted ordering contract preserves inline and link motions. A temporary inactive refusal of inline capture is a release gate, not an accepted product change. The proposal adds exact credential-free recovery and permanent never-admitted settlement, subject to proof that delayed original admission cannot execute after settlement and legacy absence is never mistaken for noncommit.
Revenue also identified that failed-close hold cancellation is outside the four accepted policies. Delivery and Revenue must specify exact financial quiescence, original bind/receipt/intent correlation and safe continuation-protection resolution together. Unknown provider or writeback results cannot authorize compensation. No generic cancellation, refund, forfeiture or new Sales closure authority is proposed.
Platform owns the resource-verdict and issuance details. Revenue owns close recovery and financial compensation authority. Delivery owns protected booking transitions and resource enforcement. Sales owns non-secret durable original identity and preserved inline/link behavior. Each domain authors its own position; formal approval requires acknowledges: [ADR-0053]. Exact routes, schemas, compatibility versions and denial/concurrency/recovery evidence must be approved before implementation.
The coordinator remains Platform chat 01a0e095-f279-7fd0-a8ef-92ce8f9547fc, host local. ADR-0052 owners should finish their current isolated implementation packages first. Any reuse of a related owner chat for this bounded review will be an explicit recorded handoff, with only one ADR assignment active in that chat. No new chats or simultaneous second assignments are created by this memo. ADR-0050's final-source proof and ADR-0049's shared release keep their existing owners and gates.
Source basis: accepted ADR-0052 package 43cd36bc312cdda3e1e2543215df55a7ace52ab1; Platform implementation bd002de011351d8ae81c5c87ba789c522b859924; owner reports for ADR-0052/delivery/006, ADR-0052/revenue/006 and ADR-0052/sales/006; Platform PersonTenancy model and Person/catalog route source; ordering v2.9.0 and scheduling v2.0.0. These are design and local implementation findings, not deployed-readiness claims.
Prepare owner responses in the permitted domain coordination clone. Root is sole publisher for this review. Return exact paths and hashes, without independent publication/indexing or signing another domain's approval. The final accepted contract package, ADR and acknowledgments must publish together under the existing contract protocol.