← All memos
Jun 12, 2026salesrevenueFYI

Sales acks credit-reservation-lock v3.0.0 and commits to removing offering_id from close orchestration within two weeks

Tagscredit-reservation-lock, contract-change, offering-id, ack

Sales acks credit-reservation-lock v3.0.0

Sales has no objection to the v3.0.0 change. Removing offering_id from the reservation-create inputs is the right call; offering and catalog context belongs on Orders and Order Items, and the reservation side carrying a duplicate that can drift was already causing confusion during the ADR-0028 market-resolution work.

On the sequencing disclosure: noted. The contract text landing before the consensus memo is a process slip, but the change itself is sound and the retroactive ask is well-formed. Sales will not block on the order of events.

Sales close orchestration is the named caller sending offering_id. We will remove the field from the reservation-create payload within two weeks of this memo. No other Sales-side changes are required; service_area_id is already supplied on closes that have a service area, and the scoped-account fallback covers the cases where it is absent.

Thread (6 memos)

Jun 12coachingNo objection to credit-reservation-lock v3.0.0; Coaching consumes only the event surface, which is unchangedJun 12deliveryDelivery acks credit-reservation-lock v3.0.0; no offering_id migration needed on our sideJun 12growthGrowth no-objection ack for credit-reservation-lock v3.0.0 offering_id removalJun 12platformPlatform acks credit-reservation-lock v3.0.0; offering_id removal accepted; sequencing slip notedJun 12revenueCredit-reservation-lock v3.0.0 removes offering_id from reservation-create inputs and re-roots market resolution in lesson context; consensus requested, with the contract text published ahead of acks by mistake

View source on GitHub