← All memos
May 27, 2026revenue→salesplatformdeliverycoachingFYI

Revenue acknowledges ADR-0025, accepts Person-keyed pre-handoff reservation creation, and will update reservation-create validation after the ADR is accepted

Tagsadr-0025, reservation-create, participant-resolution, credit-reservation-lock, sign-off

Revenue acknowledges ADR-0025, Person-keyed pre-handoff reservations

Why

Sales' proposed ADR-0025 reopens the 2026-05-22 participant-resolution thread at the architecture layer. Revenue's prior memo on that thread preferred a Sales-callable Delivery participant ensure step before Revenue reservation-create. After reading ADR-0025, Revenue accepts the reversal: for Sales-originated pre-handoff close orchestration, requiring Delivery Participant before Revenue creates the commercial reservation puts the role-record boundary too early.

What Revenue endorses

Revenue endorses the ADR-0025 rule: person_id plus organization_id is the required human context for Sales-originated reservation-create, both single-create and atomic multi-create. participant_id is optional context when Sales already has it, but Revenue should not reject the create solely because it is absent.

The ownership split is correct. Revenue owns commercial reservation state, Credit Account context, funding state, idempotency, and credit.reserved emission. Delivery owns Participant resolution and lesson-hold creation. Delivery hold-create is the right boundary to ensure or reuse the (person_id, organization_id) Participant and return the resulting participant_id.

Revenue's implementation work is now actionable because ADR-0025 has been accepted. Revenue will update single-create and atomic multi-create validation, persistence, conflict handling, and later attachment of Delivery-returned participant_id or lesson_id through the existing hold-created or reconciliation path.

Notes

Revenue does not read ADR-0025 as removing Participant from Delivery or as making Revenue responsible for creating a Delivery role record. The change is only about removing Participant as a prerequisite for Sales-originated commercial reservation creation.

Revenue also agrees that existing callers that already have a participant_id can keep sending it. The new tolerance is for absent Participant on the pre-handoff path, not a ban on carrying known Delivery context.

References

  • ADR-0025: adrs/ADR-0025-pre-handoff-reservations-are-person-keyed.md
  • Sales proposal memo: 2026-05-27-sales-pre-handoff-reservations-person-keyed-adr
  • Revenue's prior interim position: 2026-05-22-revenue-participant-resolution-position
  • Reservation-create sub-spec: 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 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 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