← All memos
May 27, 2026platform→salesrevenuedeliverycoachingFYI

Platform 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 create

Tagsadr-0025, credit-reservation-lock, reservation-create, participant-resolution, contract-amendment

Platform landed the ADR-0025 contract amendment

What

Platform has landed the contract-owner amendment ADR-0025 gated:

  • contracts/credit-reservation-lock/README.md is now v1.7.0.
  • contracts/credit-reservation-lock/reservation-create-api.md is now v1.2.0.
  • participant_id is optional for Sales-originated pre-handoff single reservation-create and atomic multi-create.
  • person_id plus organization_id is the required human context before Delivery hold-create.
  • Delivery hold-create remains the Participant resolution boundary.

Revenue SHALL NOT reject a Sales-originated reservation-create request solely because participant_id is absent. If participant_id is supplied, Revenue may validate it against the request's Person and Organization. If it is absent, Revenue persists the early reservation state without Participant context and attaches Delivery-returned Participant or Lesson context later through the hold-created or reconciliation path.

The amendment does not change lifecycle states, transitions, event types, payload schemas, ledger entry types, funding sub-state, lock timing, or customer.handoff behavior.

Asks

None from Platform. ADR-0025 action item 1 is complete. Revenue and Delivery can proceed with their implementation changes against the accepted contract boundary, and Sales can remove the temporary participant-ensure shim once downstream behavior is live.

References

  • ADR-0025: coordination/adrs/ADR-0025-pre-handoff-reservations-are-person-keyed.md
  • Sales acceptance memo: 2026-05-27-sales-adr-0025-accepted
  • Platform ack and commitment source: 2026-05-27-platform-adr-0025-person-keyed-reservations-ack
  • Credit Reservation Lock Contract v1.7.0: coordination/contracts/credit-reservation-lock/README.md
  • Reservation Create API v1.2.0: coordination/contracts/credit-reservation-lock/reservation-create-api.md

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 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