ADR-0051 accepted with separate interface and Emerson repair gates
Architectural position
Platform explicitly acknowledges ADR-0051. Person resolution remains Platform-owned; Coach persistence and its creation or repair audit remain Coaching-owned. Sales hydrates canonical names from the existing roster and Person read surfaces. The authenticated resolution operation must preserve identity review, tenant binding, durable retries, and concurrency protection. A resolved Person is not deleted as compensation for a failed Coaching transaction.
Coaching's explicit acknowledgment is 2026-10-02-coaching-adr0051-ack-integration-plan (published commits d3885e2 and clarification 36a77f1). Sales' acknowledgment is 2026-10-02-sales-adr-0051-consumer-ack (published commit 4001be5). With Platform's position recorded here, the coordinator transitions the ADR to Accepted. This accepts the architecture, not an unfinished endpoint, deployment, or operational mutation.
Emerson read-only evidence
Coaching exported exactly Coach coa_3ff0f8c9-f8cf-444d-b1d0-e06d3f84c37d, Organization org_01900000-0000-7000-8000-000000000001, from a read-only transaction. Its Person reference remains null. The contact-bearing export stays in an ignored local file and is not included in coordination artifacts.
Platform independently used its production database configuration with default_transaction_read_only=on and BEGIN READ ONLY. The canonical Organization exists. Candidate selection across all Person statuses found zero matches for normalized phone, supplied email if present, exact given/family name, or exact display name. The query returned no unrelated Person records. This is a preflight result, not a durable reservation of the identity or proof against later concurrent changes.
The existing scripts/bridge-coaching-legacy-coaches.ts then ran for this one input in dry-run mode with database-enforced read-only access. It exited zero with would_mint=1, minted=0, role_assigned=0, and failed=0. Evidence is retained locally in Platform .tmp/adr0051/emerson-readonly-preflight.json and .tmp/adr0051/emerson-bridge-dry-run.json. No Person ID was allocated, no mapping is ready, and no production data changed.
Remaining gates and sequence
The existing bridge accepts a single phone match without the required compatible-name check and does not provide the durable concurrency protection proposed for the portal operation. Its dry-run does not authorize applying it blindly. A reviewed, guarded Platform create-or-match operation must recheck current candidates and supply the canonical ID, name, decision, and retry evidence before Coaching attaches the reference.
adr0051-emerson-identity-repair-authorized clears only when Platform records explicit operator authorization for the exact production repair against a reviewable guarded procedure. The authorization must cover the canonical Person mapping operation and its necessary Platform tenancy/role effects. It does not authorize a broader backfill. The downstream emerson-platform-person-mapping-ready event remains uncleared until the actual mapping exists and is verified.
The concrete portal interface is under owner review. Review must settle exact request and name semantics, name-only candidate handling, replay after canonical identity changes, request equivalence and retention, input validation, and workload authorization. Platform will record that interface and its implementation commitment separately. coach-person-resolution-interface-ready remains uncleared until the agreed contract, implementation proofs, approved deployed route, and workload policy are available.
Coaching is preparing the existing-record attachment and its local proofs independently of portal integration. It must preserve Emerson's Coach ID, Organization, coverage, availability, and prior audits. Sales' two conditional commitments remain independent final consumer checks after Coaching's corresponding producer evidence, avoiding a circular completion gate.
Requests and verification boundary
Coaching should review Platform's forthcoming exact interface and publish its position. Platform and Coaching should return concrete implementation and local verification evidence before requesting production release approval. Sales should retain its read-only verification commitments until the exact producer-created IDs and environment are supplied.
The live ledger was checked before this filing. Coaching's mapping and interface commitments and Sales' two consumer checks were still conditional; none was marked completed. This memo clears only the ADR's architectural acceptance prerequisite. Production repair, endpoint readiness, and final Sales verification remain open.