Skip to content

feat(spec): a claims-verification pass measures the spec against the tree - #958

Open
leeovery wants to merge 1 commit into
review-source-routingfrom
spec-claims-verification
Open

feat(spec): a claims-verification pass measures the spec against the tree#958
leeovery wants to merge 1 commit into
review-source-routingfrom
spec-claims-verification

Conversation

@leeovery

Copy link
Copy Markdown
Owner

Why

Idea 40: both review agents compare documents against documents. A false empirical claim present in both the spec and its source is a perfect fidelity match — seven such claims survived six observed review cycles, and the only pass that caught them was an unauthorised remit rewrite. For a spec whose content is largely codebase measurements, nothing prescribed ever touched ground truth.

What

  • New agent workflow-specification-review-claims: opens every review cycle (Phase 1). Collects the spec's empirical claims, re-runs each load-bearing one's recorded command (never trusting the documents, prior cycles, or asserted-as-verified figures), and verdicts hold / fail / unreproducible. A failing claim that lives in a source becomes a Source defect finding (routes back via feat(spec): review findings that indict a source route back, never apply #957's lane); a spec-only failure carries the corrected measurement; unreproducible load-bearing claims must be restated measurably or removed. Read-only measurement is a hard rule.
  • spec-review.md becomes three sequential phases — claims first, so a false-in-both claim routes before fidelity review reads it as a match. Sections relettered C–G.
  • specification-format.md: empirical claims are recorded with their measuring command (cmd → result) at their home — what makes re-verification mechanical; open-decision markers are banned from the document outright.
  • Menu migration (touching-a-file rule): the review loop's cycle gate and re-loop prompts move to a new engine surface render spec-review-gate --variant continue|reloop, with render tests and a pipeline-simulation extension; convergence-analysis.md and spec-completion.md pick up the third stream.

Stacks on #957. Part 4 of the idea-40 stack.

🤖 Generated with Claude Code

…tree

Both review agents compare documents against documents, so a false
empirical claim present in the spec and its source read as a perfect
fidelity pass — seven such claims survived six observed cycles, and the
one pass that found them was an off-remit rewrite. A third agent now
opens every cycle: it re-runs each load-bearing claim's recorded command
(specification-format now records measurements as command → result),
verdicts hold/fail/unreproducible, and classifies a failure by where it
lives — source-carried failures become Source defect findings that route
back, spec-only ones carry the corrected measurement. The review loop's
two prose menus migrate to the engine (render spec-review-gate) per the
touching-a-file rule, with tests and a simulation extension.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant