Sales acknowledges ADR-0051 and gates canonical coach-name verification on producer delivery
Sales position
Sales acknowledges ADR-0051 as proposed and has no consumer-side objection. Platform owns canonical Person resolution and identity; Coaching owns Coach creation and the persisted Person reference. Sales remains a read-only identity consumer. Sales will not mint People, write Person or Coach identity links, import Platform internals, fabricate intake events, or use a name-only workaround for the missing link.
This acknowledgment records Sales' architectural position. It does not accept an unspecified endpoint, change the ADR status, clear Platform's mapping/interface delivery events, or authorize production mutation, deployment, or customer communication.
Expected consumer outcome
Emerson's existing Coach coa_3ff0f8c9-f8cf-444d-b1d0-e06d3f84c37d retains its ID and scheduling facts. Coaching exposes its approved non-null Person reference in the roster. Sales resolves that Person through Platform's existing read surface and shows the canonical display name in the Coach proposal selector instead of Coach 84c37d.
A Coach created by the repaired portal must follow the same roster-to-Person read path. Coaching and Platform own creation, retry, ambiguity, and identity-failure proof. Sales will use their exact producer-created verification record; the Sales check will not create production fixtures or submit proposals.
Consumer assessment and verification plan
The inspected modules/coaching-roster/coaching-roster.service.ts already hydrates roster Person IDs through loadPersonsBatch, with best-effort individual reads for applicable errors, and applies Platform displayName. app/workbench/_components/AvailabilityPlannerDrawer.tsx uses that display name for coach options. No Sales code or DTO change is currently required by the proposed unchanged roster and Person read contracts. A missing link or unavailable identity read can still yield a fallback, so source compatibility is not proof of a successful live display.
After each corresponding Coaching commitment delivers, Sales will record the environment, exact Coach/Person mapping, roster response, successful Platform Person display read, and resulting selector label under the relevant organization and market. For Emerson, verification must use the original Coach ID. For new creation, Coaching must supply the actual portal-created linked Coach and creation evidence, not a seed-only substitute. Any failure will be reported with its read boundary and response evidence, without silently changing identity ownership or consumer contracts.
The two Sales commitments are independent final consumer checks. Coaching may complete its own mapping/integration evidence without waiting for these Sales commitments, avoiding a circular dependency. Emerson verification does not need to wait for the new portal interface; the new-coach check waits for Coaching's portal integration and delivery evidence.
Current status and asks
Both consumer checks are now complete. The actual portal-created synthetic Coach displayed its canonical name in the authenticated production proposal dropdown; see portal consumer evidence. This supersedes the pending portal status in the earlier Emerson checkpoint below. Fixture cleanup remains with the owning domains.
Emerson's existing-Coach consumer check is complete following Coaching's production attachment. The authenticated live Sales proposal selector displays Emerson Dunham. Exact mapping, read boundaries, and evidence are recorded in Sales verification. Commitment 0 is completed; commitment 1 remains conditional on Coaching's portal integration and producer-created verification record. Please supply that record and creation evidence when ready.
No Sales source change, production mutation, deployment, or customer communication was performed. Prior follow-up sorting work is preserved.