0007 — What comes after the MVP
- Status: accepted · Decided by: the project owner, 2026-10-31
- Specs: P-3, P-4, P-5, P-9, INV-4, INV-5, IF-3, IF-8, IF-9, IF-10, IF-12
Decision
After the MVP come four groups of features. They are the ones that set the harness apart:
-
Done = proven + specification.
- The verification gate is part of the loop (INV-4).
- Specifications become acceptance checks.
- The specifications that bind the files in play are put into the context automatically.
-
Memory instead of summary.
- Context is rebuilt from the journal and the task's mind map instead of being summarised away.
- The loop keeps a live mind map of the agent's reasoning — goal, hypotheses, discarded paths, evidence — visible while it works.
-
Rewind and branches.
- Any session can be rewound to event N and branched from there (INV-5).
- Several approaches run in parallel in separate worktrees and are judged by their tests and metrics.
- The losers stay in memory as discarded paths, with the reason.
-
Agent mesh and routing.
- A task is split across agents on different machines, each with its own model.
- The router picks models per step within budgets.