Quox Dev Suite · ProofLoop
The claim is not the evidence. The run is.
An autonomous developer generates claims faster than any team in history, which is exactly why they cannot be taken on trust. ProofLoop is the loop that stops it: every claim driven on the real surface, every capture guarded by assertions, every gap filed, and every fix carried back into the page that was hedging.
Inputa claimMethoddrive the real surfaceOutputevidence or a filed gapBoth waysno over, no underclaimIn 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.
- Where do I use it
- In your terminal, inside any Claude Code session on a Quox dev box.
- When would I use it
- When you are about to claim something works and have not driven it end to end.
- How do I use it
- Ask your Claude to run /proof-loop with the claim; it drives the real surface and files what it finds.
The loop
Claims go round until they are evidence.
Anything that makes claims rots in one direction: the claims outrun the code, and nobody notices until a customer does.
ProofLoop is a loop in the literal sense: a claim is driven, captured and gap-filed, then every fix flows back into the page that made it, and the circuit runs again until the claim and the evidence match.
- 1A claimevery claim on a list
- 2Drive the real surfacethe run is the evidence
- 3Capture with assertionsno degraded shot ships as evidence
- 4File every gapwhat failed is the product
- 5Close the looppromo, docs, evidence, status
- round again, back to 1
- Claim provenshipped with its evidence
The model
Inventory, drive, file. Then close the loop.
Every claim on a list
Take the page, the README, the docs, and list every factual claim each one makes. Each claim gets a row: how it would be proven, what evidence exists now. A claim with no path to proof is cut or labelled planned, in public, on the surface itself.
The run is the evidence
Reach the capability the way a customer would, headless first. A green test suite proves the code; only driving the shipped surface proves the capability. Four real defects on our own platform were invisible to a full green suite and surfaced only when the features were actually driven.
What failed is the product
Every step that needed a human is an automation gap. Every claim that outran the code is an honesty gap. Every empty capture is a defect list nobody had. One honest attempt to prove a page yields screenshots, walkthroughs, product gaps and tooling gaps: four assets for one effort.
The loop closes both ways
When a gap gets fixed, the page that was hedging is now underselling, and underclaiming wastes the work as surely as overclaiming burns the trust. Every fix flows back into the promo, the docs, the evidence and the status ledger before the work is called done.
Honest state
What is real today, what is planned
- The full methodology, installed as a governed skill and run against real surfaces
- It has driven every honest maturity band on this site, including this page (a stage-0 artifact itself)
- Assertion-guarded capture: no login screens, no loading states, no degraded banners ship as evidence
- The stage-0 law: the ambitious page ships with the plan, staging first, gaps tagged honestly
- ProofLoop as a packaged plugin: witnessed stages on the evidence chain, not just a disciplined session
- An evidence gallery per claim: the capture, the assertion, the date, browsable per surface
- Scheduled re-proof runs, so shipped claims cannot silently rot
- The Signal handoff: refuted claims filed as proposals automatically
Evidence
The discipline, shipped as a product surface
Driven, not described
A real run, reporting its own position
Every proof-loop run emits its stage block as it moves. This one is from the 21 August 2026 run over the Dev Suite bundle pages themselves: the run that put the captures and walkthroughs on the pages you are browsing.
Ⓠ PROOF-LOOP devsuite-bundle stage 7/7 complete 1 inventory done 7 stale slots claims, 2 bundle-page, DoneEngine pageless 2 drive done slots/DoneEngine driven live earlier in session 3 capture done 3 authenticated captures, guards refused 2 degraded shots first 4 walkthrough done pinned walkthroughs on quoxslots + doneengine 5 file gaps done 2 CLI defects filed as issues 6 close loop done promo + docs + evidence + status + support corpus + prod 7 harden done 2 skills amended with what this run taught a run that ends before 7 reports as incomplete, not done
How you get it
A method you adopt, not a box you buy
In daily use here
ProofLoop runs every honest page we ship, and the discipline travels in the Shared Skills + Rules every enrolled dev server pulls, so your agents inherit it the day a host joins the fleet.
On its own
ProofLoop 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 ProofLoop yet, so what launch delivers is the licence key and the discipline, not a dashboard tile: the witnessed-stages plugin surface is the planned half, listed in the open above.
ProofLoop
Pages that cannot lie
Part of the Quox Dev Suite. Honest in both directions.