manuscript-provenance

# Manuscript Provenance Audit **Pipeline position:** Phase 2a (grounding audit). Runs in parallel with `manuscript-typography`. Depends on: content settled after Phase 1 fixes. Produces macro manifest consumed by `manuscript-review` Pass 13 (Cross-Element Coherence). ## Purpose Verify that a manuscript is a faithful rendering of computational outputs. Every number, table, figure, category label, ordering, and threshold in the document must trace to a specific script, config file, or pipeline output. Manual data entry in a manuscript is a reproducibility defect. This skill produces a provenance map — a structured report linking each manuscript artifact to its generating code — and flags every break in the chain. Companion skill: `manuscript-review` audits the document as prose (structure, argumentation, citations). This skill audits whether the document content is computationally grounded. Run both for complete pre-publication coverage. ## Boundary Agreement with manuscript-review | Concern | manuscript-review | This skill (manuscript-provenance) | | ------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------- | | Reproducibility | Does the paper describe enough to reproduce? (§6) | Does the code actually produce what the paper claims? (§1, §7) | | Figures/Tables ...