paper-reproducelisted

## Graph Mapping The paper's argument is the object under test. Extract it into the graph first; reproduction then tests whether those Grounds hold under independent execution. ``` paper conclusion -> Claim paper stated result -> pending Statement(Ground role), source=observed, verification=pending paper inference from result to conclusion -> Warrant paper method/standard behind the inference -> Backing paper acknowledged exception -> Rebuttal ``` Granularity: - extract the Claims whose verdicts matter; do not force the whole paper into one giant Claim - attach each stated result to the specific Claim it bears on - distinct results, conditions, populations, or scopes are separate pending Grounds - a paper sub-Claim used as evidence for another Claim -> reference the sub-Claim's id directly in the consuming Warrant's `ground_ids` ## Obligations Object-layer work in this channel — implementation, data download, computation, analysis, debugging — is valid only when it extracts, tests, audits, or reconciles a node or Claim status in the reproduction graph. A run not tied to a Ground it verifies or contests is loose work. | Graph state | Required action | |---|---| | A paper conclusion whose verdict matters has no Claim | `create_claim`, status `proposed` | | A paper-stated result must be tested | `create_statement(source="observed", verification="pending")` | | A Claim's Grounds have no inference principle | `