Skip to content

Record Workshop notification delivery evidence - #858

Merged
dcellison merged 1 commit into
mainfrom
docs/workshop-third-authority-review
Aug 12, 2026
Merged

Record Workshop notification delivery evidence#858
dcellison merged 1 commit into
mainfrom
docs/workshop-third-authority-review

Conversation

@dcellison

Copy link
Copy Markdown
Owner

Summary

  • record the successful installed notification-group Workshop outbox qualification
  • record clean post-delivery projection and direct-chat JSONL parity evidence
  • record that the unchanged GitHub webhook route still delivered to the same Telegram group
  • conduct the third canonical conversation authority review
  • keep worker registration and production routing cutover on hold until lifecycle ownership is explicit
  • define the next bounded, production-unused runtime-owner milestone

Installed evidence

  • the deployed bootstrap reported one Workshop, two humans, three Telegram bindings, six channel memberships, and one agent
  • notification-group delivery dlv_81b5d54eb64355eaad951e21105411fd was prepared without sending
  • the exact selected delivery succeeded on attempt 1 of 3
  • the recognizable qualification message appeared in the configured Telegram group
  • post-delivery status remained clean at 39 canonical and projected messages, zero replay mismatches, 38 matched direct-chat JSONL records, zero missing or unmatched records, and one direct parity channel
  • a GitHub webhook redelivery subsequently reached the same group through the unchanged legacy route

Authority decision

The message/outbox transaction and installed direct and group transport targets now pass. Worker registration remains held because Kai does not yet own worker startup, readiness, unexpected failure, and graceful shutdown as an explicit lifecycle contract. Existing direct Telegram sends remain authoritative for replies, schedules, GitHub and generic webhooks, files, and voice.

Next bounded milestone

Define a production-unused runtime owner around the existing Telegram worker. It must provide single-task ownership, recovery-before-readiness, visible failure propagation, deterministic start/stop behavior, and graceful shutdown without cancelling an in-flight external send. It must remain unwired from main.py and preserve all production delivery behavior until a later focused cutover review.

Validation

  • documentation-only change
  • git diff --check passes
  • all evidence values are copied from the installed qualification and status output

@dcellison
dcellison merged commit 46b10f7 into main Aug 12, 2026
1 check passed
@dcellison
dcellison deleted the docs/workshop-third-authority-review branch August 12, 2026 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants