Citation — stage 10

Citation — stage 10

Make every author-used reference traceable, real, correctly identified, and honestly connected to the claim it is supposed to support. Treat formatting, metadata existence, publication-integrity facts, and semantic support as four different questions.

Read citation-resource-map.md before a full manuscript audit. Read references/registry_contract.md before producing or consuming the canonical registry. Read references/locator_audit.md before judging claim support.

Stage contract

• Consume paper-writing's light.paper_claims.v1, exact claim/source locators, current claim text hashes, reviewer-bound citation-support hashes, manuscript, figures/tables, supplement, and reference candidates.
• Reuse literature-search provenance as input evidence; independently verify the references the author actually keeps.
• Emit light.citation_registry.v1, BibTeX, CSL JSON, source-level evidence, failure records, claim-edge review, citekey audit, and light.findings.v1(producer=citation).
• Keep stage 10's only critical gate citation_verify: confirmed missing works and chimeric citations. Metadata conflicts, unavailable sources, claim relevance, formatting, and publication-update alerts are warn/skip.
• Fix citation failures inside stage 10. ROUTES has no key 10; never invent a back-edge.
• Hand references.bib, citekey-audit.json, registry and delivery.json to typesetting. Typesetting compiles and checks keys; it does not re-decide authenticity. delivery.json must declare status and per-deliverable sha256: hashes so typesetting can reject stale or edited handoffs.

Non-negotiable rules

1. Never invent a reference, DOI, author, year, venue, citekey, locator or support verdict.
2. Never call a network failure, rate limit, 5xx, authentication failure, or index miss “this work does not exist.”