Experimental contract
What this family tests
controlled workflow studies
- Cheap Lie-bracket probe calibration
- Validation-call economy study
- Skill-library scale experiment
- Anchor-chain benchmark
Book-to-code crosswalk
The highlighted Experiment cards covered here
- Experiment: the retained empirical hierarchy14.8 Application probes · reported result or audit · direct chapter family
Implementation map
From entry point to source surface
Start here
These concrete files are selected from the complete registered source surface to orient the reader.
- runner · public-pinned —
lincs-lasko:scripts/run_anchor_chain_benchmark.py↗Open the pinned public source file. - runner · public-pinned —
lincs-lasko:scripts/run_anchor_chain_scale.py↗Open the pinned public source file. - runner · public-pinned —
lincs-lasko:scripts/analyze_skillopt_run.py↗Open the pinned public source file.
Author-declared entry points
scripts/run_anchor_chain_benchmark.py
Resolved code
Evidence record
Artifacts and frozen runs
Result artifacts
benchmark summaries and workflow traces
Run records
No run-level packet is registered. The family retains code-level provenance, but public run reproduction still requires curation.
Evidence boundary
Compute savings are relative to the supplied skill language and validation protocol; the system does not invent that language.
This registry links the experiments reported by the three books to their executable or archived code surfaces. A code link establishes traceability, not independent reproduction, correctness, or support for a claim beyond the experiment's stated boundary.