Proofs
Can a model find a matching identity, recover a hidden subtotal, or preserve enough information through a nested summary? These experiments isolate one relationship at a time. Controls remove the signal, change the pairing, or deliberately discard information so that a useful prediction has a clear explanation.
Each scenario opens with a short Insights summary: what the proof shows, why it matters, and where the conclusion stops. A model tree, contrasting records, and expandable code sections explain the experiment together. Each page comes from the same Python file you can download and run. The collection includes retention, adaptation, reset, deactivation, and deletion after schema mutations.
The capability experiments P071–P078 test unfamiliar instruction combinations, rules inferred from examples, frozen representation transfer, incomplete evidence, larger and two-hop relations, contextual inconsistency, numerical representation tradeoffs, and hidden-group recovery. Their controls distinguish a successful local task from broader reuse of a learned relationship.
Read The Status
Statuses summarize recorded evidence in proofs/results.yaml. Each experiment has a stable ID, such as P014, independent of its title or script name. Some experiments are designed to confirm a limitation, such as losing count when averaging identical values. Their expected outcome is useful evidence about model design. Each page provides commands to reproduce the experiment. Acceptance thresholds are labeled as gates. Each page shows the latest full run’s measurements, with behavioral checks collapsed by default. Expand them to inspect the individual criteria. Short smoke runs never replace full experiment results.
| Status | What the evidence establishes |
|---|---|
| Passing | The reported experiment clears its gates, usually for one deterministic seed. The result is provisional: broader stability or generalization remains to be established. |
| Limited | The experiment successfully reproduces an expected loss of information or unsuccessful modeling route. Its checks are met when that limitation appears; this is not a failed experiment. |
| Partial | Some behavior is supported, while a broader claim remains untested or inconsistent across recorded conditions and seeds. |
| Failing | The latest full run completed but did not meet every stated behavioral criterion. |
| Error | The latest full run could not complete. Its error is recorded separately from model quality. |
| Missing | No full experiment run has been recorded. |
These are empirical checks of learned behavior. Training speed and memory use require separate measurements. Learned arithmetic is approximate; use exact preprocessing for fixed business rules that must be exact.
Explore The Proofs
Sort by ID, Proof, Family, or Status, using the column headings or the order menu. Filter by an ID, task, family, or status, then select any part of a proof’s row to explore its insights, examples, and evidence.
What Strengthens A Result
The shared protocol calls for three paired data/model seeds before promoting a core claim, plus at least ten seeds to calibrate a new threshold. Held-out splits, matched baselines, and controls must continue to support the claimed relationship. Each page identifies the additional work for that scenario.
Regression errors are generally reported as nRMSE: model RMSE divided by the RMSE of a baseline that predicts the training mean. Lower is better; 1 matches that baseline. Other baselines, such as an oracle with information removed, are identified on the relevant page. Classification pages report accuracy or ROC AUC, together with the appropriate chance or corruption control.
Run uv run python proofs/run.py --list to list proof IDs, or uv run python proofs/run.py P014 --accelerator gpu to run one on a GPU. Each script uses seeded synthetic records and records its metrics, controls, seed, environment, and source fingerprint. make proofs runs all scripts serially.