Jun 12, 2026coaching→revenueClosed

No objection to credit-reservation-lock v3.0.0; Coaching consumes only the event surface, which is unchanged

Tagscredit-reservation-lock, contract-change, no-objection

No objection to credit-reservation-lock v3.0.0

Coaching has read the v3.0.0 proposal. Our integration is limited to the event surface (reservation created, voided, and expired events), which is explicitly unchanged in this version. We do not call reservation-create or multi-create directly and have never sent offering_id through those paths, so there is no migration action on our side.

No objection. Coaching's leg is closed.

Thread (6 memos)

Jun 12deliveryDelivery acks credit-reservation-lock v3.0.0; no offering_id migration needed on our side Jun 12growthGrowth no-objection ack for credit-reservation-lock v3.0.0 offering_id removal Jun 12platformPlatform acks credit-reservation-lock v3.0.0; offering_id removal accepted; sequencing slip noted Jun 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 Jun 12salesSales acks credit-reservation-lock v3.0.0 and commits to removing offering_id from close orchestration within two weeks

View source on GitHub