A coding agent reports that the work is done, and the tests exit 0. Endophasia answers from records, not from the report. You state what a correct result looks like before the work begins, hand the brief to the agent, run the checks yourself, and read one ledger of what is established and what is not. It attaches beside the harness you already run (Pi, today) and never installs into it, patches it or replaces it.
- Use it when
- You need to know whether an agent's work is what it claims to be, why two runs differed, or what a change to a prompt, model or harness does before it ships.
- Works today
- Tasks, attempts and briefs; operator-run checks with receipts, verification plans, an acceptance ledger and working-tree provenance. A live Pi workbench in which every prompt, steer, queue and stop is approved in the terminal. Recording, exact replay, trajectory comparison, and controlled and sandboxed experiments. Build from source:
main is well ahead of npm 0.1.0-alpha.2.
- Pencilled in
- An operator interface for evaluation-driven adaptation, model-internal observation, and live control of harnesses other than Pi.
- Does not claim
- That relayed reasoning is a verified record of the model's computation, that a passing check is acceptance, or that terminal approval contains the tools an agent runs.