Experimental contract
What this family tests
document extraction and benchmark comparisons
- Four-domain causal-claim extraction audit
- Geometric Transformer versus UMAP manifold ablation
- UniCausal extractor comparison
- Homotopy-aware claim normalization audit
Book-to-code crosswalk
The highlighted Experiment cards covered here
- Experiment: Democritus GT rendering ablation.16.3 Relational Geometry with the Geometric Transformer · reported result or audit · direct chapter family
- Experiment: Democritus–UniCausal extraction comparison.16.7 External Calibration against UniCausal · 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 —
democritus-openai:pipelines/pipeline_llm.py↗Open the pinned public source file. - implementation · public-pinned —
democritus-openai:scripts/manifold_builder.py↗Open the pinned public source file. - implementation · public-pinned —
democritus-openai:scripts/visualize_manifold.py↗Open the pinned public source file.
Author-declared entry points
pipeline_llmdriver.py
Resolved code
Evidence record
Artifacts and frozen runs
Result artifacts
saved extraction outputs and GT/UMAP ablations
Run records
No run-level packet is registered. The family retains code-level provenance, but public run reproduction still requires curation.
Evidence boundary
Extracted claims and rendered manifolds do not certify causal truth or identification.
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.