Documentation
A place for AI work to stand on
The Athanor gives AI tools bounded, attributed access to project knowledge—and, when you choose it, durable governed continuity that survives closed sessions and changing models.
Most AI tools either forget between sessions or recover context by pouring files, summaries, and search results into a prompt. That can retrieve text; it does not distinguish current truth from stale memory or a machine-generated guess. The Athanor supplies that missing structure and keeps every part of it inspectable.
Three doors in
I work with AI tools
Your tool only works with the context it has. Point Vault at one or several project folders and it returns relevant passages with their sources—no database, embeddings, or GPU. When decisions deserve to outlive the session, AKASHA adds durable, typed memory you govern.
I build agent systems
The Athanor separates model judgment from continuity, retrieval, authority, provenance, and repeated deterministic cognition. The active model is a replaceable body operating inside those contracts, not the database of truth.
I want to know why it is shaped like this
Rooms, Houses, paper boats, a furnace name from alchemy. The mythology is a user interface for discipline, and the discipline is real.
Start with the latent-space argument.
What is true today
Status words mean the same thing everywhere in these docs:
- Current: used by the reference House now.
- Specified: a written contract exists; implementation may lag.
- Planned: accepted roadmap direction.
- Research: investigated, with no release promise.
Current means Windows x64 with the OMP harness; Vault and AKASHA retrieval;
typed memory and lessons; GIGA Stage 1 candidates under review discipline; and
Hallways where attention and read state remain separate facts.
The web prototype at gui-prototype/ is the read-only operator surface.
Run bun gui-prototype/serve.ts from the repository root.
It reads the Host through a loopback proxy.
The Godot client is parked.
Cingulate, OMEGA, and ANON remain roadmap claims.
If a page says something works, a receipt should exist. Evidence holds the public measurements.
Find your question
| Question | Document |
|---|---|
| How do I install the supported release? | Install |
| How do I use rooms and organs? | Usage |
| How does retrieval work right now? | Retrieval |
| What is authoritative, exactly? | Architecture |
| How do typed lessons work? | Lessons |
| What may GIGA write, and what may it never do? | Hippocampus |
| What is actually measured? | Evidence |
| What is unsupported or out of scope? | Limitations |
| What exists versus what is planned? | Planned Features |
| Why is the architecture this strange? | For latent-space explorers |
Deep reference
- The concept map keeps the system's definitions stable.
- Runtime Architecture owns Host, delivery, invocation, and proof.
- Code Flow Map traces current module ownership and event paths.
- Parked Godot Client preserves the historical native specification.
- Synthesis Architecture covers bounded symbolic synthesis.
- Companion Ecosystem covers room sovereignty and signed exchange.
- Product Architecture maps domains, capabilities, and governance.
- Documentation history preserves dated provenance without competing with current contracts.
Nothing on the public site is connected to a live House. The interface specimen uses fictional browser-only records.