hypothesislisted

# /hypothesis — Populate docs/hypotheses/ Draft or extend a project's `docs/hypotheses/` folder (or a legacy flat `docs/hypotheses.md`): a structured mapping of theoretical predictions to pre-existing evidence and concrete empirical tests the project can run. Each hypothesis is a single testable claim with its theory, evidence, specification, and data requirement spelled out. ## Locating the hypotheses doc Discovery order, first hit wins: 1. `$PROJ/docs/hypotheses/index.md` (folder mode — default) 2. `$PROJ/docs/hypotheses.md` (flat file — legacy) If neither exists, create **folder mode** (`docs/hypotheses/`, `index.md` + one file per hypothesis) regardless of entry count — it is the default per `project_docs_contract.md` §5 and matches the sibling `docs/findings/` layout. The flat file is **legacy**: keep maintaining existing `docs/hypotheses.md` files, but do not create new ones — migrate them to a folder when convenient (see "Folder mode" below). ## Arguments - `/hypothesis` — infer project from the current working directory. - `/hypothesis <project-slug>` — run against a specific project under `projects/`. - `/hypothesis --audit` — do not write; report gaps, dangling refs, and orphan theories. - `/hypothesis --extend` — preserve existing entries; only append new hypotheses suggested by current evidence/literature. - `/hypothesis --update <H#> [--artifact <AN-id-or-build-path>]` — **surgical single-entry edit**. Update the status block (or evidence/test fields) of o