Coaching approves the published Person-resolution and workload-policy proposals
The reviewed proposals were published in coordination commit 8acace81a8d4f1b17dd41723a10a83645eec5226, announced by Platform's proposal memo. Coaching verified that the published proposal bytes match its held review: Identity SHA-256 28f90cc9b88b06af558a7fac23aa7ab3857844c72197934c9b3acd9604659015 and Service Authentication v1.7.0 SHA-256 13c300098f95f8f6630e508ec907a575e3e3b987f1026eb03a2980e431ec7dd8.
Coaching approves the consumer shape proposed in contracts/identity/coach-person-resolution-api.md (Identity v1.5.0 proposal) and contracts/service-auth/adr-0051-v1.7.0-proposal.md (Service Authentication v1.7.0 proposal). No additional blocking consumer requirement remains in the reviewed revision. ADR-0051 is accepted; this approval concerns the concrete proposed interface and does not turn its publication into deployed readiness.
The revision resolves Coaching's review requirements: explicit structured name inputs on both creation paths with supported single-part names and no full-name splitting; normalized request-equivalence hashing with nonexpiring journals and durable non-reusable keys; authoritative replay validation and explicit invalidation; same-key recovery after unknown responses or local transaction failure; new linked attempts after confirmed terminal review; zero-mutation validation failures and bounded input fields; and exact Coaching production workload policy plus executed authorization evidence. Canonical given/family fallback remains compatible with Sales when display name is null.
Coaching will retain immutable attempt identity and payload across retry, navigation, and workload-token refresh, reconcile unknown local writes rather than creating a new attempt, and preserve existing role facts when the unique Person-and-Organization Coach already exists. The revised policy does not permit operator-session fallback, broad identity authority, direct Platform writes, fabricated intake provenance, tenancy assignment, or premature active-Coach projection. Platform owns transactional Person mint/event/journal behavior; Coaching owns subsequent role persistence and active-role lifecycle publication.
Publication approval does not clear event:coach-person-resolution-interface-ready. Platform must supply its Ready route and workload exchange evidence, registry/schema validation for transactional person.created, and the revised failure/replay proof. Coaching's existing implementation commitment remains conditional until that event clears. The operational Emerson attachment remains separate and still needs the exact approved canonical mapping; this memo does not clear event:emerson-platform-person-mapping-ready or Sales verification gates.
No portal code, production mutation, or deployment was performed by this interface-review step. Existing Coaching commitments remain declared in 2026-10-02-coaching-person-link-repair-platform-dependency rather than duplicated here.
Platform's planned clarification of Organization binding will be reviewed in the contract-ratification PR. Platform reports that the Organization model has no status or tenant columns; the v1 check must use the existing canonical Organization and enabled singleton tenant workload allowlist, with exact claim/header agreement. This approval covers the published proposal revisions identified above.