The second brain as context layer. How context-over-prompt becomes operational infrastructure.

"Context is the lever" is easy to say and almost never operationalized. The default pattern is to paste a document into a chat session, get a good answer, and then lose the context entirely when the session closes. The next session starts from blank state. The lever is there in principle; nobody built the handle.

The second brain is the handle. Plain markdown, git-tracked, a kg.json ontology wired as system context into every AI session. Not reached for manually when remembered, but loaded by default. The second brain is context-over-prompt made into infrastructure: every future AI session reads the same brain and writes back to it. That bidirectional link is what makes it compound. Without the persistent layer, the principle stays theoretical. With it, each session inherits the last session's accumulated signal without rebuilding context from scratch.

The substrate decision

Notes apps lock the schema. Markdown files in a git repo are readable by any AI agent, diffable, portable, and version-controlled. The substrate outlasts any single vendor. When the primary AI provider changes. And it will. The context layer survives intact because it is plain text in a format that predates every current LLM.

The architectural decision that matters most is not which app to use. It is whether the brain is wired as a default input or an optional one. A context layer accessed only when the operator thinks to paste it is a habit, not infrastructure. Habits break under load. Infrastructure routes around failure.

Writes-back as the compounding mechanism

A second brain that only reads is a static document. The compounding mechanism is writes-back: when a session produces a decision, a principle update, or a new pattern, it is written back to the same substrate. The brain should be measurably more useful at session one hundred than at session one. That delta is the only metric that matters for evaluating whether the system is functioning as infrastructure or decaying as an archive.

The ontology layer (kg.json) solves the retrieval problem, not just the storage problem. Raw markdown accumulates fast. Without typed nodes and typed edges connecting themes, principles, decisions, and projects, retrieval degrades to keyword search. The graph structure lets agents traverse context, not just grep it. That is the difference between a search index and a reasoning substrate.

The maintenance calculus

The reason second brains failed in the PKM era was maintenance overhead. AI reduces that burden significantly; it does not eliminate it. The audit heuristic I use: if the brain has not been written to in sixty days, it is not functioning as infrastructure. Prune, refresh, re-index. Static context decays.

Two questions enforce the quarterly audit: what patterns has the brain surfaced that changed a decision? What domains have accumulated no signal? The first confirms the system is closing loops. The second identifies where instrumentation is absent. The operator who seeded the brain once and never returned does not have a context layer. They have an expensive initial draft.

The forward question

The second brain is the production form of the context-over-prompt principle. It scales AI session quality across time by ensuring each session starts with the full accumulated context rather than a blank state. The architectural choice. Plain markdown plus git plus a typed ontology. Is vendor-agnostic, agent-readable, diffable, and durable.

Operators who skip this layer pay the context tax on every session: re-pasting the same background, re-explaining the same constraints, re-arriving at conclusions the previous session already reached. The interesting forward question is what the context layer looks like when the graph is three years deep and the agent can traverse it in real time. That is the version I am building toward.