Tier 0 system view
The Tier 0 core, as a system.
11 modules keep state local, put humans at the gate, and stop external actions when the kernel cannot decide. Each module links to its case study.
The system in four layers
Layers are an operating view, not a strict dependency graph. Evidence-backed relations live on the product map.
Kernel and control
The parts that own state, models, and evidence.
Agent execution
The parts that plan, delegate, and run agent work.
Human-gated operations
The human side of the system: approvals, publishing, and operating.
Business loops
The loops that face customers, content, and revenue.
Four rules the system keeps
Local-first
State lives in your data directory, SQLite, or loopback services; the system can be taken away and replaced.
Fail-closed
External actions stop when the decision kernel, credentials, or policy is unavailable.
Human gates
Publishing, refunds, merges, and outreach wait for explicit sign-off.
Evidence first
Diffs, tests, logs, traces, and audit events are the acceptance surface.
Current state, without rounding up
8 modules are marked Local, 1 is in build, 1 is pre-launch, and 1 has its configuration ready. “Local” describes local-first operation, not a public production SLA.
No module on this page is presented as a public SaaS. The system is being proven locally first.
Keep exploring
See how the modules connect.
The product map lists every active product and the relations that have citable evidence.