Skip to content

Paper to code (crosswalk)

A row-by-row map from each section / box of the manuscript to concrete code, the command that exercises it, and the artifact it produces. The point of this page is "given a paper claim, where do I look in the repo?" and "given a CI run, which paper claim is this artifact evidence for?"

Paper sections

Section references point at paper/main.tex in the accompanying manuscript.

Paper §/Box Short text Files / functions Command Artifact produced
§4.2 NC1 loop-dominance: M (dB) ≥ Mmin → nc1 bit m_db; estimate_L; run_baseline ldtc run --config configs/profile_r0.yml artifacts/indicators/ind_*.{jsonl,cbor}; artifacts/audits/audit.jsonl
§4.3 SC1 resilience: δ ≤ ε and τ_rec ≤ τ_max → sc1 bit sc1_evaluate; omega_power_sag ldtc omega-power-sag --config configs/profile_r0.yml --drop 0.3 --duration 10 audit.jsonl; verification_timeline.png; sc1_table.csv
§4.1 (Δt); §4.5 LREG and Δt governance LREG; DeltaTGuard; AuditLog ldtc run --config configs/profile_r0.yml audit.jsonl with dt_changed; hash chain
§4.6 Box 1a Smell tests / invalidations smelltests Negative-control configs audit.jsonl run_invalidated with reason
§6.2.1 Refusal semantics (T1 to T3) refusal; omega_command_conflict ldtc omega-command-conflict --config configs/profile_negative_command_conflict.yml --observe 2 audit.jsonl refusal_event
Appendix A Derived device-signed indicators only build_and_sign; IndicatorExporter Produced automatically; python scripts/verify_indicators.py JSONL + CBOR; signature verified
§4.1 (C/Ex); §4.6 Deterministic C/Ex partition PartitionManager; greedy_suggest_C ldtc run --config configs/profile_r0.yml audit.jsonl partition_flip; Ω freeze
§6.5 Ω battery primitives omega.power_sag; omega.ingress_flood; omega.command_conflict ldtc omega-* commands audit.jsonl omega_event; figures bundle
Methods §8.6 Calibration to R* thresholds scripts/calibrate_rstar.py python scripts/calibrate_rstar.py ... configs/profile_rstar.yml; summary JSON

How to read a row

Take the first row, NC1, as an example:

  • The paper defines NC1 as M (dB) ≥ Mmin, window-by-window.
  • That definition is implemented by m_db (which computes 10 · log₁₀(𝓛_loop / 𝓛_ex)) and the threshold check inside run_baseline.
  • ldtc run --config configs/profile_r0.yml exercises the path end-to-end on the bundled R0 profile.
  • The path produces artifacts/indicators/ind_*.{cbor,jsonl} (signed) and artifacts/audits/audit.jsonl (hash-chained). Reading the nc1 field of any indicator tells you whether NC1 passed for that audit-chain head.

The other rows follow the same shape: paper claim → code → command → file you can grep.

Where to find the supporting tests

Concern Test files
m_db and sc1_evaluate tests/test_metrics.py, tests/test_sc1.py
Estimators (linear / MI / Kraskov) tests/test_estimators.py, tests/test_estimators_properties.py
Partition manager and greedy growth tests/test_partition.py
LREG enclave invariants tests/test_lreg.py
Audit-chain integrity tests/test_audit_chain.py
Smell tests tests/test_smelltests.py
Indicator signing and exporter tests/test_attest.py, tests/test_exporter.py
Refusal arbiter tests/test_refusal.py
Δt governance tests/test_dt_guard.py
Ω modules tests/test_omega_*.py
CLI orchestration tests/test_cli_*.py

(Run pytest -q to execute the full suite.)

See also