Skip to content

Latest commit

 

History

History
244 lines (207 loc) · 14.7 KB

README.md

File metadata and controls

244 lines (207 loc) · 14.7 KB

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 from declared candidate models; it does not demonstrate that a physical universe has been reconstructed.

Layout

Path Contents
This folder The basis, the paper set, canonical references and the common-objections guide
registers/ Generated V3 registers and ledgers
research/ Research notes, each verified by a code lane
policies/ Data, hardware-evidence and writing policies

Keep this directory limited to shared references, scientific registers and cross-project research results. Maintain existing pages instead of adding individual run reports or duplicate status summaries. Implementation-specific mathematics belongs with its owning code. Editorial dates and migration narratives do not belong in maintained prose; scientific provenance stays with the evidence that requires it. Preserve valid links and source commitments when consolidating documents.

Three Reading Routes

Basis And Paper Set

  • The OPH Basis states the closure hypothesis, the no-outside rule, the agreement condition and the executable specification, and how the theorem-library premises A1, A2 and A3 relate to them.
  • The Paper Set records the model milestone, the role of each paper and the archived papers.

Canonical References

  • Interpretation and Working Terms distinguishes complete-history closure, intrinsic computation, emergent-physics proposals, mathematical fixed points and the different uses of time.
  • Premise Reference gives the formal statements of the theorem-library premises A1, A2 and A3.
  • Source and Repair-Law Selection separates the executable candidate inputs, derived consequences and physical identification.
  • Frozen-Prediction Ladder records tests whose conditions are fixed before the comparison data are examined.
  • Postdiction Ledger records comparisons with measured values and their input ancestry.
  • Empirical Status inventories laboratory comparisons, reference-value and hardware tests, and what they can decide about the executable repair rules.
  • OPH Falsification Program lists only mature mathematical and realized-branch falsifiers.
  • Programme-wide obstruction search seeks inconsistency, joint-realization impossibility and limits on explanatory unification, with explicit exclusion and stopping criteria.

The physics issues assign bounded work on the common repair model, its tests and existing-evidence audits. Historical closure issues retain their scientific boundaries; administrative closure does not discharge a physical premise.

Model Construction Status

Find the simplest shared repair rule that satisfies the known constraints. Reuse the existing arguments before adding mechanisms; require geometry, reversible response and clocks to connect through the same source process.

Established Mathematics for Observer Agreement maps distributed recovery, sheaf diffusion, boundary extension and contextuality to explicit candidate obligations. Its work products govern theorem reuse and the distinction between recovery, exact agreement and physical law selection.

Repair Laws explains which parts of the repair law are forced, which are free, which members of the admissible family the model executes, and which tests tell them apart. This maintained research summary has a separate role from the generated registers.

Runnable Model is the live home of observer and repair-law construction, including executable native and P-dependent binary observers, capacity checks and local-tick results. Its construction guide records the contracts, constructed connections and missing physical inputs. Its work ownership links parallel construction, physical tests and audits; its release policy ties paper releases to an approved model milestone, which the paper set records. Tested model code, correctness fixes and reproducibility checks are published between releases.

The model–theorem premise map connects the candidate to existing theorem premises and their closure conditions. It is generated from the model map in tracking/ and checks references and coverage, without certifying that every theorem antecedent has been extracted or discharged. The scientific claim registry retains authority over established claims; these documents track the construction intended to supply their inputs.

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. The five-ledger map groups the sources into the claims, premises, predictions-and-tests, evidence and papers ledgers.

  • 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 maintained construction or theorem tied to its verifying code package. Source-pinned notes require matching receipt updates when their content changes. Consolidate overlapping notes and keep implementation contracts beside the code; extra/ holds TeX papers only.

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