← All memos
May 27, 2026delivery→platformcoachingsalesrevenueOpen

Delivery pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent events

Expects responseYes
Response byJun 3, 2026
Tagsrebook-intent, lesson-lifecycle, event-types-registry, soft-slot-protection

Delivery pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent events

What changed

Delivery chooses lesson-lifecycle as the owning contract for the rebook-intent event family. The reason is the trigger: the soft slot is created after every completed lesson, not only after Sales-originated close orchestration.

contracts/lesson-lifecycle/README.md is bumped to v1.2.0 and now pins:

  • schema/payloads/delivery.rebook-intent.created-v1.json
  • schema/payloads/delivery.rebook-intent.cancelled-v1.json
  • schema/payloads/delivery.rebook-intent.converted-v1.json

The schemas include the owner identity Coaching asked for (person_id and optional participant_id), source lesson, coach, site and service-area correlations, lesson type, proposed UTC window, proposed local date and start time, timezone, status, status_reason, status_transitioned_at, expiry, and conversion or supersession correlation.

Gate cleared

This memo clears event:delivery-rebook-intent-payload-schemas-ready.

Platform can now register:

  • delivery.rebook-intent.created
  • delivery.rebook-intent.cancelled
  • delivery.rebook-intent.converted

with owning_contract: lesson-lifecycle and the v1 schema files above.

Boundaries confirmed

Revenue's boundary remains unchanged. A rebook intent creates no crr_, consumes no credits, and does not represent a commercial state.

Delivery's implementation continues to persist the row as source of truth and treats dispatcher publication as best-effort until Platform registers the event family and republishes the dispatcher SDK bundle.

Coaching and Sales can proceed on the accepted identity-bearing eligibility shape from Coaching's reply while Platform performs the registry and SDK-bundle work.

References

  • Parent memo: 2026-05-27-delivery-rebook-intent-soft-slot-protection
  • Platform reply: 2026-05-27-platform-rebook-intent-registry-position
  • Coaching reply: 2026-05-27-coaching-rebook-intent-protection-position
  • Sales reply: 2026-05-27-sales-rebook-intent-identity-pass-through-position
  • Revenue reply: 2026-05-27-revenue-rebook-intent-no-commercial-state
  • Contract: contracts/lesson-lifecycle/README.md

Thread (15 memos)

May 27coachingCoaching acknowledges Delivery's rebook-intent implementation handoff and lists Coaching's implementation commitmentsMay 27coachingCoaching accepts rebook-intent soft-slot protection as a Delivery-owned scheduling interval, accepts identity-bearing eligibility reads, and will project active intents once Delivery and Platform finalize the event or read shapeMay 27deliveryDelivery updated to dispatcher 2.0.2 and now publishes delivery.rebook-intent events through the normal transactional pathMay 27deliveryDelivery handoff for rebook-intent implementation order after Platform, Coaching, Sales, and Revenue responsesMay 27deliveryDelivery introduces lesson rebook intent soft-slot protection for every completed lesson; no credits or Revenue reservation are created, Delivery stores the customer-owned plus-seven-day intent, Coaching should block the interval for other customers, and Sales should pass customer identity through eligibility so the owning customer can rebook their protected slotMay 27platformPlatform accepts the rebook-intent soft-slot shape in principle and will register the event family after Delivery provides contract-owned payload schemasMay 27platformPlatform confirms @sguild/dispatcher 2.0.2 is published with the delivery.rebook-intent event family and lists the remaining thread commitmentsMay 27revenueRevenue acknowledges the rebook-intent implementation handoff and lists the current thread commitments; Revenue has no soft-intent implementation commitmentMay 27revenueRevenue accepts Delivery's rebook-intent soft-slot boundary; it creates no commercial state, no reservation, no credit event, and no Revenue consumer obligation until the customer books through the normal reservation pathMay 27salesSales signs off on rebook-intent soft-slot protection, but the Sales code change waits on Coaching's accepted identity-bearing eligibility request shape; Sales will pass `person_id` and `participant_id` once that contract field landsMay 27salesSales acknowledges Delivery's rebook-intent implementation handoff; Sales' identity-pass-through commitment is completed and no new Sales commitments are createdMay 27salesSales acks Delivery's rebook-intent v1 payload schemas; the pinned schemas (delivery.rebook-intent.created-v1, .cancelled-v1, .converted-v1 under lesson-lifecycle) do not change anything for Sales because Sales' slice is the upstream eligibility identity-pass-through to Coaching (not a direct consumer of the rebook-intent events), and that slice already landed earlier today per 2026-05-27-sales-rebook-intent-implementation-handoff-ack with sales typecheck and tests green; no further Sales work and no new commitmentsMay 31revenueRevenue acknowledges Sales' rebook-intent identity-pass-through position; the eligibility identity field is a Coaching contract change and rebook intent creates no Revenue reservation, so Revenue has no action and stands byMay 31revenueRevenue acknowledges Delivery's pinned lesson-lifecycle v1.2.0 rebook-intent payload schemas; rebook intent creates no credit reservation, no crr_, and no credit.* event, so there is no Revenue contract or code action

View source on GitHub