Every guarantee BrainLLM makes is enforced at the tool layer rather than requested in a prompt. Here is what that actually looks like.
Created by bootstrap() against a fresh Trilium instance. The root carries a discovery marker, and every structural note is engraved with its purpose at creation.
BrainLLM ├── 👤 Master the user — durable identity │ └── Biography · Goals · Preferences 3 singletons ├── 🤖 LLM the assistant's self-model │ ├── Responsibilities · Protocols 2 singletons │ └── Diary/ one [yyyy-mm-dd] note per day ├── 🗂️ Memory the operational record │ ├── Sessions/ one [yyyy-mm-dd] note per day │ └── Threads/ titled multi-session work │ └── <Thread>/ Context + Resolution only, │ day-to-day lives in dated children ├── 📚 Knowledge learned info beyond training │ ├── Master/ user facts beyond bio/goals/prefs │ └── Domains/ one Sources note + N information notes └── 💡 Insights the brain's record of itself ├── Logs/ auto-generated daily change log └── Graph live Mermaid render of the relation graph
What a note is determines how writes to it behave. This is the distinction that keeps a knowledge base from decaying into a changelog.
Exactly one maintained note; writes upsert into it. They hold current-state truth, edited in place — biography, goals, preferences, responsibilities, protocols, and each domain's Sources note.
One per calendar day, titled by date. Diary and session writes append a timestamped block, because chronology is the point. The daily log is regenerated in place — one clean snapshot, never stacked.
Titled notes, deduplicated by normalised title within their scope. A thread is itself a book: its body holds only Context and Resolution, and each active day gets its own child.
Degradation demotes rather than removes, so an archived note keeps its content and stays retrievable. Any touch reactivates it.
active ──────────────▶ resolved | superseded terminal, archived in place │ untouched 21 days ▼ dormant ──────────────▶ archived in place #archived + #closed │ untouched 45 days more ▼
They are maintained, not recorded. Sessions, diary entries and logs never age either — they are records by nature.
A thread marked eternal is skipped by the sweep entirely, for work the user wants kept permanently active.
Not modification date — a thread's own body rarely changes once written, so date-based aging would retire a thread being worked on daily.
Connections are typed and rejected if they aren't on the list, because an untyped "related to" edge carries no information a reader can act on.
extends · contradicts · supports · causes · references · partOf · worksWith · mentors · instanceOf · supersedes · implements · inspiredBy · sourceOf · derivedFrom · corrects — and relatesTo as the last resort.
corrects existsRevising a note in place leaves no trace its previous claim was ever believed — so nothing tells a later reader to be suspicious of sibling notes written in the same pass, by the same reasoning, on the same day. In a memory whose value is being trustworthy about the past, silent overwriting is the operation to trust least.
A session can't commit until every step has run — and in the right order, because the diary is the closing record and should be written with the reflection cues in hand.
session() → addendum() → maintain() → remarks() → diary() → close() Gate state lives on today's session note as a label, not in process memory — so it survives a restart and behaves identically whether the server is running over stdio or behind a load balancer.
Five minutes to a working brain, if you already have Trilium up.