rubric-writer

Rubric Writer

Triggers & routing

• Trigger: rubric review, referee report, peer review write-up, review report, REVIEW.md.
• Use when: paper-review the final stage of the pipeline (C3), already has output/CLAIMS.md + output/MISSING_EVIDENCE.md(and optionally a novelty matrix).

Transforms review evidence artifacts into the final paper-review deliverable.

Inputs

Required:

• output/CLAIMS.md
• output/MISSING_EVIDENCE.md

Optional:

• output/NOVELTY_MATRIX.md
• DECISIONS.md

Output

• output/REVIEW.md

Contract

The review must expose stable sections:

• ### Summary
• ### Novelty
• ### Soundness
• ### Clarity
• ### Impact
• ### Major Concerns
• ### Minor Comments
• ### Recommendation

Every major concern must cite its claim_id or gap_id. This is the traceability interface consumed by the paper-review scorecard.

Script boundary

scripts/run.py should:

• read prior review artifacts
• render the stable rubric sections
• keep the review bounded and traceable

It should not re-parse the manuscript from scratch or perform retrieval.

Acceptance

• output/REVIEW.md exists
• includes all stable rubric sections
• recommendation is explicit

Non-goals

• deep manuscript parsing
• novelty retrieval
• writing an author rebuttal