Telegram Noise Policy

Core rule

Telegram only on breakage. Reserve the channel for actual failure; routine digests follow the wrap-up protocol only. Noise trains the user to ignore it.

What fires Telegram

Trigger	Source	Severity
Delegation ratio <40%	session-end-check.sh	SEVERE
Persistent <40% over 3 sessions	Orochimaru	systemic debt
Subagent runtime >15 min	runtime benchmark	ESCALATE
Subagent runtime >20 min	runtime benchmark	KILL-ELIGIBLE
Burnout flag	AllMight burnout alert	calendar-triggered
Credential exposure	Itachi sweep	SEVERE

80/20 gate (enacted 2026-06-08)

Telegram notification pipelines apply an 80/20 filter. Only the 20% highest-leverage signals push to Michael — the rest logs silently to vault.

Pass-through domains (the vital 20%):

Domain	Commander	Signal types that push
Health	Allmight	Smoking pattern alerts, health threshold breaches, burnout flags
Finance	Bulma	Spend anomalies, large transactions, budget threshold breaches
Career	Zuko	Job application updates, interview scheduling, cert deadlines
Fitness	Zoro	Workout streak breaks, plateau detection

Orochimaru enforcement: Orochimaru audits notification volume per commander per week. Commanders outside the pass-through list who generate >3 Telegram pushes in a 7-day window get the 80/20 filter forced — their notifications downgrade to vault-only logging until the next Orochimaru review. Orochimaru decides ongoing who needs the filter applied.

Everything else: logged to the-government/information_reference/logs/ or audit reports. No Telegram push.

What does NOT fire Telegram

• Routine session summaries — these go to handover files
• Task completions — logged to CT100 postgres
• Audit findings below SEVERE — written to the-government/information_reference/audit-reports/
• Knowledge fold outputs — filed via Diataxis into the-government
• Any commander output outside the 80/20 pass-through list (unless Orochimaru exempts)

Credential discipline in Telegram

Never echo a credential value in any Telegram message. Detect → redact → surface the name of the exposed credential → wait for Michael.

Channel routing

Channel	Purpose
Minato (primary)	Interactive advisor — Michael's main Telegram interface to Hinata
Alert channel	Automated SEVERE flags only
Session crons	07:03 morning · 12:02 midday · 18:03 evening · review · Orochimaru scout · monthly audit

Raw message handling (Canary rule)

Raw Telegram exports (YYYY-MM-DD-telegram-*.md) are never stored in Commander folders. They must be either:

• Extracted (signal → commander knowledge-base or the-government reference)
• Moved to inbox/done/

The Commander folder contains only the extracted knowledge or decision, never the raw message file.

---

Extracted from supreme-court/runtime/runtime_workflow §11 + federation/captain_canary-organiser_context