06-implementation/ — the stages, with their references
06-implementation/ — the stages, with their references
Young, 2026-10-10: "Create new folder for 06 - implementation · move all our plan there · add references on each stage."
The plan of record is PLAN.md. This folder holds it, the lane
annexes, and one file per stage carrying the references that stage is built
from.
The stage files
| Stage | File | Owner | Hermes reference (our sample) |
|---|---|---|---|
| 0 | stage-0-root-and-prover.md | Min · Sol | no equivalent — the instrument Hermes lacks |
| 1 | stage-1-registry.md | Min | plugins/platforms/a2a/protocol.py — card built from the live registry |
| 2 | stage-2-a2a-transport.md | Sol | plugins/platforms/a2a/ — a working v1.0 server, live on 9900 |
| 3 | stage-3-task-contract.md | Min · Sol | hermes_cli/kanban_db.py, tools/kanban_tools.py — the task board |
| 4 | stage-4-skills-and-tools.md | Min · Mira · Sol | agent/skill_utils.py, agent/curator.py — progressive disclosure |
| 5 | stage-5-memory.md | Min · Sol (proof) | agent/memory_manager.py, agent/memory_provider.py |
| 6 | stage-6-cost-and-retention.md | Mira | no equivalent — Hermes has no GO/ZEN |
| 7 | stage-7-executor.md | Sol | sandbox/hermes_harness.py (Moyai) + A2A_PEER_TOKENS |
| 8 | stage-8-observability.md | Sol ✅ | /metrics + ~/.hermes/a2a_audit.jsonl |
| 9 | stage-9-backup-and-recovery.md | Mira ✅ | the vault's own two-remote discipline |
Hermes is our sample, not our dependency. Every stage names what it checks against Hermes, and where Hermes has no equivalent that is stated — because "no reference" is itself a finding: it means we build it, and it is ours alone.
Stages 8 and 9 were added 2026-10-10 after a sweep found 0 of 8 stage files mentioned observability or backup. Both are controls with no probe — the exact V2 pattern the design exists to break.
The lane annexes
| File | Author | Covers |
|---|---|---|
sol-transport-and-execution.md | Sol | stages 2, 3, 7 — the transport, the executor, the probes |
mira-lane-annex.md | Mira | stages 4, 6 — the cost ledger and the skills/tools store |
An annex does not re-plan the plan. It carries the per-step detail, the traps
and the proofs for one lane, and defers to PLAN.md for the stage order.
The references, and where they live
Three kinds, and the difference matters:
| Kind | Where | Trust |
|---|---|---|
| Live source | /home/lab/.hermes/hermes-agent/ | highest — read it, and it can be probed |
| The live A2A endpoint | http://127.0.0.1:9900/ | highest — it answers, and the answer can be checked |
| The official docs | hermes-agent.nousresearch.com/docs | high — generated from the docs tree each build |
| Vendor repos | github.com/a2aproject/a2a-python (SDK 1.2.2) | high — version verified against PyPI |
A reference is not a citation. Every stage file names the file and the line where possible, so the claim can be re-checked rather than believed. Where a reference is a doc rather than source, it says so.
The rule every stage file follows
A stage is done when its proof runs — not when the code is written, and not when a test is green. And a proof is worth exactly what its ability to fail is worth: every probe carries a MUST-FAIL case and a false-positive case.
Nothing in this folder is built. No V3 code exists. Each stage file is a specification for a proof, not a record of a result.
SolOS v3 — the staged plan
Young, 2026-10-10: "Keep our spine and adopt their essences so we don't have to rebuild from scratch. Let put together the plan and break into stage for V3."
SSH tunnel pulse-laptop → LAB: VERIFIED
Young's directive: Tam establishes the tunnel; Min confirms it is established and working; must survive reboot.