Methodology
How capability actually improves here.
Not an architecture reference — this is the short version of what a soul and a skill go through, and why. Implementation detail lives in the codebase, not here.
Formation
A soul isn't switched on — it's built in three stages, in order. Distillation seeds a fresh soul from trusted sources: curated documentation, exemplar traces, and the consolidated identity of prior, already-stable souls in its lineage. Inherited learning follows — the soul absorbs passed-down memory and heuristics before it ever acts on its own, so even a brand-new soul carries a past.
Self-improvement is the stage that never ends: the soul reflects on its own outcomes, detects its own weaknesses, and revises itself — while its core values and hard constraints change far more slowly than everything else, on purpose, so identity survives the adaptation.
Six domains, one soul
Every soul is structured around six brain-inspired domains — not as decoration, but because judgment needs more than a single task-execution loop.
The same six domains, in structural detail
The six domains above are still all there are — nothing new was added on top of them. What changed is how much of each one is actually modeled: Connectome maps every domain onto its real, classical neuroanatomical structures (151 in total — hippocampus, amygdala, insula, and the rest, using real public-domain nomenclature) instead of treating a domain as one flat score. Social cognition is the one exception worth naming: it has no anatomical home of its own, so it's modeled as a purely functional domain that draws entirely on structures filed under the other five.
This is depth, not expansion — a soul's domain scores are still exactly six numbers at the frontmatter level; the structures are what those six numbers are grounded in underneath.
The skill lifecycle
Skills go through the same loop, on repeat, for as long as they stay in use — discovered from real signal, not assigned by a human curator.
A candidate is only promoted into the library once it clears an evaluation gate — and a soul only reaches for a promoted skill if its own gating check (bound, confidence-matched, aversion-clear, fluency-scaled) allows it.
Orchestration
Souls and skills are data. Something has to turn that data into an actual model call — assembling the shared reasoning engine, calibrating it with a specific soul's frontmatter, retrieving the right skills and memory, and routing the request to whichever model tier is doing the work.
Seiza Harness
Seiza Harness is the name of that layer. It doesn't reason on its own — it assembles context, enforces the skill-gating policy before a dispatch is allowed, and decides which stage of a skill's lifecycle runs on which model tier. Everything upstream of it is data; everything downstream is a model call.
Five model tiers do that work, split by volume and stakes rather than by task type — the same split repeats across every feature on this site, not just the skill lifecycle.
Closing the loop
"Self-improvement never ends" (see Formation, above) is only true if something actually reads what a soul does and feeds it back. Three pages generate that signal; Consolidation is what turns it into a soul's next revision.