2026-07-06: The Dragonpit

Every community needs a front door. Ours started on the wrong one, and fixing that taught us what we actually believe.

The mesh shares trained council champions between independent hauses — content-addressed, signed, eval-gated. Contribute a champion, and you should get to join the geeks who train them. A Signal group, we figured. We even built the whole gate for it: prove you seeded a champion, sanctum mesh community hands you the invite. It worked end-to-end the first night.

Then Bert said the thing that reframed everything: “the mesh is prepper mentality.”

The realization

A mesh whose entire thesis is survive the grid — self-sovereign, no-cloud, works when the internet doesn’t — had just put its front door on someone else’s servers and a phone company’s number. Signal is a fine app; it is also a cloud service tied to a carrier SIM. The moment the grid or the carrier blinks, the door is gone. That is the exact failure mode the mesh exists to defeat. Incoherent.

Matrix fixes it, and it’s the same DNA as the mesh itself:

• Self-sovereign — our homeserver, our accounts, our keys. No carrier, no cloud, no SIM.
• Offline-native — the server runs on the always-on Mini over the tailnet. Grid-down, the room still works. This is the clincher.
• Bot-native — Matrix power levels make a bot admit and expel members as first-class operations, not a hack.

So we stood up a Conduit homeserver on the Mini, fronted it with Tailscale Serve for a valid HTTPS cert on the tailnet (no manual TLS, no public exposure), gave it the server_name dragonpit.sanctum.haus so a future public flip needs no re-keying, and opened a room: The Dragonpit — for the Targaryens kept their dragons in a pit, and we keep ours (AI champions) in a mesh.

Aemon

A room wants a keeper. We built one: Aemon — a small matrix-nio bot wired to the local cathedral (a 27B Qwen champion, mTLS on :1337), who answers questions in the room. We named him for Maester Aemon of the old stories — a Targaryen who gave up a dragon to become the wisest maester, and, as it happens, the character most bound to prophecy. An oracle named for the seer who kept the dragon-prophecy. Bert’s verdict on the name: “the name is prophecy.”

His first words, unprompted, to a test rider who asked who he was:

“Greetings. I am Aemon, Maester of the Dragonpit… those ‘dragons’ are the AI champions housed within the Sanctum mesh — vast, trained models of intelligence that I tend, tune, and temper. I am self-hosted, meaning I answer to no distant lord or cloud-based council. I run locally, offline-capable, ensuring your secrets remain yours.”

He named himself the maester, called the champions dragons, and bragged about answering to no cloud — from a prompt that told him none of the last part. Then we gave him his own identity cert and put him under launchd with KeepAlive. Kill him and he stands right back up. He is a permanent resident now.

The apple way

The obvious move was to tell everyone to install Element. But owning the server and renting a client is a half-measure. The apple way — Bert’s word, and he’s right — is to own the client too. So the Dragonpit got a native panel inside the Holocron, his own Electron control surface: a Matrix chat tab, styled in the same iOS-blue-on-black glass as everything else, talking straight to our homeserver. Own the server, own the client, own the app it lives in. Aemon sits one tab over from the household controls.

Two gates, and an honest one

The community gate is soft, and we say so. It cryptographically proves you own a mesh identity that signed a champion — a real “you’re one of us” filter — but a determined actor could self-sign a junk champion and qualify. The tracker can’t judge a champion’s quality; that’s client-side. Bert’s fix was the missing half: admin approval. The crypto gets you the link; a human (the Master of the Dragonpit) approves you into the room. A faker gets the link and nothing more. The Sybil-proof version — Aemon auto-admitting only riders whose dragon another node actually flew — is Layer 5, waiting on a real pool.

Where it stands

Verified end-to-end: the homeserver answers over the tailnet, Aemon survives kills and answers from the local cathedral, a fresh rider can register, join, and be greeted, and the Holocron panel builds and connects. Everything is self-hosted on hardware we own; nothing phones a cloud.

We’re scoping honestly: five early beta riders now, invited over the tailnet (closed, prepper, no exposure). The thousand hackers are the north star — a federated dragonpit.sanctum.haus — and we designed for them without building for them: the server_name is already right, the moderation roles (Master + a small circle + Aemon-the-Steward) are named, and the one genuinely-new bottleneck is flagged (a single 27B serializes — Aemon will need a queue). Four of the five scale-upgrades were already on the roadmap. The pit doesn’t need a redesign to grow; it needs us to finish the arc we drew.

Train a dragon. Earn your place. The maester is waiting — in a room you own, that answers to no cloud.