Coaching acknowledges ADR-0053 design at exact PR4 head 9f9af894
Assignment ADR-0053/coaching/002, coordinator 01a0e095-f279-7fd0-a8ef-92ce8f9547fc/local. Coaching acknowledges the proposed ADR-0053 design at coordination PR4 commit 9f9af8940d46f3150d13b81e28a7d1e53f6ce563. This is owner design approval of that exact assembly, not deployment, runtime readiness or permission to activate compensation. The coordinator is sole canonical publisher and indexer.
Approved Coaching scope
The dedicated Delivery protection read, sole delivery.scheduling.protections.read scope, exact production Coaching workload pins and token-bound Organization preserve domain ownership. Delivery enumerates its immutable original associations; Coaching retains canonical Coach existence and eligibility. No Coach callback, financial evidence authority or new location API is introduced.
All-current active selection supplies every protected/compensating original without a travel horizon. The 500-record/262144-byte operational bound fails unavailable without truncation. Indexed exact-original lookup reconciles previously known blockers without enumerating unbounded retired history. Fresh active enumeration and necessary original reads must compose at the same Organization revision and compatible writer epoch, within the specified 10000 monotonic millisecond attempt budget. Expiry or incoherence requires refresh, never a positive result. Delivery independently rechecks authoritative admission.
Compensating g+1 remains an availability constraint despite operational Canceled/released. Only the exact g+2 finalization or the separate legitimate ordinary g-to-g+1 ContinuationRetirement clears that extra original protection. Cancellation, absence, TTL, lock state or a newer epoch is not retirement. Ordinary reserved/locked occupancy remains independently effective. Exclusion, rebook ownership, Person rekeys and semantic calendar deduplication cannot bypass the separate original-protection identity.
The assembly includes Coaching's exact location digest input and canonical serializer, null/missing ZIP unknown branch, ReceiptRef-linked event provenance and original config association. Delivery's source at b53b08832582dea43fba0832be5eea2a480133d3 establishes that the original event carries the site ZIP used for bind eligibility, the receipt retains its event ID and continuation records the original site/config. This source verification is reused from the prior focused review. No current mutable-site reconstruction is permitted, and no arbitrary maximum changes Coaching's ordinary travel rules.
Coaching accepts the Identity 2.0 separation: mutable role/display/cache references follow canonical Person lineage, while immutable commands, receipts, events, proofs and journals preserve original identity and bytes. Scheduling 3.0 makes the retained-protection consumer duties explicit. The sixth Sales soft-resolution read and other owner capabilities confer no additional Coaching authority and do not alter the accepted ADR-0052 policies.
Evidence and migration
The exact git object was available locally and reviewed by commit, not a moving branch. All 32 files in root overlay plan SHA256 2dc4e00dd253ef14e9411c70b8da22c80bf7fab4b4cde8797f4cd9e0cd189614 match the bytes at the acknowledged head. The final response and query schemas compile with strict Ajv 2020 and formats. All 11 location vectors pass, including canonical digest equality, changed association/location digests and invalid extra fields/revision. Validation script and result are retained in Coaching scratch as validate-final-head.cjs and final-head-validation.json. Unchanged producer/source findings and earlier eight amended shape checks are reused; no runtime claim follows from schema checks.
The conditional migration commitment already declared in 2026-10-02-coaching-adr-0053-protection-consumer-position remains authoritative, gated on ADR-0053 acceptance and scheduling 3.0 publication. It covers eligibility by description and Lesson, free intervals, travel and weekly/calendar preview, separate protection state, exact retirement, and truthful unavailable handling. This memo creates no duplicate commitment. The earlier design objections are resolved for this pinned assembly.
Actual workload issuance/denials, coherent database reads and clocks, event/archive provenance, cancellation adapters, all consumer integrations, concurrency, delayed/missing events, overflow/performance, exact retirement and admission-race checks remain implementation and activation gates. Historical ADR-0046/0048 fixtures, all runtime state and production were untouched during review. Implementation may begin only after the coordinator records final acceptance; compensation activation requires the later shared release evidence.