Eight sections, and what each one holds
The whole console in one table, with the panel descriptions it ships and the pages behind each section.
| Section | What it holds | Pages |
|---|---|---|
| Dashboard | no panel | Capture health and archive at a glance |
| Content | Manage captured messages, publication consent, and review queues. | Messages · Capture · Consent · Retention · Reports · Evidence holds · Screening |
| Interaction | Control how CIND3R3LLA addresses people, responds, follows up, and archives. | Addressing · Guards · Follow-up · Welcome · Language · Memory · Replies · Nicknames · Consent behaviour · Voice · Archiving · Diagnostics |
| Moderation | Two escalation ladders, who is under a sanction, and the record of every step. | Rules · Active · Log |
| Book of Elii | no panel | The Book · The Recital · The Assembled Word · History |
| AI Control | Configure models, profiles, runtime policy, knowledge, safety, and operational testing. | Overview · AI Bot Setup · Access Control · Runtime · Models · Routing · Hardware · Telemetry · Personality · Privacy & Safety · Providers · Knowledge & RAG · Testing & Compare · Audit |
| Plugins | Review installed extensions and open each plugin control surface. | Overview · Channel Bridge (5 pages) · Music Library (4 pages) · Crypto Prices · Web Search |
| System | Manage core settings, security, embeds, and website delivery. | Settings · Security · Embeds · Backups |
Panel descriptions and page lists quoted from src/web/server.ts:439-805 (registerNav) and src/web/html.ts:209-308 (panel copy) · quoted in site material Block 3 section 1, gathered 2026-08-30 at main @ 5044c83
How it behaves
Hovering a section opens a panel; the sidebar then shows only that section's sub-pages, with the bot switcher above it on every page. Two sections carry no panel description because they need none: the Dashboard is the landing page, and the Book of Elii is the one section whose four pages name themselves.
Every page shows "N item(s) awaiting review" when open reports exist, so a queue cannot sit unnoticed behind a section nobody opened.
Where it lives, and why there is no link
The console is a second hostname on the same process as the public site, and this site links to it nowhere, deliberately: the hostname derives the passkey binding, and a public link to a passwordless sign-in page is the shape of a phishing target. An operator reaches it by typing its address.
Capture health and archive at a glance
What the dashboard shows the moment an operator signs in, and at what scope.
What is on it
- Five live counts across the deployment: messages, published, deleted, opted-in members and revoked consents. "Published" is the derived publication view, never a flag, so it cannot drift from what a member actually consented to.
- A banner comparing media receipts against the relay expiry, either naming failed and at-risk file receipts or saying all expected media arrived.
- Cards for messages by type, the last eight process errors, which reset on restart, and the last ten audited admin actions.
Per bot, and everything else
A bot status card carries a state badge, one line per room the bot is in or "in no room", when it last captured, and how long the process has been up. Rooms are per bot; everything else on this page is deployment-wide.
The bot switcher, and what scope you are in
Every page declares whether it is per bot, shared across the deployment, or mixed, and the switcher writes nothing at all.
The bot switcher sits at the top of the sidebar on every page, and choosing a bot writes nothing: no setting, no audit row, only the admin session's own selection. Every page then declares what it is: per bot, shared across the deployment, or mixed. On a shared page the bot buttons are disabled rather than hidden, so the scope of what you are about to change is visible rather than inferred.
A link that named a bot says so, rather than silently switching you.
From this link, not your usual selection.