CLAUDE.md

Router. This file is deliberately short: it is loaded into every session in this repository, whichever task you are here for. It names the one rule that binds every task, then sends you to the file that governs yours.

Which file governs you

Routed by what you are about to do, not by who you are. Someone who unzipped a release and someone who cloned the repository read the same two files; which one applies changes the moment they start editing src/.

If you are...	Read	Then stop
Drafting content with this pipeline -- a survey, thesis chapter, textbook chapter, tutorial, deep-research report -- or revising one	AGENTS.md	That file and the skill you are running are the whole contract. You do not need anything below
Changing this repository's own code -- anything under src/, scripts/, tests/, bench/, .github/	DEVELOPER-AGENTS.md, which governs, then docs/CODE-STANDARDS.md for what the code must look like	--
Changing this repository's prose -- docs/, README.md, or these files	DEVELOPER-AGENTS.md for the commit/PR conventions	--

Doing both in one session is normal -- drafting with the pipeline and then fixing a bug you hit. Re-read this table at the switch; the developer rules do not apply to a draft, and the drafting rules do not apply to src/.

SOUL.md is the one-page why behind all of it, and the tie-breaker when two files seem to disagree.

The one rule that binds every task

A citekey may be used only if it appears in the human's own .bib export and was picked up into the ledger by a real parse of a real PDF.

Never fabricate, guess, generate or rewrite a citekey -- not in a draft, not in a test fixture, not in an example in a doc. Fabricated placeholder references have reached real published papers; preventing that is what this project is for. AGENTS.md has the rule in operational terms, SOUL.md has why it cannot bend.

Why this file is a router and not the guidance itself

Three reasons, so the next person does not consolidate it back:

1. The two audiences need opposite things. A drafting session should not be carrying the release process, the coverage bar and the module boundaries in its context; a refactoring session should not be carrying the dossier format. Splitting by task keeps each session's standing instructions to what actually applies.
2. Everything ships. scripts/release.py bundles every prose document -- AGENTS.md, DEVELOPER-AGENTS.md, SOUL.md, docs/ -- because they cross-reference each other by name and dropping one leaves dangling links in the rest. So the developer guidance reaches a release consumer regardless; the routing is what stops it reaching a drafting session, which is the distinction that matters.
3. It has to degrade. Different agents load different files -- CLAUDE.md, AGENTS.md, or neither. This file therefore duplicates no guidance and imports nothing: whichever of the two an agent picks up, it finds a pointer to the other by name rather than half a ruleset. AGENTS.md carries the same pointer in the other direction, and has since before this file existed.