preregisterlisted

# Preregister This skill supports "decide before observing" for confirmatory claims. Exploratory runs may still use seed_perturb / pin_metric, but any number intended as a main publication claim should have a matching prereg row first. ## When to invoke - Before a result is promoted from exploratory to a confirmatory manuscript claim. - Right after `bt-tournament` returns the top-2 hypotheses when the next run is explicitly confirmatory. - Whenever the user types `/preregister`. ## Required arguments | arg | meaning | example | |---|---|---| | `hypothesis_id` | id from `mem_nodes` (kind=hypothesis) | `hyp_a3f9...` | | `metric_name` | exact claim text the engineer will pin later | `"test accuracy"` | | `direction` | `higher_better` or `lower_better` | `higher_better` | | `threshold` | number that separates `met` from `missed` | `0.85` | | `seed_count` | how many seeds the seed_perturb call must use | `5` | | `alpha` | nominal Type-I error rate | `0.05` | | `mc_correction` | `bh` (Benjamini-Hochberg, default), `bonferroni`, or `none` | `bh` | | `heldout_dataset` | optional dataset name to be queried via query_heldout | `mnist-test` | ## Workflow 1. Call `mcp__verify__list_preregistrations(hypothesis_id=...)`. If a row exists with status `open`, do not fail the session. Ask whether to reuse that lock, withdraw it outside this tool, or create a separate confirmatory prereg for a genuinely different metric. 2. Call `mcp__verify__preregister(...)` with the exact metric text