draftlisted

# draft ## When to use Writing anything longer than a note — a section, an argument, a paper — or working out the derivation a proposition depends on. ## Method 1. Ground first: `magi search "<what you need>"` and `magi wiki context --name <concept>` for what the project already says. Write from what you read, not from what you remember. 2. Write to `drafts/<slug>.md`. Drafts are yours to edit freely; they are not compiled and they never move into `wiki/`. 3. A draft that supports a proposition is its derivation. Point the proposition at it (`--derivation drafts/<slug>.md`) so that editing one shows up as debt on the other. Scripts that check it live in `tools/`, never in a CLI's scratch directory, and are named with `--evidence tools/<script>`. 4. Exploratory prose that is not yet a claim goes in a `> [!draft]` callout, so a later reader can tell working-out from conclusion. 5. Citations: `magi bib --all` for what the draft cites, `--fetch` to fill in what the cards lack. 6. Before calling it done: `magi verify <claims.json> --project-dir .` for the claims, `magi math check` for the formulas, `magi stats verify-refs <draft.md>` for the links. verify and verify-refs each take their file. ## Rules - **Never** cite a reference card as a source. Cite the `raw/` file behind it; the card is a compiled view and can be wrong exactly where it matters. - **Never** move a finished draft into `wiki/`. A conclusion becomes a proposition in `threads/`