Ratify ADR-0051 identity and workload contracts and register person.created
This single contract PR publishes Identity v1.5.0, Service Authentication v1.7.0, the ADR-0051 amendment and this record together. It follows Platform proposal commit 8acace81a8d4f1b17dd41723a10a83645eec5226 and Coaching's approval at ab1d3eb2f1458c49562404d931be0c469ef9976f. Existing consumers remain compatible; no route, policy or contract version is deprecated, so no deprecation window starts.
Authorities and clarifications
The authoritative operation is Coach Person Resolution API. The workload policy is Service Authentication section 4.10. The retained proposal is historical rationale, not a second policy authority.
The PR clarifies that Organization authorization requires an existing canonical row and an enabled exact singleton workload binding. Platform's Organization table has no status or tenant columns. It also aligns authentication codes with Service Auth section 6: UNAUTHENTICATED, FORBIDDEN and INSUFFICIENT_SCOPE. These clarifications require Coaching review of the final PR before merge.
Event registration proposal and acceptance
Platform registers person.created, schema version 1, with Platform as producer and platform-warehouse as initial consumer. The owning contract is Identity. The payload is the exact ten-field canonical Person shape at person.created-v1.json, with no contact, role, tenancy, membership or fabricated intake data. This implements the already accepted Identity section 7.1 requirement and introduces no new consumer obligation outside Platform.
The registry and payload schema publish in this PR. Platform must mirror both into its dispatcher package and prove transactional outbox publication before any ADR-0051 mint. Registration alone does not prove every existing mint writer already emits the event, or that a deployed warehouse consumer has processed it.
Execution and release gates
The operator's explicit instruction, "Coordination can authorize production changes and mutations", was verified in chat 01a0e095-f279-7fd0-a8ef-92ce8f9547fc; the coordinator skill now reflects that scope. Necessary ADR-0051 production work can proceed after its concrete safeguards and evidence pass. This record does not authorize unrelated changes or customer communication.
Emerson's repair remains bounded to the previously reviewed Coach, Organization and private input hash. Real PostgreSQL rollback, replay, concurrency and writer-exclusion proofs, the registered event, a fresh no-match preflight and exact post-write verification precede mapping delivery. Coaching owns attachment and Sales owns final name verification. The guarded procedure preserves existing Coach scheduling facts.
Portal readiness separately requires implementation, durable retry and negative proofs, a Ready deployment and the exact Coaching production workload exchange. The original Platform implementation commitment remains working. Neither coach-person-resolution-interface-ready nor emerson-platform-person-mapping-ready clears from this contract publication.
Platform main automatically deploys the shared Render worker after CI. Any Platform main publication must be sequenced with the ADR-0048 and ADR-0049 coordinators before it can restart fanout or process existing backlog. This coordination-only PR does not publish Platform application code.