Skip to content

Latest commit

 

History

History

README.md

OPH Reference Documents, Registers And Research Notes

This directory contains the canonical reference documents, the generated scientific registers, repository policies, and the research notes that accompany the executable lanes. Research planning and task state live in this repository's GitHub issues. Scientific results live in the papers, Lean library, executable code, and evidence artifacts. The registers index those results, and each research note states a result that its code package verifies.

If you are new to OPH, the strongest starting material lives outside this directory. The technical paper states the primary technical account. The OPH textbooks work through the basic derivations with the math taught along the way. The interactive simulation renders real run data so you can watch the universe assemble itself.

Layout

Path Contents
This folder Canonical references and the common-objections guide
registers/ Generated V3 registers and ledgers
research/ Research notes, each verified by a code lane
instrument_specs/ Instrument designs listed in the instrument register
policies/ Data, hardware-evidence and writing policies

The five canonical references keep fixed paths because verifier receipts, the Lean core and frozen custody records cite them by path. Published essays link to the common-objections guide at its path in this folder. Records written before 2026-10-04 cite the other documents at docs/<NAME>.md or extra/<NAME>.md; each file keeps its name in the folders above.

Three Reading Routes

Canonical References

Each quantitative closure condition is tracked as a GitHub issue labeled closure, with its evaluation boundary and required completion stated on the issue.

Registers

Each register is generated from a JSON source by a tool in tools/. The first line of every page names its source and generator; edit the source, then regenerate.

  • Premise Register names each V3 input and its consumers and classifies each evidence path by its scientific role.
  • Observation Ledger records the physical targets, adequacy rungs, premise ancestry, frozen-target links, and evidence paths.
  • Emergent-Instrument Register lists the simulation-instrument designs and frozen instruments of the adequacy program.
  • Constants Ancestry declares the complete input ancestry of each constants family against the premise register.
  • Selection Ledger records the selections that consensus forces, with the exposed premises and proofs behind each row.
  • Gravity Premise Ladder types each gravity interface with a premise packet, a theorem or countermodel, and a deletion test.
  • Standard Model Correspondence classifies each Standard Model term and sector by what OPH supplies.

Research Notes

Each note states a construction, theorem or audit in Markdown; the code package named with it verifies the note and pins it by path and SHA-256 in its receipt. A change to a note therefore rebuilds that receipt in the same commit. New notes go in this folder; extra/ holds TeX papers only, and the claim registry check rejects Markdown notes there.

Clocks and source realization. These notes build on one another in this order:

  1. Massive flights, resolved reads and observable clocks, verified by code/m1_operational_clocks.
  2. Coherent source codes, entropy selection and charged clocks, verified by code/m1_source_realization.
  3. Fermionic clocks and reads from the proper-code source, verified by code/m1_fermionic_source.
  4. Fixed-rate noise and protected source reads, verified by code/m1_fixed_noise.
  5. Source histories with noisy records and control, verified by code/m1_noisy_records.
  6. Fixed-strength quantum computation and live public records, verified by code/m1_expander_archive.
  7. Full-interface leakage, dissipation and source refinement, verified by code/m1_leakage.
  8. A filled source vacuum, positive excitation energy and readable clocks, verified by code/m1_sea_energy.

Gravity and the dark sector.

Independent comparison.

Existing-theory audit and simplification.

Instrument Specifications

Evidence, Data And Writing Policies

  • Hadron Data Policy defines provenance and promotion rules for the hadronic pipeline.
  • Hardware Evidence Bundle H defines the evidence and attestation contract for physical hardware claims.
  • Writing Style Guide defines the project’s reader-facing prose conventions.
  • The IBM Quantum Cloud code and data archive contains the reproducible engineering benchmark, receipts, and interpretation boundary beside their executable producers.
  • Simulator outputs have no theorem or empirical-promotion authority in the paper stack. A simulator count, replay, fit, or diagnostic closes no analytic or physical receipt; theorem status needs analytic proof packets, and empirical promotion needs public physical evidence bundles.

Reader Support