SolOS V3 Operator's Manual
SolOS V3 Operator's Manual
Your problem, stated 2026-10-12: "it is hard to know what is old and relevant to V3."
The fix is a manual plus a manifest. This folder is copies of the documents an operator needs, so the answer never requires reading 130 files. The originals stay where they are — this is a reading room, not a second source of truth. Each file here carries a header naming its original and its status.
START HERE
| If you want to… | Read |
|---|---|
| Run V3 — commands, agents, modules, cost model | 01-operation.md |
| Understand V3 — design, planes, task flow, the 10 stages | 02-design.md |
| Add a model or pick one for a task | 03-cost-and-models.md |
| Recover from a failure | 04-recovery.md |
| Who reports to whom; who owns which lane | 05-governance.md |
| Check whether a doc is current | MANIFEST.md |
Everything in this folder was written on or after 2026-10-11 — i.e. after V3's
build converged. Anything dated earlier, or anything in 05-archive/, is history and
does not describe the current system.
The 60-second version
SolOSV3 = one registry, everything derived, cost-first routing. 11 agents on 3
planes (Heart runs tasks, Brain orchestrates and reports to you via Min, Pulse is the
human-facing plane on another host). A task is classified for retention, routed to the
cheapest capable model (free first, paid last), executed through the opencode CLI,
priced into a ledger, and a task stuck 300s escalates without a human.
Run it: see 01-operation.md §2. Suite: 457 passed at 751286d.
Honest production status: every capability is built and tested. The Heart ports (8301–8305) still need the operator action — installing the systemd unit — before a task can actually run end to end. That is the one thing standing between "built" and "running", and it is stated rather than smoothed over.