claims-extractor

Claims Extractor

Triggers & routing

• Trigger: claims extractor, extract claims, contributions, assumptions, peer review, review, claim extraction.
• Use when: review/peer review or evidence audit, requiring the claim list to be persisted and traceable to the original text location (section/page/quote).
• Skip if: no available manuscript/full text (for example, missing output/PAPER.md or equivalent text).
• Network: none.
• Guardrail: each claim must carry a locatable source pointer; distinguish empirical vs conceptual claims.

Transforms manuscript text into a traceable claim ledger for paper-review.

Input

• output/PAPER.md

Output

• output/CLAIMS.md
• output/CLAIMS.jsonl (review-claim.v1, one addressable claim per line)

Contract

Each claim block must include:

• claim text
• type: empirical or conceptual
• scope
• source pointer back into output/PAPER.md

The Markdown and JSONL files are two views of the same claim records. Downstream skills should prefer JSONL and retain Markdown fallback for older Workspaces.

Script boundary

scripts/run.py should:

• detect claim-like sentences
• normalize them into stable claim blocks
• attach source pointers
• separate empirical and conceptual claims

Keep parsing and ranking heuristics in shared review tooling, not in the skill script.

Acceptance

• output/CLAIMS.md exists
• output/CLAIMS.jsonl exists and every record has a stable claim_id
• every claim has a source pointer
• empirical and conceptual claims are separated

Non-goals

• judging whether a claim is good
• generating evidence gaps
• writing review prose