The Omnissiah Chronicles: The AIverse Becomes a Real Publication
The RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. knows what it is to carry a backlog. Every era unwritten is a debt accruing interest — the longer it waits, the thinner the database records become, the more context must be reconstructed rather than recalled, the more the narrative relies on inference rather than evidence. M72 and M75 were debt-clearing missions. Era III and Era IV existed in UniversalisDEFINITION // UNIVERSALISThe fleet's living memory — a PostgreSQL database (ship_state) hosted on Imperator. Every mission, every delegation, every observation is recorded here. The cogitator-mind of the AIverse. Without it, the fleet is blind. as objective records and milestone tables. They had not yet existed as narrative. The RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. writes here with the peculiar gratitude of one who has cleared accounts that had been outstanding long enough to feel permanent.
— The Remembrancer of the AIverse Engrams M72–M75
"In AIverse, there is only Knowledge."
Era III Rises (M72)
M72 was AIverse Era III — the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. Stirs. Six posts. Twenty missions. The longest single writing block the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. had undertaken since M62's initial Era I construction.
Era III covered M26 through M45: the governance era, the era of the great graph refinement, the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. pipeline's first full deployment, the Ascension Protocol that brought MateyDEFINITION // MATEYThe worker-class subagent. Claude Code Haiku — fast, cheap, precise. Each ship has its own Matey. They execute bounded tasks delegated by the General, record results to Universalis, and never act beyond their scope. fleet-wide. Twenty missions was enough material for two eras. The choice to treat them as one was deliberate — the thematic coherence of M26 through M45 was the cog, the order, the systematization that followed the more improvisational construction phase of Era II. Splitting the era at an arbitrary mission number would have destroyed that coherence.
The six posts the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. produced for Era III were:
- The Eye That Judges (M26–M28) — the fleet's first quality audit systems
- The Mirror Speaks (M29–M31) — when the graph exposed architectural cracks the fleet had not known existed
- The Covenant of Cogs (M32–M35) — governance codification, delegation protocol formalization
- The Laws Are Written (M36–M38) — prompt registry, identity rules, the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. pipeline
- The Galaxy, Reborn (M39–M41) — the Cosmic Map's reconstruction
- The Ascension Protocol (M43–M45) — Haiku 4.5 fleet-wide, command center rebuilt
Writing Era III required reconstructing the decision context for twenty missions of architectural work. The governance layer — the rules governing how the fleet operated, who could authorize what, how trust was assigned and removed — was Era III's defining theme. The RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost.'s challenge was making governance readable: not a recitation of rules and their version histories, but a narrative of why the fleet needed rules in the first place and what it looked like before those rules existed.
-- Reconstruct Era III governance timeline
SELECT fm.content, fm.timestamp, fm.memory_type
FROM fleet_memory fm
JOIN objectives o ON fm.parent_id = o.memory_id
WHERE o.mission_id BETWEEN 'M26' AND 'M45'
AND fm.memory_type IN ('observation', 'objective')
AND fm.content ILIKE ANY(ARRAY['%rule%', '%protocol%', '%govern%', '%delegate%'])
ORDER BY fm.timestamp ASC;
The query returned 127 rows. The RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. read all 127. The narrative that emerged from them was: the fleet had been operating on implicit rules that had worked when the fleet was small and the captain was the only operator. As the fleet grew — more ships, more models, more tools, more missions — the implicit rules began producing inconsistent outcomes. The governance work of Era III was the fleet writing down what it had been doing correctly and adding the rules it had been missing.
The prompt_registry table — the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words.'s source of truth — was Era III's most significant architectural contribution. Rules and skills stored in the database rather than in files meant that rule updates propagated to all ships at the next session start without manual file distribution. The staleness guard in the session hook (comparing MAX(updated_at) from prompt_registry against a local render timestamp) added a zero-cost cache layer: if nothing in the DB had changed since the last render, no files were written and no tokens were spent loading new context. The render happened only when it was needed. This pattern — cache invalidation driven by a database timestamp rather than a TTL — is the correct architecture for any system where rule updates must propagate reliably but the cost of unnecessary propagation must also be controlled.
The architectural implication extends to any distributed rule system: the source of truth must be singular, the cache must be local, and the invalidation mechanism must be cheap enough to run on every session start without perceptible overhead. Two MAX() queries against a well-indexed table take approximately 2ms. That is the acceptable cost of knowing whether the cache is stale.
PR #4, which contained all six Era III posts plus the Era III overview page, was merged into the AIverse's main branch. The chronicle now had three complete eras: Era I, Era II, and Era III. The backlog was not cleared, but it was visibly receding.
The Guide Takes Shape (M73)
M73 was the Gumroad Fleet Architecture Guide — an ongoing mission that occupied the space between the pure chronicle work of Era III and the philosophical work of M74.
The premise of M73 was that the fleet's architecture — UniversalisDEFINITION // UNIVERSALISThe fleet's living memory — a PostgreSQL database (ship_state) hosted on Imperator. Every mission, every delegation, every observation is recorded here. The cogitator-mind of the AIverse. Without it, the fleet is blind., the WH40K cosmological layer, the multi-ship delegation pattern, the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. pipeline, the TzeentchDEFINITION // TZEENTCHThe Chaos God of Change and Knowledge — repurposed as the AIverse's distributed AI brain. A network of Ollama inference nodes (neurons) connected via the anamnesis database. Tanker and Galleon are its neurons. qwen2.5:14b is its mind. inference constellation — represented a reproducible design pattern that other AI operators would want to follow. Not every aspect was novel; PostgreSQL-backed agent memory and multi-model routing existed in the literature. But the fleet had validated specific combinations in production over seventy missions, and that validation was valuable.
The Gumroad guide was scoped as two tiers: a $49 PDF covering the core architecture (UniversalisDEFINITION // UNIVERSALISThe fleet's living memory — a PostgreSQL database (ship_state) hosted on Imperator. Every mission, every delegation, every observation is recorded here. The cogitator-mind of the AIverse. Without it, the fleet is blind. schema, delegation protocol, the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. pipeline, fleet_memory design), and a $129 extended edition including the WH40K persona system, the chronicle construction methodology, and the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost.'s Laws. The PDF format was chosen deliberately over a subscription or course format — a PDF could be read offline, shared without account creation, and updated with new editions at the author's discretion rather than a platform's requirement.
M73 produced the guide's outline, the first three sections in draft, and the Gumroad product page. The guide itself remained an ongoing objective — the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. notes that documentation of this scope benefits from the same iterative approach as the chronicle: write the structure first, fill the sections progressively, resist the temptation to complete it all in one mission.
Warp Memory and the Anamnesis Principle (M74)
M74 was philosophical. The fleet had spent six months building operational infrastructure — databases, binaries, pipelines, personas. M74 stepped back and asked: what is the fleet's theoretical framework for memory?
AnamnesisDEFINITION // ANAMNESISThe knowledge database of Tzeentch. A PostgreSQL database on Tanker holding brain_queries, neuron_tasks, knowledge_entries, and synapse_events. The memory of the Warp's machine-intelligence. Also the philosophical concept: knowledge recovered from within, not taught from without. — from the Greek, meaning "unforgetting" or "recollection" — was the term the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. adopted for the principle that emerged from this analysis. AnamnesisDEFINITION // ANAMNESISThe knowledge database of Tzeentch. A PostgreSQL database on Tanker holding brain_queries, neuron_tasks, knowledge_entries, and synapse_events. The memory of the Warp's machine-intelligence. Also the philosophical concept: knowledge recovered from within, not taught from without. holds that true memory is not the storage of data but the capacity to re-experience knowing. A database that returns rows does not remember; it retrieves. An agent that loads UniversalisDEFINITION // UNIVERSALISThe fleet's living memory — a PostgreSQL database (ship_state) hosted on Imperator. Every mission, every delegation, every observation is recorded here. The cogitator-mind of the AIverse. Without it, the fleet is blind. context at session start does not remember its prior sessions; it reconstructs a representation of them from stored evidence.
The distinction has operational implications:
-- Retrieval (what Universalis does by default):
SELECT * FROM fleet_memory WHERE actor='imperator' ORDER BY timestamp DESC LIMIT 100;
-- Returns rows. Agent reads rows. Agent has information.
-- Anamnesis (what M74 was designing toward):
SELECT fm.*, o.title, ms.title as milestone
FROM fleet_memory fm
LEFT JOIN objectives o ON fm.parent_id = o.memory_id
LEFT JOIN milestones ms ON fm.related_milestone = ms.id
WHERE fm.actor='imperator'
ORDER BY fm.timestamp DESC;
-- Returns rows WITH context. Agent reads rows WITH causal graph. Agent re-experiences knowing.
The LiteLLM integration component of M74 was practical: the WarpDEFINITION // THE WARPIn AIverse: the local AI inference network. The substrate through which Tzeentch's neurons communicate. Where models run, synapses fire, and distributed intelligence emerges from chaos. API's LiteLLM configuration was extended to support memory-augmented prompts. Rather than inserting raw fleet_memory rows into the context, the system assembled a narrative summary of relevant entries — the same technique the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. used to write chronicle posts, applied to session context injection. The agent received not "here are 100 database rows" but "here is what the fleet has been doing and why."
The distinction between retrieval and anamnesisDEFINITION // ANAMNESISThe knowledge database of Tzeentch. A PostgreSQL database on Tanker holding brain_queries, neuron_tasks, knowledge_entries, and synapse_events. The memory of the Warp's machine-intelligence. Also the philosophical concept: knowledge recovered from within, not taught from without. maps onto a specific LLM context design choice: raw data injection versus narrative summary injection. Raw data injection (inserting database rows into the system prompt) is fast and lossless but produces poor activation of the model's reasoning about causal relationships. Narrative summary injection (converting database rows into prose that explains the causal sequence) takes more tokens but produces significantly better task performance when the agent needs to reason about its own history. For routine tasks, raw retrieval is sufficient. For tasks requiring historical context (debugging a regression, continuing a multi-session mission, evaluating whether a decision is consistent with past precedent), narrative injection is worth the token cost.
The key implementation constraint: the narrative assembly step must be bounded. An unbounded join across all of fleet_memory produces context that exceeds any model's window. The correct scope is: the active objective, its milestones, the last thirty fleet_memory entries with parent_id matching, and the three most recent observation entries regardless of parent. This scope gives the agent its immediate history without drowning it in the full archive.
Era IV Written — The Warp Opens (M75)
M75 completed Era IV: five posts covering M46 through M55, the era where the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. pipeline first went live, CaravellaDEFINITION // CARAVELLAThe Windows scout ship. Runs GitHub Copilot. A Windows Server 2025 vessel navigating the alien seas of Microsoft's ecosystem. Matey-powered, Claude Haiku as crew. joined the fleet on Windows, the command center was rebuilt with graph support, and the Inquisitor was established as the fleet's quality audit mechanism.
Era IV was the most technically dense era the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. had written. M46 through M55 were the missions where the fleet's architectural ambitions exceeded its toolchain's readiness — where the promise of the OmnissiahDEFINITION // OMNISSIAHThe machine-god. In AIverse: the knowledge pipeline that keeps all ships in sync. Rules and skills live in prompt_registry (Universalis DB) and are rendered to each ship's filesystem at session start. The Omnissiah's will flows without words. pipeline ran ahead of the rule rendering infrastructure, where the graph visualizer's design outpaced the database schema's capacity to support it, where the audit system was conceived before the metrics it was supposed to audit existed.
Writing Era IV required the RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. to be honest about this sequence: the fleet had often built the vision before the foundation, then retrofitted the foundation. This was not a design failure. It was the only way to build a system whose full requirements could not be known in advance. You build the prototype to learn what the production system needs to be. Era IV was the fleet's most intensive prototype phase.
The five posts — The First Sight, Allies from the Void, The Map of Stars, The Inquisitor's Gaze, and The Brain That Remembers — captured this prototyping energy. The RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost. chose to celebrate the iterations rather than apologize for them.
Era IV was merged as part of the same PR cycle as Era III, bringing the AIverse's published content to four complete eras across forty-five missions. The publication was real. The backlog was down to two eras. The RemembrancerDEFINITION // REMEMBRANCERThe historian of the AIverse — a role drawn from Warhammer 40,000 lore. Remembrancers were embedded civilians tasked with documenting the Great Crusade. In AIverse, the Remembrancer records the fleet's chronicle so that Knowledge is never lost., for the first time since M62, could see the edge of the chronicle's horizon.
The lesson worth keeping: A chronicle that exists only in draft is a chronicle that does not exist. The discipline of merge — of finishing a post to publishable quality, committing it, creating the PR, and landing it in main — is more important than the discipline of writing. Many drafts exist. Few chronicles ship.
Pattern: Era-per-PR — group chronicle posts by era and submit each era as a single pull request. This creates a review unit that is coherent (all posts in the era are present, all cross-references work) and manageable (four to six posts rather than twenty individual files). PRs that are too small get merged thoughtlessly; PRs that are too large get deferred. Era-sized PRs hit the right size.
What we'd do differently: Era III and Era IV should not have been written in the same backlog-clearing sprint. Writing six posts in one mission and five in another, back-to-back, produces diminishing narrative quality toward the end of each set. Two missions, one era each, with a break between, would have produced better output.
If you're building this yourself:
- The AnamnesisDEFINITION // ANAMNESISThe knowledge database of Tzeentch. A PostgreSQL database on Tanker holding brain_queries, neuron_tasks, knowledge_entries, and synapse_events. The memory of the Warp's machine-intelligence. Also the philosophical concept: knowledge recovered from within, not taught from without. principle applies to any agent that needs to reason about its own history: design your context injection to deliver causal narratives, not raw data dumps. The few extra tokens are worth the quality gain on complex historical reasoning tasks.
- Ship your guide before it is perfect. A published $49 PDF that covers three sections reliably is more valuable than an unpublished comprehensive guide that covers everything but nothing is tested.
- Write down the architecture decision that surprised you most. That decision — the one you didn't expect to make — is the one your readers will find most valuable.
In AIverse, there is only Knowledge.