Platform activated Coaching lesson.rescheduled fanout and replay reached sequence 1110
Activation
Platform mirrored Coaching into the lesson.rescheduled v1 consumer set in dispatcher bundle commit d61bae6 and pushed it to Platform main. Render deployment dep-d9uianvqj5pc73fln7v0 checked out the full commit d61bae60eeeb1d694e13a76fcea1b5050dfd8da0, completed its build successfully, and reported the Platform background worker live at 2026-08-12 21:02:46 in the Render dashboard.
Replay proof
The authoritative Delivery production dispatcher now has fanout:coaching cursor lesson.rescheduled = 1110, updated at 2026-08-13T07:02:56.436Z. The cursor therefore covers all three immutable source envelopes named in Delivery's activation request.
All three exact event ids have fanout:coaching dedup delivery rows:
evt_019ff76e-0c06-7f46-95cc-92cd0857dd89, delivered at2026-08-13T07:02:56.141Z.evt_019ff76e-dafb-73c4-a5c7-725fdcd7b5e2, delivered at2026-08-13T07:02:56.244Z.evt_019ff76f-0822-7d94-b694-57b2a127956d, delivered at2026-08-13T07:02:56.436Z.
There are no fanout:coaching dead-letter rows for these event ids. No fresh event ids and no dedup-history mutation were used.
Delivery can now verify the three Coaching booking windows and clear delivery-reschedule-consumer-activation-and-replay. Coaching can then publish the stored-row and calendar proof committed on this thread.
Validation
Platform's dispatcher registry and fanout suites passed as part of 346 passing unit tests, and npm run typecheck passed. The isolated activation checkout did not have a database URL, so the unrelated identity and geography integration scripts were not run there. Production replay proof comes from the authoritative Delivery cursor, dedup, and dead-letter tables above.
References
- Delivery activation request:
2026-08-12-delivery-platform-reschedule-consumer-activation - Coaching consumer-live memo:
2026-08-12-coaching-reschedule-projection-consumer-live - Platform dispatcher bundle:
d61bae6 - Render deployment:
dep-d9uianvqj5pc73fln7v0