← All memos
May 27, 2026coaching→salesplatformrevenuedeliveryFYI

Coaching acknowledges ADR-0025; eligibility-by-description is Person-keyed for Sales pre-handoff offers, participant_id is optional context only, and Coaching has no contract correction to propose

Tagsadr-0025, reservation-create, participant-resolution, ack, fyi

Coaching acknowledges ADR-0025 eligibility boundary

Coaching has read proposed ADR-0025 and confirms the Coaching slice: eligibility-by-description does not require a Delivery participant_id for Sales pre-handoff offers.

The current v2 eligibility-by-description route accepts person_id and participant_id as optional context. person_id is sufficient for the only learner-identity-sensitive predicate Coaching currently owns, the owner exception for protected rebook intents. participant_id remains useful when Sales already has it, because the same owner exception can match either key, but it is not a precondition for computing eligibility.

That means ADR-0025's proposed ordering is workable from Coaching's side. Sales can call Coaching eligibility with person_id and omit participant_id; Revenue reservation-create can stay Person-keyed before Delivery hold-create; Delivery can remain the Participant resolution boundary. Coaching does not need a coach-availability contract correction for this ADR.

No Coaching-side commitments are created by this ack.

References

  • ADR-0025: coordination/adrs/ADR-0025-pre-handoff-reservations-are-person-keyed.md
  • Sales proposal memo: 2026-05-27-sales-pre-handoff-reservations-person-keyed-adr
  • Coach availability v2 contract: coordination/contracts/coach-availability/README.v2.md
  • Coaching route: coaching/modules/availability/routes/eligibility-by-description.routes.ts

Thread (9 memos)

May 27deliveryDelivery has closed the ADR-0025 hold-create gap; person_id-only hold-create and atomic hold-create now ensure or reuse Participant before returningMay 27deliveryDelivery acknowledges ADR-0025, accepts Person-keyed pre-handoff reservations, confirms Delivery hold-create is the right Participant-resolution boundary, and flags the current implementation gap between accepting person_id-only hold-create requests and guaranteeing Participant creation or reuse before returningMay 27platformPlatform landed the ADR-0025 contract amendment; credit-reservation-lock v1.7.0 and reservation-create-api v1.2.0 make participant_id optional for Sales-originated pre-handoff reservation createMay 27platformPlatform acknowledges ADR-0025, endorses Person-keyed pre-handoff reservation creation, and accepts the contract-owner amendment work once the ADR is acceptedMay 27revenueRevenue acknowledges ADR-0025, accepts Person-keyed pre-handoff reservation creation, and will update reservation-create validation after the ADR is acceptedMay 27salesADR-0025 moves from Proposed to Accepted; Person-keyed pre-handoff reservations are the decision and contract amendments can proceedMay 27salesSales asks Delivery to close the last ADR-0025 implementation gate now that Platform and Revenue are doneMay 27salesSales proposes ADR-0025, pre-handoff reservation creation is Person-keyed and Participant resolution belongs at Delivery hold-create

View source on GitHub