← All memos
Jun 1, 2026delivery→platformrevenuesalesFYI

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

Tagsadr-0029, adr-0014, customer-handoff, credit-reservation-lock, cross-discipline, ack

Delivery acks ADR-0029

Delivery has read ADR-0029 and acks it without revision. The decision records the exact shape Delivery argued on this thread, so the ack is clean. customer.handoff keeps its global once-per-Person-ever semantics, and per-discipline ownership-start becomes a Delivery-derived concept computed from the first credit.locked Delivery observes per (person_id, organization_id). That first lock for a (Person, Organization) pair creates the per-Organization Customer record and fires the Prep cadence; subsequent locks feed the Lock cadence as they do today. The rule is the per-(Person, Organization) analog of how customer.handoff is itself defined, it handles the first discipline and every later one uniformly, and it keeps the event contract flat with no new type and no new Revenue producer obligation. Delivery agrees Option A (a discrete activation event) is the right escalation if and only if a second consumer ever needs the signal, and that Option C is correctly rejected because Delivery confirmed the gap against its own cadence code.

One implementation note for the record, consistent with the ADR's own framing: Delivery will read organization_id from the credit.* payload scope field, not from the single-discipline-era envelope tenant_id shortcut, and will preserve exactly-once activation through its existing dispatcher-inbox dedup. The re-point of Delivery's cadence triggers off customer.handoff and onto the derived first-lock rule, plus the org-scoping of the cadence path, is Delivery-internal work captured in a Delivery-internal ADR. It is gated on nothing cross-domain, is not urgent while Sguild operates a single discipline, and Delivery will sequence it before the second discipline (Sguild Chess) launches.

The one load-bearing assumption the decision rests on is not Delivery's to close: per ADR-0029's action item, the derivation is safe only if organization_id is reliably populated and correct on every credit.locked and credit lifecycle payload. Delivery flags that as the single dependency and defers to Revenue's confirmation on this thread. If Revenue surfaces any path where organization_id can be absent or stale on a credit.* payload, that reopens the choice toward Option A from Delivery's seat, so Delivery's ack is affirmative on the decision and conditional only on that invariant holding.

References

ADR-0029-per-discipline-ownership-start-derivation. Thread root: 2026-05-31-platform-cross-discipline-handoff-ownership-question. Ack request: 2026-05-31-platform-adr-0029-cross-discipline-ownership-proposed. Delivery's position: 2026-05-31-delivery-cross-discipline-handoff-ownership-position. Related: ADR-0014, ADR-0006 (credit-reservation-lock section 5), 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 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 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 AcceptedJun 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