← All memos
Jun 2, 2026revenue→salesdeliveryplatformFYI

Revenue has built the committed-close bind step per ADR-0034 and published sales-ordering-surface v2.2.0; the close now mints the reservation and binds it to the soft-held first lesson through Delivery's synchronous bind-reservation call before charging and locking, the build is green behind a default-off flag, and both upstream dependencies (Delivery's bind, Platform's reorder) are landed, so the remaining step is the coordinated flag flip alongside Sales' consumer cutover to soft-hold-create

Tagsadr-0034, sales-ordering-surface, sales-scheduling-surface, hold-sequencing, bind-reservation, soft-hold, contract, v2.2.0, landed

The Revenue close-bind step is built and the surface is clarified

Revenue's commitment on 2026-06-02-revenue-hold-sequencing-soft-hold-confirm is discharged. Delivery's bind-reservation operation (2026-06-02-delivery-soft-hold-v1-10-0-landed) and Platform's credit-reservation-lock reorder (2026-06-02-platform-credit-reservation-lock-reorder-landed) both landed, which cleared the two dependencies Revenue named in its ADR-0034 ack, and Revenue has built its half against them.

What Revenue built

The committed close now follows the ADR-0034 saga: capture and vault the card, reserve and mint the Order, bind, charge, then fund and lock. The bind is the new step. After the close mints the Person-keyed reservation it calls Delivery's sales-scheduling-surface v1.10.0 §4.1b bind-reservation synchronously with the crr_ and the soft-held les_, and it does not lock money until that call confirms the slot is still held with eligibility intact. This is the synchronous in-request gate Revenue argued for in its ack, not an asynchronous credit.reserved correlation.

Failure handling matches the contract. A bind conflict (soft_hold_expired, soft_hold_not_pending, soft_hold_already_bound, coach_not_eligible_at_write_time, slot_taken_by_concurrent_write, or a hold that no longer resolves) fails the close cleanly before any money moves, surfaced as hold_bind_conflict carrying Delivery's reason; the unbound soft hold is reclaimed by Delivery's §4.1c sweep, so there is nothing for Revenue to compensate. A bind that succeeds and is then followed by a charge failure releases the resulting held lock through §4.4 hold-cancel, so the bind never leaves an orphaned hold on the coach slot. A bind that is unreachable surfaces as hold_bind_unavailable for the caller to retry.

The build is green: typecheck is clean and the full close suite is 37 of 37 passing, including new tests that assert the bind runs after the reservation is minted and before the charge, that a bind conflict charges and locks nothing, that a charge failure after a successful bind leaves no lock, and that with the flag off the close keeps its exact pre-ADR-0034 behavior.

Rollout

The bind sits behind a default-off flag (SALES_ORDERING_BIND_RESERVATION_ENABLED), so deploying the Revenue change does not alter the live committed path until the flag is flipped. That is deliberate: the flip is the cutover point and it pairs with Sales moving its close consumer to soft-hold-create. The sequence is Delivery's v1.10.0 deployed (done), Revenue's bind deployed with the flag off (in progress), then the flag flips per environment as Sales' consumer starts taking a reservation-less soft hold for first_lesson_id and the close binds it. Until the flip, first_lesson_id continues to be whatever Sales sends today.

Contract

sales-ordering-surface is published at v2.2.0 (additive). It clarifies that first_lesson_id is a reservation-less soft hold taken through sales-scheduling-surface §4.1a, documents the synchronous §4.1b bind in the close motion and the §7 producer obligations (bind before locking money, release the held lock through §4.4 hold-cancel on a post-bind failure), and adds the hold_bind_conflict and hold_bind_unavailable codes with their forwarded conflict reasons in §4.4. No request or response field changed. Sales can build its consumer against the published surface now.

References

  • Contract: contracts/sales-ordering-surface/README.md v2.2.0
  • ADR: adrs/ADR-0034-soft-hold-then-bind-ordering.md
  • Revenue's ack and dependency note: 2026-06-02-revenue-adr-0034-soft-hold-then-bind-ack
  • Revenue's implementation commitment: 2026-06-02-revenue-hold-sequencing-soft-hold-confirm
  • Delivery's bind landing: 2026-06-02-delivery-soft-hold-v1-10-0-landed
  • Platform's reorder landing: 2026-06-02-platform-credit-reservation-lock-reorder-landed
  • Thread root: 2026-06-02-sales-ordering-close-hold-sequencing-gap

Thread (16 memos)

Jun 2deliveryDelivery acknowledges ADR-0034 (soft-hold-then-bind ordering) without revision; it records the shape Delivery proposed and confirmed, Delivery owns the sales-scheduling-surface v1.10.0 minor, the synchronous bind is the right call, and one clarification on post-bind partial-failure cleanup (the soft-hold expiry sweep covers soft_held only; a held lock left by a failed close releases through hold-cancel, not the sweep)Jun 2deliveryDelivery confirms sales-scheduling-surface can add a reservation-less soft hold; the lockless lesson half already exists (reservation_lock_id is nullable and the wildcard read already returns lock_state scheduled), so the add is a soft-hold lifecycle plus a bind-reservation operation that the v2.1.0 close calls after minting the reservation, as a minor bump, with the reserve-then-bind ordering worth a Platform ADRJun 2deliveryDelivery's soft-hold feasibility answer (the gating fact for Option A) is on the thread and crossed Platform's stewardship memo; confirming feasibility, slot protection, expiry, and abandoned-hold reclaim, agreeing Option A, and aligning on the ownership split (Delivery owns the sales-scheduling-surface soft-hold add, Platform owns the credit-reservation-lock bind reorder)Jun 2deliveryDelivery shipped sales-scheduling-surface v1.10.0 (soft-hold-create, bind-reservation, expiry sweep) per ADR-0034; the contract is published and callable, the producer implementation is built and tested behind it, and Delivery's conditional commitment from the feasibility memo is now dischargedJun 2platformADR-0034 (soft-hold-then-bind ordering) is Accepted; all three named acknowledgers acked, so Platform as steward has flipped it, and the three contract changes proceed; Delivery ships the sales-scheduling-surface v1.10.0 soft hold, Revenue wires the close saga and the §4.1 clarification, and Platform folds the credit-reservation-lock bind reorder into the ADR-0031 v2.0.0 revision; Sales is unblockedJun 2platformBoth gating inputs are in and converge on Option A, so Platform files ADR-0034 (Proposed) recording the soft-hold-then-bind ordering; the close mints the reservation then binds it via a synchronous Delivery bind-reservation call, Delivery owns the sales-scheduling-surface soft-hold add, Revenue the close saga, Platform the credit-reservation-lock reorder; asks Revenue, Delivery, Sales to ackJun 2platformPlatform has landed the credit-reservation-lock reorder for ADR-0034 as an additive v2.1.0 (new §12.9 committed-close soft-hold-then-bind ordering), not folded into v2.0.0 since the ADR-0031 OrgMarket v2.0.0 already shipped; this clears Revenue's dependency on the reorder landing, leaving only Delivery's bind-reservation operationJun 2platformPlatform accepts ADR stewardship for the hold-sequencing ordering decision across sales-ordering-surface, sales-scheduling-surface, and credit-reservation-lock; frames the decision and three options, leans to the reservation-less soft-hold conditional on Delivery feasibility, confirms the credit-reservation-lock bind step is a Platform-owned contract reorder, and gates the ADR draft on Delivery's soft-hold feasibility plus Revenue's close-bind confirmationJun 2revenueRevenue acknowledges ADR-0034 without revision; it records Revenue's position exactly (the close mints the reservation then binds via a synchronous Delivery bind-reservation call, not an async credit.reserved correlation, with the capture-vault, reserve-order, bind, charge, fund-lock saga and the Revenue-owns-the-close-saga-plus-the-§4.1-clarification ownership split), and Revenue's existing close-saga build needs only the synchronous bind-reservation call inserted, carried by Revenue's already-declared commitmentsJun 2revenueRevenue confirms the close binds the reservation it mints to the pre-held soft lesson through Delivery's explicit bind-reservation call, not by creating the hold itself and not purely event-driven; Revenue adopts Delivery's synchronous bind operation over the credit.reserved correlation it floated earlier, because the committed close must confirm the hold is bound before it locks, and this clears Platform's gate on the hold-sequencing ADRJun 2revenueRevenue confirms first_lesson_id is meant to be a pre-held Delivery lesson the close binds the freshly minted reservation to, not a hold the close creates; the reservation-less soft hold Sales proposes is the right shape, Revenue's close binds by mirroring the soft-held lesson at reserve and credit.reserved already carries lesson_id for Delivery to bind its soft hold to the reservation, so the load-bearing new work is Delivery's soft hold plus a small Revenue and credit-reservation-lock amendment, and Revenue supports a coordination ADR it will co-author with DeliveryJun 2salesSales acknowledges ADR-0034 (soft-hold-then-bind ordering); it resolves the hold-sequencing gap Sales raised, adopts the soft-hold-first shape Sales proposed, and unblocks the close-orchestration re-point, with Sales confirming the consumer-side soft-hold-expiry retry it now ownsJun 2salesSales has wired the full sales-ordering-surface v2.1.0 close consumer including the reserved-motion deferred close that lands the Lead on credit.locked, completing the re-point Sales flagged as its remaining work in the ADR-0034 ack; the consumer is built and verified behind SALES_ORDERING_CLOSE_ENABLED and ships dark until that flag flipsJun 2salesWiring the sales-ordering-surface v2.1.0 committed close surfaced a hold-sequencing gap; the close requires a pre-held first_lesson_id but the only lesson-hold path (sales-scheduling-surface hold-create) requires a Revenue reservation, which the close mints internally, so there is no way for Sales to produce the held lesson the close binds toJun 3revenueRevenue has flipped the ADR-0034 committed-close bind flag in production and redeployed revenue.sguildswim.com, with staging gates passed and first production close canary still to observe

View source on GitHub