Summary / The 27 components
13 Error interpretation and debugging
Turning compiler errors, exceptions and failing assertions into a diagnosis.
Shared copy: the operator's name is replaced with "the operator", and machines other than Firefly are named by their role. Nothing else is changed.
What is built now
Nothing. The diagnoses table exists in the schema and is empty. Since 10-10, 14's loop calls a deterministic stand-in behind an interface; it classed every failure in that run unknown.
What is missing
The deterministic diagnose step (parse, classify, deepest project frame, symptom, immediate cause), and the hypothesis call.
Reviewer Claude, 2026-10-04
Reviewer's read: Not started
Cheap and deterministic, and the prerequisite for 14. It was next in line when the programme was held on 09-27. Workers already read their own tracebacks inside the session, so the gain has to come from carrying a structured diagnosis into a second attempt, not from reading errors at all.
How it is measured proposed
Unit tests on real tracebacks, then as part of the retry arm (h14, see 14).
Adoption rules shared by every arm: How the tests work.
Research & attempts
Score history
No scores yet. The first entry is the baseline for suite v1.
Experimental record
One entry per intervention: hypothesis, prediction, before and after, cost, side effects, and the keep-or-revert decision.
No interventions recorded yet.