cruxlisted

# crux — an agentic research companion `crux` turns a research program into a **scientific-method lab notebook**: a tree of **Questions** (what we don't know) and **Hypotheses** (falsifiable, testable leaves), rooted at a **Project**. A deterministic engine (`scaffold/`, a Python CLI) does the bookkeeping — IDs, the `Parent::` tree, validators, the evidence-ledger roll-up, the review gate, and regenerating `META.md` + `EXPERIMENTS.md`. The vault is plain markdown, openable in Obsidian (graph mode shows the question/hypothesis tree). You (the Agent) operate the engine on the researcher's behalf. The engine never judges; **you** supply the science and the researcher (the **PI**) makes the calls. ## When to use this The user is running a research program and wants it tracked rigorously: opening research questions, designing experiments as problem → hypothesis → verifiables → findings, recording results, deciding when a question is answered, and updating what's still open. Not for one-off tasks with no hypothesis, and not for launching the runs themselves (crux *records* runs; your training/job harness launches them). ## The model - **Project** — the root node, one per vault. - **Question** (`q*`) — has **no verifiables of its own**; it is resolved by **aggregating its children's findings**. Questions nest (a question's parent can be another question). - **Hypothesis** (`h*`) — a falsifiable leaf under a question, with `## Verifiables` (pre-registered checks), `## Findi