Quox Dev Suite · FixLoop
Every bug ends as a passing test.
The worst agent failure mode is not the wrong fix, it is the fifth wrong fix in a row. FixLoop is the bug discipline as software: reproduce with a failing test before touching code, fix minimally, keep the whole suite green, and stop after three attempts instead of spiralling.
Firsta failing testThenthe minimal fixAlwayswhole suite greenLimitthree attempts, then stopIn plain words
What it is, where it lives, when to reach for it
- What is it
- A Quox skill for Claude sessions, installed with the dev suite alongside ProofLoop.
- Where do I use it
- In your terminal, inside any Claude Code session on a Quox dev box.
- When would I use it
- When a bug is reported, or something that used to work has stopped working.
- How do I use it
- Ask your Claude to run /fix-loop with the bug; it writes the failing test before the fix.
The loop
One circuit per attempt. Three at most.
FixLoop is a loop in the literal sense: if the whole suite is not green after a fix, the work goes round again, and after three failed attempts it stops and rethinks instead of spiralling.
- 1Bug reportedthe loop starts here
- 2Failing test firstno test, no understanding
- 3Minimal fixthe smallest change that turns it green
- 4Whole suite runa fix that breaks something is reverted
- 5Still red? Round againthree attempts, then stop and rethink
- round again, back to 1
- Suite greenthe bug ends as a passing test
The model
Reproduce, fix, prove. Stop before you spiral.
No test, no understanding
FixLoop refuses to touch the code until the bug exists as a failing test. If you cannot write the test, you do not understand the bug yet, and every edit you make from that position is a guess wearing a fix’s clothes.
Minimal, then prove it
The smallest change that turns the test green, then the WHOLE suite, because the second most expensive bug is the one your fix just created. A fix that breaks something else is reverted, not argued with.
The loop that refuses to spiral
Sequential guessing is how agents burn a night on one bug. After three failed attempts FixLoop stops, reverts, and switches mode: parallel investigators each test a distinct hypothesis, evidence picks the winner. The spiral is a policy violation, not a mood.
Attempts on the record
Where it goes next: every attempt, revert and regression run as witnessed events on the evidence chain, with the three-strikes gate enforced by the platform. Your audit trail shows not just the fix that shipped but the two that were rightly abandoned.
Honest state
What is real today, what is planned
- The full method, installed as a governed skill: failing test first, minimal fix, whole suite, revert on regression
- The three-attempt limit with mandatory stop-and-parallelise, run on our own bugs daily
- The parallel-investigator escalation pattern (distinct hypotheses, evidence-ranked)
- FixLoop as a packaged plugin: attempts, reverts and suite runs as witnessed events on the chain
- The three-strikes gate enforced by the platform, not by discipline
- The Triage handoff: FixLoop as the engine Triage drives per accepted bug
- Regression ledger per repo: which bugs came back, with the test that now guards each
- F4A patrol’s human-approval gate was unreachable by any human (owner-scoped, not org-scoped).Human session now sees and approves the gate; the patrol dispatched.blocked the first live patrol
- F3A gated agent action failed closed but filed no reviewable proposal, so no human ever saw it.Agent action now files a real, human-visible approval proposal.silent governance gap
- F5The org binding silently accepted a slug instead of the real id, running work in a phantom org.The wake now refuses an unverifiable binding; the valid id is accepted.validation gap
How you get it
A discipline you inherit, a plugin later
In the shared rules today
FixLoop travels in the Shared Skills + Rules every enrolled dev server pulls: your agents reproduce with a failing test, fix minimally and stop at three attempts because the discipline arrived with the host, not because someone remembered to say so.
On its own
FixLoop has its own store row at $19, and it ships inside the Dev Suite bundle at $169. The row is priced and launch-gated: checkout opens on launch day, through Stripe, with the licence key delivered by email.
There is no dashboard plugin manifest for FixLoop yet, so what launch delivers is the licence key and the discipline, not a dashboard tile: the witnessed-attempts plugin surface, with the platform-enforced three-strikes gate, is the planned half listed above.
FixLoop
Fixes that stay fixed
Part of the Quox Dev Suite. Three strikes, then think again.