The system map
How the whole thing fits together
The individual write-ups in Systemseach cover one part. This is the single picture they live inside — how a thought moves from a rough note to finished work, and how what I learn doing the work comes back round. It's deliberately a map of the structure, not its contents.
Capture
ideas · signals · documents · conversations
Route & file
classify · sensitivity gate · inbox → home
Governance
3 active slots · session + weekly review · displacement rule
Build
one primary at a time
Diagnose
lab → agent → advisor panel
Maintain & ship
projects in production
Knowledge & memory
decisions · learnings · durable library · cross-session memory
Ask the corpus
RAG & learn-ask — grounded, cited answers
Everything starts at capture. Ideas, signals, documents, and the odd half-formed thought go into one place rather than scattering across notes apps and my memory. Nothing is judged at this stage — capturing is meant to be frictionless.
Then it gets routed and filed. Each item is classified and sent to its proper home, with a sensitivity check that runs first: anything personal or confidential is only ever proposed to a safe destination, never filed automatically.
The governancelayer is the gate, and the part I'd point to first. There are only three active slots — one primary build, one secondary, one for exploration — and a displacement rule: nothing new becomes active unless it consciously replaces something. A short session routine and a weekly review keep the focus honest. Most captured ideas wait here, on purpose.
What passes the gate becomes active work, in one of three lanes: building the current primary thing, diagnosing a new idea through a chain of specialist checks, or maintaining what's already shipped. Only one primary build runs at a time.
The work produces a knowledge and memorylayer — decisions with their reasoning, lessons learned, a durable library of concepts, and a cross-session memory so the next session doesn't start cold.
And that layer is retrieved: I can ask the corpus a plain question and get a grounded, cited answer back. Those answers feed into the next capture and the next piece of work, which is what makes it a loop rather than a filing cabinet.
A sanitized view — the structure is shown, never the material that moves through it.