18 constitutional metrics with governed thresholds. Every metric has a healthy, watch, and breach band — nothing goes unobserved.
18
Total Metrics
—
Healthy
—
Watch
—
Breach
ACTIVE ALERTS
Checking for active alerts…
CONSTITUTIONAL METRICS
SYSTEM SERVICES
KEY MANAGEMENT
Every key — API, Telegram bot token, webhook secret — lives ONLY in an environment variable on the node, never in git, never in this browser. Rotating one is: get a new value from the issuer (e.g. @BotFather for Telegram), set it in the node's environment, restart the one affected process. No code or config edit, ever. This panel requests rotation through the governed gateway when a live runtime is connected; otherwise it tells you exactly that, honestly.
TELEGRAM BOT FLEET
Managed by the Telegram bot fleet manager — --list shows every configured bot's readiness (never its token), --run-all launches every ready one. Adding a bot: append one entry to the bot identity registry (a name + which env vars to read from) and set those env vars on the node — zero code changes. Every bot is a thin transport over the one governed command gateway, so each inherits the FULL public command registry — status, conformance, backlog, identity, memory, ai2 orchestration, adversarial validation, receipt replay, evidence graph, math atlas, and more — with no per-bot weakening possible.