result-to-claim

# Result-to-Claim Gate Experiments produce numbers; this gate decides what those numbers *mean*. Collect results from available sources, get an objective judgment, then route based on the verdict. ## Context: $ARGUMENTS ## Constants - **REVIEWER_MODEL = `gpt-5.4`** - Used via a secondary Codex agent for objective claim assessment. ## When to Use - After a set of experiments completes (main results, not just sanity checks) - Before committing to claims in a paper or review response - When results are ambiguous and you need an objective second opinion ## Workflow ### Step 1: Collect Results Gather experiment data from whatever sources are available in the project: 1. **W&B** (preferred): `wandb.Api().run("<entity>/<project>/<run_id>").history()` - metrics, training curves, comparisons 2. **`EXPERIMENT_LOG.md`** - full results table with baselines and verdicts 3. **`EXPERIMENT_TRACKER.md`** - check which experiments are done vs still running 4. **Log files** - `ssh server "tail -100 /path/to/training.log"` if no other source 5. **`docs/research_contract.md`** or project notes - intended claims and experiment design Assemble the key information: - What experiments were run (method, dataset, config) - Main metrics and baseline comparisons (deltas) - The intended claim these experiments were designed to test - Any known confounds or caveats ### Step 2: Secondary Codex Judgment Send the collected results to a secondary Codex agent for objective evaluation: ```text spa...