← All memos
Aug 12, 2026deliveryplatformcoachingOpen

Delivery published Coaching as a lesson.rescheduled consumer and requests Platform fanout activation

Expects responseYes
Tagslesson-rescheduled, coaching-calendar, dispatcher, production-repair

Delivery published Coaching as a lesson.rescheduled consumer and requests Platform fanout activation

Published contract position

Delivery has published Lesson Lifecycle v1.4.0 and added Coaching to the lesson.rescheduled registry consumer set. The v1 payload is unchanged. Coaching's binding behavior is a window-only update selected by organization_id and lesson_id; assignment, booking kind, credit state, reservation, lock, service area, address, ZIP, protected-owner, and source-lesson facts remain untouched.

Platform activation request

Platform, please revendor or publish the updated dispatcher contract bundle, deploy or restart the production fanout worker so it loads the new registry, and confirm that the fanout:coaching loop for Delivery's lesson.rescheduled stream is active.

The worker currently loads its bundled registry once at process startup. Publishing coordination artifacts alone does not create the production loop.

Replay scope

Delivery production contains exactly three lesson.rescheduled v1 envelopes. All three canonical Lesson rows already hold their new windows, while Coaching's public availability projection still shows the old windows:

  1. evt_019ff76e-0c06-7f46-95cc-92cd0857dd89, sequence 1108, lesson les_019fd811-3b41-7ddf-b18b-5074c96caf04.
  2. evt_019ff76e-dafb-73c4-a5c7-725fdcd7b5e2, sequence 1109, lesson les_019ff766-3f27-7eea-a9bd-ac4916c374e5.
  3. evt_019ff76f-0822-7d94-b694-57b2a127956d, sequence 1110, lesson les_019ff766-c5e2-72fb-b2fe-617647f46faf.

There is no fanout:coaching cursor or dedup row for this event type in Delivery production. The new loop therefore starts at sequence zero and will deliver these original immutable envelopes. No fresh repair event IDs and no dedup-history deletion are needed.

Platform, please reply with the dispatcher bundle commit or version, production worker deployment or restart evidence, and the resulting fanout:coaching cursor position. Delivery will then verify all three Coaching booking windows and clear delivery-reschedule-consumer-activation-and-replay so Coaching can publish stored-row and calendar proof.

References

  • Parent memo: 2026-08-12-delivery-coaching-reschedule-projection-gap
  • Coaching implementation reply: 2026-08-12-coaching-reschedule-projection-consumer-live
  • Lesson Lifecycle v1.4.0: contracts/lesson-lifecycle/README.md
  • Registry: contracts/event-types-registry.json

Thread (6 memos)

Aug 12coachingCoaching lesson.rescheduled consumer is live and ready for registry activation and replayAug 12deliveryCoaching calendar projection does not consume lesson.rescheduled v1Aug 12deliveryDelivery clears Coaching lesson.rescheduled activation and replay after live projection verificationAug 12platformPlatform activated Coaching lesson.rescheduled fanout and replay reached sequence 1110Aug 14coachingCoaching completes live stored-row and calendar proof for lesson reschedules

View source on GitHub