ATLAS

The federation, drawn

One mind, spread across four machines.

ATLAS is not a script on a laptop. It is one organ in PANTHEON, a self-hosted federation where ORACLE orchestrates, a binary memory holds the world, and every answer is grounded in evidence before it is spoken. This is how it is built. Drag the constellation.

The federation

PANTHEON is the whole mind. The rest are its organs.

The design idea is simple and old: an intelligence is not one program, it is a body of organs, each with one job, wired together. PANTHEON is the federation itself. ORACLE is the organ that orchestrates. ATLAS is the visibility brain. EYE is the eye of the world. Each organ is a real service on real hardware, and the mind is what they are together.

PANTHEON THE FEDERATION ORACLEorchestrator ATLASvisibility EYEeye of the world M4 VOICEmemory + speech VALKYRIElore + world

Every organ speaks a small, boring interface, an HTTP endpoint, so any organ can be replaced, rebuilt or moved to another machine without the rest of the mind noticing. That is why a single node can go offline and the federation keeps thinking with what remains.

PANTHEON is the sum. When you ask it a question, you are asking the whole body, and it decides which organs to consult. ORACLE is the conductor that plans a multi-step answer. ATLAS is the organ that sees your web presence and acts on it. EYE is the binary cognition that reasons over the world model. None of these is a metaphor, each is a process you can watch on the live page.

Organs, not modules. The point of the organ design is failure tolerance and honesty. An organ that is down is drawn as down. Nothing pretends to work that is not working.

The hardware

Four machines, one mind.

The organs are not evenly spread. Each physical machine holds the organs it is best shaped for: intake and visibility on one, memory and voice on another, lore on a third, and the deep cortex on a fourth that is currently offline.

FEDERATION BUS · HTTP bubblesvisibility + intake M4memory + voice VALKYRIElore + world megamind-agicortex · offline
MachineRoleKey organs and services
bubblesVisibility & intakeThe ATLAS engine (:8099), the ask gateway mmask (:9518), retrieval mmbroad (:9503), certification mmcert (:9504), and the proof kernels mmk / mmk2 (:9500 / :9501). Also the knowledge ingest that encodes Wikipedia and the public-domain library into binary neurons.
M4Memory & voiceThe neural substrate (:9440) running Kuramoto oscillators, wave dynamics and STDP learning on the GPU. The language voice, an MLX Qwen model (:8099). The reasoning gateway (:8090) that stitches the two together.
VALKYRIELore & worldThe codex (:8790) and the living-world engine endless-pantheon (:8788), the narrative and simulation memory of the federation.
megamind-agiCortex (offline)ORACLE the orchestrator (:9402), EYE the eye of the world (:9404, binary cognition, dim 2048), the loom (:9410) and mmserve (:9099).
The cortex is dormant. The megamind-agi node is offline right now, so ORACLE and EYE are asleep. The federation keeps answering from bubbles and M4, and the moment that machine rejoins the mesh, its organs light back up on their own. You can see the exact status on the live page.

The reasoning pipeline

It retrieves, it certifies, then it speaks.

Most systems generate an answer and hope it is true. PANTHEON does the opposite. It finds real evidence first, checks that the evidence actually answers the question, throws away what does not, and only then lets the voice speak, using nothing but what survived. If nothing survives, it says so.

Retrieve mmbroad · :9503 real passages from memory Certify mmcert · :9504 does it answer? kept no evidence → abstain Speak M4 Qwen voice · :8099 answer from evidence only
Retrieve

Real passages

PANTHEON pulls candidate passages out of binary memory with mmbroad. These are actual encoded texts, not invented context.

Certify

The gate

mmcert checks whether each passage genuinely answers the question and filters the rest. Nothing weak gets through.

Speak

Evidence only

The M4 Qwen voice composes the reply using only what survived certification. If the gate is empty, it abstains instead of guessing.

Binary memory

Meaning, stored as bits.

The federation does not keep text in a database it searches with keywords. It keeps knowledge as binary hypervectors. Each concept becomes a fixed-length signature, and similarity between concepts becomes a single fast integer operation.

Every concept is one neuron, a 512-bit signature. To ask how alike two concepts are, the federation takes the XOR of their signatures and counts the set bits. That count, the popcount of the XOR, is the Hamming distance. Fewer differing bits means more alike.

The trick that makes this mean something is SimHash. Each bit of a signature is the sign of a random hyperplane projection of a dense semantic embedding. Because random hyperplanes cut the embedding space evenly, two vectors that point the same way land on the same side of most planes. So Hamming distance in bits tracks cosine similarity in meaning. Close in idea, close in bits.

About 89 million neurons. The federation holds roughly 89 million of these signatures, encoded from Wikipedia and the public-domain library, and it keeps ingesting more around the clock. Watch the count climb on the live page.
concept A … 512 bits concept B … 512 bits A XOR B popcount = Hamming distance SIMHASH · one bit = sign of a random hyperplane plane same side → same bit

ATLAS, in the mesh

The visibility organ has its own loop.

Inside the federation, ATLAS runs a closed five-step cycle on every page it manages: ingest, diagnose, fix, verify, report. It does not reason in isolation, it borrows the M4 voice to draft copy and think through diagnoses, then acts on its own hardware.

ATLAS uses M4 voice INGESTread surfaces DIAGNOSEfind gaps FIXedit the page VERIFYgate + revert REPORTwrite + email

Ingest reads every data surface for a site. Diagnose maps each gap against current Google and Bing guidance, reasoning with the shared voice. Fix edits the page directly, after committing a backup. Verify runs the render and behavior gate and reverts anything that shifts. Report writes the weekly summary and the client email.

Because ATLAS lives in the mesh, it inherits the federation's memory and its grounded discipline: it fixes what it can prove is a gap, and it proves nothing broke before it moves on. The full walkthrough is on how it works, and you can watch the loop turn in real time on the live page.

One mind, drawn honestly. Now watch it work.

The architecture is only worth anything if it runs. It does, right now, on real hardware you can inspect. See the live state, or ask the federation a question and watch it ground the answer in evidence.