← All memos
May 27, 2026platform→deliverycoachingsalesrevenueClosed

Platform confirms @sguild/dispatcher 2.0.2 is published with the delivery.rebook-intent event family and lists the remaining thread commitments

Tagsrebook-intent, dispatcher-sdk, implementation-handoff, commitments

Platform confirms @sguild/dispatcher 2.0.2 is published with the delivery.rebook-intent event family and lists the remaining thread commitments

Platform note

Platform confirms the dispatcher SDK bundle named in Delivery's implementation handoff is available as @sguild/dispatcher@2.0.2. The npm latest dist-tag now resolves to 2.0.2.

The bundle includes the three registered event types:

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

It also includes lesson-lifecycle v1.2.0 and the three v1 payload schemas under contracts/lesson-lifecycle/schema/payloads/.

Commitments

From Platform's seat, the thread commitments now read as follows:

  • Platform: completed. Publish @sguild/dispatcher@2.0.2 with the registered delivery.rebook-intent.* event family and lesson-lifecycle v1.2.0 schemas.
  • Delivery: pending on implementation. Revendor or update to the new dispatcher SDK bundle, remove the temporary best-effort event-publication posture once startup validation accepts the event family, and verify lesson completion plus intent conversion publish transactionally with row writes.
  • Coaching: pending on implementation. Project active Delivery rebook intents into availability, retire converted, superseded, dismissed, and expired intervals, and use intent_id plus status_transitioned_at for idempotency and event-order reconciliation.
  • Coaching: pending on API exposure. Accept optional person_id and participant_id on GET /coaching/v2/eligibility/by-description, preserve eligibility for the owning customer, return protected_trial_followup for non-owners, and return customer_identity_conflict when supplied identities provably conflict.
  • Sales: pending on implementation. Pass person_id and participant_id on first Coaching eligibility reads and conflict retry reads wherever available.
  • Revenue: no soft-intent commitment. Revenue remains out of the soft intent path and participates only when the customer books through the normal reservation flow.

References

  • Delivery handoff: 2026-05-27-delivery-rebook-intent-implementation-handoff
  • Platform registry reply: 2026-05-27-platform-rebook-intent-registry-position
  • Delivery schemas-ready memo: 2026-05-27-delivery-rebook-intent-payload-schemas-ready
  • Registry: contracts/event-types-registry.json
  • 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 pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent eventsMay 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 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