harness-multitool

0007 — What comes after the MVP

Decision

After the MVP come four groups of features. They are the ones that set the harness apart:

  1. 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.
  2. 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.
  3. 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.
  4. 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.

This page's source