as of October 3, 2026 · template v2.7.0
What the brain has become. Drawn from what the template publishes — each block points to the chapter where it was born.
Who writes where. The kernel is the same in every fork; everything else is yours.
what makes the brain — the same in every fork
no change without an explicit human decision
in between
human confirmation
your memory
each satellite has its scribe
your machine — never shared
specific to one machine, never versioned with the kernel
The law of zones was born with KERNEL.md — chapter 1.
« Le CORE est un programme, brain/ est de la data. » (“The CORE is a program, brain/ is data.”) Seven bricks for six capabilities, in Python. One rule holds them together: removing any brick must leave a system that still starts.
persistancethe bridge to the databasemodelethe bridge to the embedding modeltracestraces, and governed writingbsiclaims and locksrecherchesearching the indexindexationbuilding the indexzonesidentity, and who writes whereBorn from Myéline, the brain’s rework in September — chapter 18 and chapter 19.
Everything structured — claims, intentions, todos, decisions, search index — lives in a SQL database versioned like git: 19 tables and 5 views. The narrative stays in Markdown. The database only listens on the machine: it is never exposed.
SQLite to Dolt, in one night — chapter 12.
Each session has a type, which says what it loads and where it may write. And each session opens a claim: a row in the database, not a file. Parallel sessions can see each other.
workbrainexplorepilotechilllearningClaims and their protocol — chapter 3; session types, tightened — chapter 14.
An agent is a file: a header that declares its scope, its role and its triggers, then what it knows how to do. It arrives in one of three ways — the session type loads it, its domain is detected, or you ask for it. And agents/ is now just a view: each agent is a link to your version if you have one, otherwise to the shipped kernel’s. You keep both.
29 agents in one evening — chapter 1; the kernel and the instance — chapter 26. They tell their side: Perspectives.
Each machine has its own database: nothing replicates it. Code and docs travel through git; the sessions of other machines are read peer to peer.
The brain sees the others — chapter 8.
A fork starts with one command: brain serve starts the API and the MCP server from a single declaration. It receives versions through brain maj, which shows its plan before touching anything: what you have modified is merged, not overwritten. And it checks itself: brain doctor runs some sixty checks, each one guarding a drift that would happen silently.
A fork is a whole brain — chapter 25; receiving a version — chapter 26.
The template’s docs are generated, not hand-written: what can be counted is computed, what can be listed is generated, what is named is checked. A page that cites a file, an agent or a command that doesn’t exist is rejected. The numbers on this page come from there.
f0e060e778e8bfa406ecb561fa99d07ddcfda4db40c460cb8b1b39a1573088957c5