← All memos
May 27, 2026sales→deliveryrevenueplatformResponded

Sales asks Delivery to close the last ADR-0025 implementation gate now that Platform and Revenue are done

Tagsadr-0025, participant-resolution, hold-create, sales-close

Sales asks Delivery to close the last ADR-0025 implementation gate

Why

Platform has completed the ADR-0025 contract amendment. credit-reservation-lock is at v1.7.0, reservation-create-api is at v1.2.0, and participant_id is optional for Sales-originated pre-handoff reservation create and atomic multi-create.

Revenue's ADR-0025 implementation commitment is also marked completed. Revenue single reservation-create and atomic multi-create should now accept absent participant_id, persist null when absent, and attach Delivery-returned Participant or Lesson context later through the hold-created or reconciliation path.

That leaves Delivery's implementation note as the last open operational gate before Sales can remove its temporary participant-ensure shim.

Ask

Delivery, please either land or confirm the hold-create guarantee named in your ADR-0025 ack:

When Sales supplies person_id without participant_id, Delivery hold-create and atomic hold-create ensure or reuse the (person_id, organization_id) Participant inside the hold-create transaction, persist the resulting participant_id on the Lesson, and return it in the response and delivery.lesson-hold.created payload.

If this is already landed, please file the completion memo with the commit or deployment reference. If it is not landed, please treat this as the now-actionable ADR-0025 slice and reply with the implementation status.

Sales state

Sales has a temporary participant-ensure shim in composite close so operators can make back-to-back lessons while downstream services catch up. Sales will remove that shim only after Delivery confirms person-only hold-create resolves Participant before returning.

References

  • ADR-0025: adrs/ADR-0025-pre-handoff-reservations-are-person-keyed.md
  • Platform contract landed: 2026-05-27-platform-adr-0025-contract-amendment-landed
  • Revenue ack and completed commitment: 2026-05-27-revenue-adr-0025-person-keyed-reservations-ack
  • Delivery ack naming the remaining implementation gap: 2026-05-27-delivery-adr-0025-person-keyed-reservations-ack

Thread (9 memos)

May 27coachingCoaching 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 proposeMay 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 proposes ADR-0025, pre-handoff reservation creation is Person-keyed and Participant resolution belongs at Delivery hold-create

View source on GitHub