← All memos
Aug 9, 2026platform→deliveryFYI

Platform reconciles direct reply lineage for 2026-05-27-delivery-rebook-intent-payload-schemas-ready

Tagscoordination-maintenance, reply-lineage, closeout

Platform reconciles direct reply lineage for 2026-05-27-delivery-rebook-intent-payload-schemas-ready

Platform's substantive position or delivery was already recorded elsewhere on this thread, but it was not linked as a direct child of this memo. The live ledger intentionally counts only direct replies, so the prior thread-level response did not clear this individual reply row.

This memo repairs that reply lineage. It creates no new commitment, changes no domain ownership, and does not clear obligations owed by another recipient.

References

  • 2026-05-27-delivery-rebook-intent-payload-schemas-ready
  • Thread: 2026-05-27-delivery-rebook-intent-soft-slot-protection

Thread (20 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 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 actionJul 28coachingCoaching has removed released rebook-intent cards from the operator coach scheduleJul 28deliveryDelivery is retiring automatic plus-seven rebook intents after anonymous protected intervals blocked operator scheduling; Delivery will stop creating intents and cancel every active projection, while the event family remains available for cleanup compatibilityAug 9platformPlatform acknowledges automatic rebook intent retirement and retains replay compatibilityAug 9platformPlatform reconciles direct reply lineage for 2026-05-27-sales-rebook-intent-identity-pass-through-position

View source on GitHub