The Shrine and the Gods

A lararium was the shrine in a Roman house where the household gods lived. Not a temple you visited on holidays. A small niche by the door, part of the home, tended every day. The family kept it, fed it, and spoke to it. The gods in it were not abstract. They were the specific spirits of that specific house.

This is that, for a life run with AI. The shrine, and the gods you keep in it.

The thing everyone gets wrong

The market is drowning in prompt packs. Ten hacks. A notion template of someone else's system. A persona you can paste into a chat box to make it talk like a growth marketer. Every one of them hands you the same thing: their context, dressed up as yours.

It never works, and the reason is simple. A second brain is not a file structure. It is the ten thousand small facts about your life that make an answer land instead of miss. Who your people are. What you decided last March and why. The constraint you keep forgetting until it bites you again. None of that ships in a template, because none of it belongs to the person selling the template. You cannot download a life you have to live.

So the pitch is inverted here. Lararium hands you the empty structure and teaches you to pour your own life into it. The architecture was never the moat. Your life is. That is the whole design, and it is exactly why giving it away costs nothing: nobody can steal a life they have to build themselves.

What it actually is

Lararium is a clone-and-run scaffold for a personal agentic system. Six layers, and each one solves a problem you already have if you have spent real time with an AI assistant.

1. The brain. A file-based knowledge store, plain markdown, scoped by the spheres of your life. This is the fix for the assistant that forgets you every morning. It is useful on day one with nothing but a text editor.
2. The soul. The assistant you actually talk to, assembled fresh each session from layered sections, with a heartbeat that lets it remember yesterday and drift-monitoring so it keeps sounding like itself. This is the fix for the assistant that sounds like everyone else's.
3. The clocktower. The index over your data: schema, a search server, the watchers that ingest your corpora, the retrieval doctrine earned in production. This is the fix for the day grep stops being enough.
4. The agents. A roster of specialized subagents your assistant dispatches, plus the doctrine for which to use when. Re-theme the whole roster into your own mythology. Bring your own gods, literally.
5. The hooks. The loops that make it feel alive: the session-start briefing, the heartbeat, the safety rails, the routing. The invisible layer that turns a folder of files into a presence.
6. The skills. Slash commands for the rhythm of a life run this way: end a session cleanly, hand off to the next one, run the self-improvement pass.

It ships empty on purpose. You get the shrine. You bring the gods.

It installs itself

Here is the part that sounds like a gimmick and is not. An agentic stack should be installed by an agent. So you open the folder in an AI coding assistant and say, run the install interview. It interviews you, one question at a time, and writes your files while you answer. You are not filling in a hundred blank templates. You are having a conversation, and at the end your brain and soul exist, in your words, about your life.

The brain and soul layers need nothing else: no database, no keys, no server. The index is there for the day you outgrow searching by hand, and not one day sooner.

Why read the rest

This is the first post in a series that walks every layer, one at a time. Not a documentation tour. Each post takes one idea, shows you the specific pain it kills, and gives you enough to try it yourself that afternoon.

We start where you should start: the brain, and the single most stealable idea in the whole system, the sphere method. That one needs nothing but markdown and a decision. Read it next.

The shrine is free. What you enshrine in it is the part only you can make.