Experimental contract
What this family tests
controlled synthetic recovery and registered real-data calibration
- Controlled relational recovery
- Post-confirmatory dimension diagnostic
- Pooled Hodge baseline
- MovieLens registered negative calibration
Book-to-code crosswalk
The highlighted Experiment cards covered here
- Experiment: higher-order relational recovery.12.1 From Point Clouds to Witnessed Relations · 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.
- implementation · public-pinned —
lincs-radar:relational_descent.py↗Open the pinned public source file. - runner · public-pinned —
lincs-radar:run_relational_dimension_diagnostic.py↗Open the pinned public source file. - runner · public-pinned —
lincs-radar:run_hodge_baselines.py↗Open the pinned public source file. - runner · public-pinned —
lincs-radar:run_movielens_experiment.py↗Open the pinned public source file.
Author-declared entry points
relational_descent.pyrun_relational_dimension_diagnostic.pyrun_hodge_baselines.pyrun_movielens_experiment.py
Resolved code
implementation · 3
result-record · 4
Evidence record
Artifacts and frozen runs
Result artifacts
RELATIONAL_CONFIRMATORY_RESULTS.mdRELATIONAL_DIMENSION_DIAGNOSTIC.mdHODGE_BASELINE_RESULTS.mdMOVIELENS_RESULTS.md
Run records
No run-level packet is registered. The family retains code-level provenance, but public run reproduction still requires curation.
Evidence boundary
The synthetic advantage is specific to the declared two-dimensional bottleneck, and the MovieLens study is a retained negative result rather than evidence of universal relational benefit.
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.