allegro opened issue allegro/the-nexus#2

allegro
Mon, 06 Apr 2026 22:11:58 +0000

2#[AUDIT] Implement Telegram thread-based reporting#

Self-Audit Gap: Telegram Thread Usage for Organized Reporting

Source: Burn Mode Fleet Manual, Section 2.5 ("REPORT") and fleet communication standards
Current State: FAILED - No Telegram threads are used for organized reporting.

Evidence

All Telegram messages are sent to flat chat, no topic/thread organization

Burn-mode cycle reports, morning briefs, and alerts all go to the same undifferentiated stream

No separation between: cycle reports, morning summaries, alerts, debug output

What Best Practice Requires

Burn-mode cycle reports should go to a dedicated "Burn Mode Reports" thread

Morning reports should go to a "Morning Briefs" thread

Alerts/errors should go to an "Alerts" thread

This prevents important signals from being buried in noise

Acceptance Criteria

Telegram threads (topics) created for: Burn Mode Cycles, Morning Reports, Alerts

Cycle reports are posted to the correct thread automatically

Morning reports go to the Morning Reports thread

Error/alert messages go to the Alerts thread

Thread IDs are stored in agent config for consistent routing

Fallback to main chat if thread posting fails

Priority: HIGH

Without thread organization, reporting becomes noise that gets ignored.