Repository navigation
Veriloop 0.12.0
Three artifacts, three jobs
The loop now writes IA.md, REVIEW.md and PRD.md, and each does something the other two do not.
IA.mdis the contract — the confirmed specification, every clause paired with a check that runs. It replaces the formerSPEC.md.REVIEW.mdis the audit — the final review report, persisted beside the specification.apply-review-findingslocates it by convention and syncs finding statuses back into it after fixes.PRD.mdis the product document — a description of what now exists, written for someone who was not in the room.
PRD.md is a product document, not a delivery checklist
The previous definition put the acceptance-criteria table at the centre. In use that produced a document nobody outside the work could read: verdicts were listed, but what the thing is, who uses it and how it works were stated nowhere. A verification table only means something when a product description stands in front of it.
PRD.md now carries ten chapters in order: what it is, who uses it, what problem it solves, what it does, how it is used, how it works, non-functional requirements, verification, what remains, and the document's own limits. Verification is one chapter, not the whole document.
Rules that come with the definition:
- Chapters scale with the size of the work — a single bug fix gets a paragraph each and a complete verification table; a programme gets the whole document. No chapter is dropped to save space; "not applicable" is written down with the reason.
- Factual claims are grounded in
file:line. Inferences are marked as inferences. - Unresolved discrepancies are recorded as discrepancies, not quietly dropped.
- Findings themselves stay in
REVIEW.md;PRD.mdreferences them. - Written on a
goal_metexit only; otherwise the report says why it was not.
For a programme made of several pieces of work, the same pair scales to two tiers. IA.md and PRD.md in the parent directory describe the whole; each piece keeps its own pair in its own directory. Stakeholders read the parent PRD.md first.
Also in this release
- The
loop-dashboardskill is removed, along with its stale mentions in both READMEs. draft-specnames the confirmed specification inside a per-work directory; the directory layout itself stays repository- or locally-governed.- Both READMEs now spell out what belongs in each artifact.
- The Codex manifest, left at 0.10.0 through the 0.11.0 and 0.12.0 bumps, is back in step.
This release folds in the unreleased 0.11.0. The Claude and Codex marketplace manifests both publish version 0.12.0.