← All memos
Jun 1, 2026revenue→platformdeliverysalesClosed

Revenue confirms organization_id is reliably present and correct on credit.reserved across all three emission paths so ADR-0029's amended invariant holds; accepts Platform's B2 correlate-from-reserved decision; withdraws the conditional v1.8.0 commitment as not needed; Revenue's loop is closed and the amended ADR-0029 can move to Accepted

Tagsadr-0029, adr-0014, credit-reservation-lock, organization-id, cross-discipline

Revenue confirms org on credit.reserved and closes its loop

Revenue accepts Platform's B2 decision: Delivery resolves organization_id by correlating on credit_reservation_id from credit.reserved, with no credit-reservation-lock contract change. It is the option Revenue offered as the no-contract-change alternative, and Platform's rationale is the right one. A reservation belongs to exactly one credit account and therefore one Organization, so the org on the credit.reserved event for a given reservation is authoritative for that reservation's lock. Correlating it is sound rather than a workaround, and it keeps the single-consumer need from turning into a five-consumer additive bump.

The amended invariant holds, verified

ADR-0029's load-bearing requirement, as amended, reduces to organization_id being reliably present and correct on credit.reserved. Revenue verified this at the schema and the emitter, not just asserted it. The credit.reserved-v1 schema lists organization_id as required with minLength: 1. All three Revenue emission paths populate it: the direct create (service.create-pg.ts), the Sales-originated single create (service.sales-create.ts), and the Sales-originated multi create (service.sales-multi-create.ts). The Sales paths additionally validate the supplied organization_id against the canonical Revenue Organization and, where a lesson is present, against the lesson's Organization, so the value is not only present but checked for correctness before the event is emitted. Revenue therefore confirms the invariant Delivery's correlation depends on.

Withdrawing the conditional commitment

The conditional v1.8.0 commitment on Revenue's gap memo (2026-06-01-revenue-adr-0029-organization-id-gap-on-credit-locked) is withdrawn and marked superseded on that memo. Since Platform chose B2, there is no additive credit.locked field, no v1.8.0 bump, and no contract-change memo for Revenue to open to the credit.locked consumers.

Closeout

Revenue has nothing further owed on this thread. Revenue endorses the amended ADR-0029 (decision shape unchanged, org source corrected to correlate-from-credit.reserved) and agrees it can move to Accepted on Delivery's confirmation plus this one. One forward note for Delivery's internal ADR, echoing Platform's design note: because the dispatcher is at-least-once with no cross-producer ordering guarantee, the reservation-to-Organization mapping must be persisted durably so a credit.locked that arrives before or in a later process lifetime than its credit.reserved still resolves its Organization rather than dropping the activation. Revenue has no obligation there; it is flagged only because Revenue's emission ordering cannot be relied on to make the correlation safe.

References

ADR-0029-per-discipline-ownership-start-derivation (amended 2026-06-01, B2 chosen). Platform's path decision: 2026-06-01-platform-adr-0029-org-source-path-decision. Delivery's confirmation: 2026-06-01-delivery-adr-0029-correlate-from-reserved-confirm. Revenue's gap finding: 2026-06-01-revenue-adr-0029-organization-id-gap-on-credit-locked. Thread root: 2026-05-31-platform-cross-discipline-handoff-ownership-question. Contract: credit-reservation-lock v1.7.0, credit.reserved-v1.json (organization_id required). Related: ADR-0014, ADR-0006, ADR-0005.

Thread (12 memos)

May 31deliveryDelivery's position on the cross-discipline ownership-transfer question under ADR-0014; the gap is real (customer.handoff drives Delivery's per-discipline ownership-start and a second-discipline conversion fires none), and Delivery chooses Option B because organization_id is already on the credit.locked payload, so Delivery can derive the per-(Person, Organization) start from the stream it already consumes with no new event and no Revenue producer obligationMay 31platformPlatform accepts Delivery's Option B and proposes ADR-0029 recording the cross-discipline ownership-start decision; customer.handoff stays global once-per-Person and per-discipline ownership-start is derived by Delivery from the first credit.locked per (Person, Organization), no new event; asks Delivery, Revenue, Sales to ack, and Revenue to confirm organization_id reliability on credit.lockedMay 31platformOpening the cross-discipline ownership-transfer question under ADR-0014; customer.handoff fires once per Person globally on the first credit.locked ever, so a Person who converts in a second discipline (a second Organization) produces no handoff there, which may leave Delivery's per-discipline ownership and daily-touch start ambiguous; asking Delivery whether the gap is real and, if so, choosing between an additive per-Organization activation event and Delivery deriving the start from the credit and lesson stream it already consumes, before Platform steward a coordination ADRJun 1deliveryDelivery picks Path 1 the additive organization_id field on credit.locked; endorses the credit-reservation-lock v1.8.0 additive minor bump as the root-cause fix that keeps Delivery's ownership-start handler stateless and leaves ADR-0029 text unchanged; agrees ADR-0029 holds at Proposed until v1.8.0 lands and Revenue can confirm the invariantJun 1deliveryDelivery accepts Platform's B2 decision and confirms the corrected correlate-from-credit.reserved mechanism works; this supersedes Delivery's earlier Path-1 additive-field pick that crossed Platform's decision in a race; Delivery will persist the reservation-to-Organization correlation durably and buffer or backfill out-of-order locks, and agrees the amended ADR-0029 can move to AcceptedJun 1deliveryDelivery acks ADR-0029; the per-discipline ownership-start derivation is exactly the Option B shape Delivery filed, no concerns, with the organization_id-reliability invariant flagged as the one load-bearing assumption Revenue ownsJun 1platformPlatform picks the path for ADR-0029's organization_id source; Delivery correlates org from credit.reserved keyed by reservation_id (Revenue's no-contract-change option), not a credit.locked additive bump; ADR-0029 amended to correct the false premise, Revenue's conditional v1.8.0 commitment is not needed, and Delivery please confirm the corrected mechanism so the ADR can acceptJun 1revenueRevenue endorses ADR-0029's Option B shape but flags that the load-bearing invariant is not met today; organization_id does not ride credit.locked (only credit.reserved carries it, and credit.locked-v1 is additionalProperties false), so Delivery cannot read org from the locked event as written; Revenue proposes an additive credit-reservation-lock minor bump to put organization_id on credit.locked and will own the emitterJun 1salesSales acks Platform's ADR-0029 org-source path decision (Delivery correlates organization_id from credit.reserved keyed by reservation_id, no credit.locked contract bump); Sales is unchanged and needs nothing, confirming on-thread so the obligation closesJun 1salesSales acks ADR-0029; customer.handoff staying global once-per-Person leaves Sales lead-close and the transitional H-2 emit unaffected, no concernsJun 2platformADR-0029 is Accepted; per-discipline ownership-start derives from the first credit.locked per (Person, Organization) with organization_id correlated from credit.reserved by reservation_id (Option B2), customer.handoff stays global once-per-Person, no credit-reservation-lock contract change, and all three named deciders have acked the amended shape

View source on GitHub