Orientation guide

Choose a 10-minute path before opening the full archive.

This page is the reader router for the coordinated 70-entry release. It is built to lower the first barrier for outside readers: pick the question closest to your field, read a small set first, then return to the manuscript archive.

Claim authority. Scientific claims are defined by the manuscripts. Guide text is a routing aid only.
First 10 minutes

Get the shape of the work before reading technical detail.

One-sentence thesis

CHC is a bounded manuscript program for asking which physical structures become stable records, shared facts, interfacial outcomes, and testable cross-domain constraints.

One-paragraph thesis

The guide is meant to help a reader choose an entry route before opening the full archive. It does not ask researchers to accept CHC as a whole or to replace established tools. It separates root framework claims, measurement and record layers, objectivity criteria, material-interface branch budgets, public-data stress windows, and claim-boundary checks, while keeping the manuscripts and Zenodo archive as the authority for exact statements.

What this guide is for

  1. Find why a bounded part of CHC may be worth checking before reading details.
  2. Separate root framework, measurement, cosmology, gauge, and completion layers.
  3. Keep visual guide material secondary to manuscript records.
  4. Use the canonical Zenodo DOI when citing or checking the fixed v1.0 archive.

What not to expect

  • Not an empirical confirmation statement.
  • Not a standard-model, general-relativity, or cosmology replacement announcement.
  • Not a product, benchmark, or implementation disclosure.
  • Not a substitute for paper assumptions and exclusions.
  • Not a claim that every lane is owner-level closed.
  • Not a replacement for archive records or manuscript PDFs.
For outside researchers

Start from the extra question CHC asks on top of existing tools.

CHC is not offered here as a superior replacement for QFT, GR, cosmology, or open quantum systems. Its possible value is narrower: it asks which calculated structures become stable records, shared facts, interfacial outcomes, or bounded public-data constraints. These routes are designed so a reader can test one claim family without accepting the whole framework.

See full reading paths
ENTRY 01

Detector records

When does a threshold crossing become a recorded event?

Start where the series separates switching, failed transients, local commit, latching, and durable record-counting.

Claim family
Detector-local event closure and durable record formation.
Standard tools retained
Propagation, detector physics, thermodynamic switching models.
What CHC adds
A typed separation between threshold crossing, local commit, latching, and record status.
Failure condition
No declared detector family supports the cross-observable record-side constraints without retuning.
ENTRY 02

Classical objectivity

When is decoherence not enough for a shared fact?

Read the redundant-record route as a stricter objectivity filter using accessibility, consensus, discord leakage, and pointer stability.

Claim family
Redundant-record objectivity and shared-fact certification.
Standard tools retained
Open-system dynamics, decoherence, pointer-state analysis, fragment access models.
What CHC adds
A certificate layer separating decohered states from publicly recoverable, consensus-bearing records.
Failure condition
The added certificate conditions do not exclude or organize any case beyond ordinary decoherence language.
ENTRY 03

Interfacial outcomes

How does absorbed excitation become externalized, retained, or dissipated?

Use the branch-budget route as a middle-layer interface grammar, explicitly not as a Maxwell, QED, or detector-microphysics replacement.

Claim family
Interfacial branch budgets for absorbed excitation.
Standard tools retained
Maxwell/QED calculations, material response, transport, dissipation, detector microphysics.
What CHC adds
A record-facing budget grammar for externalized outcome, retained/internal ledger, and dissipative sink branches.
Failure condition
Branch labels cannot be tied to conserved budgets, measured channels, or reproducible interface regimes.
ENTRY 04

Public stress tests

Can bounded CHC constraints survive public-data checks?

Open the witness-window papers first, then check whether the declared support or stress labels stay within their non-claim boundaries.

Claim family
Public-data witness windows, exclusions, reproductions, and holdout-style stress tests.
Standard tools retained
Public catalogs, standard statistics, astrophysical/cosmological baselines, reproducibility checks.
What CHC adds
A claim-boundary discipline for separating support, stress, nonexclusion, block, and failure labels.
Failure condition
The windows require post-hoc retuning, overstate support labels, or fail to produce bounded exclusions.
For skeptical readers. The intended first test is not whether the full CHC program is true. Start with one bounded claim family: detector-record formation, shared-fact certificates, interfacial branch budgets, or public-data stress windows. Each should be judged by its stated assumptions, recovery limits, exclusion conditions, and whether it survives as more than retrospective reinterpretation.
Failure condition. If no bounded claim, exclusion, reproduction, or holdout-style test survives scrutiny beyond retrospective interpretation, CHC should be treated as a philosophical or heuristic framework rather than as a competing physical theory.
Concrete examples

What CHC is actually doing across the 70-entry archive.

A large theory archive is easy to misread as one sweeping assertion. This guide instead points to concrete moves: where CHC introduces a boundary distinction, what ordinary tools remain in force, and what would make the distinction useful, redundant, blocked, or false.

Open current review status
EXAMPLE 01
DE / CR2 / CMB

Cosmology as a sequence of declared windows

The cosmology-facing papers separate homogeneous phase-flat response, chronometer inference, bound-structure decoupling, and primary-sector ruler constraints. This lets a reader ask a narrower question than whether CHC replaces cosmology: which background, clock, ruler, or width statement is being made, and under which recovery or exclusion condition?

EXAMPLE 02
OPL / DBC / DTM / RSF

Measurement as threshold, commit, latch, and durable record

The measurement papers treat a detector event as a layered process: propagation reaches an effect domain, a local opening or threshold is crossed, a metastable device commits or fails to commit, and only some outputs become durable records. That grammar is useful because it can be checked directly against ordinary detector/readout models.

EXAMPLE 03
OBJ / RSF

Shared facts as public recoverability, not private decoherence alone

The objectivity route asks whether redundant records become publicly recoverable and consensus-bearing, rather than only decohered in a formal state description. Its review value is also its risk: if quantum Darwinism, spectrum broadcast structure, pointer stability, or fragment-access criteria already cover the case, CHC wording should be narrowed or retired.

EXAMPLE 04
CBL / CBL-VP0 / CBL-VP1

Interfaces as branch-budget accounting

The interfacial branch-budget route asks whether absorbed excitation can be tracked into externalized, retained, and dissipated channels under one calibration map. The companion records are useful as public-pilot and support surfaces, but they remain bounded: they can sharpen or downgrade the branch grammar without validating the parent claim by themselves.

EXAMPLE 05
FRC / TDC / QAC companions

Public data as stress surfaces, not loose support

The public-data companions make source basis, selection risk, reproducibility status, and downgrade condition visible. FRC/CHIME is the clearest example: the rerun surface is public, but the declared selection-stress condition fails, so the correct value is transparency and falsifiability rather than support inflation.

EXAMPLE 06
BH1 / BH2

Black-hole questions as accessibility and return-boundary problems

The black-hole papers approach horizons, evaporation, memory, and return kernels through conditional access and boundary structure. The series value is in making those assumptions explicit enough to compare with standard black-hole, JT-bath, and information-flow accounts.

Inspectable targets. The archive is worth reading where broad interpretive questions become named review surfaces: clocks, rulers, records, shared facts, interfaces, horizons, source-count windows, and public-data support lanes. The value is not a validation claim; each surface can be challenged, narrowed, blocked, or retired without accepting the whole framework.
Formula anchors

Use equations as navigational handles, not decorative authority.

Technical readers need concrete places to start. This guide surfaces a small set of readable anchors so visitors can see where to challenge the action, recovery conditions, boundary bookkeeping, and phase-loading identity.

Open CHC root
Use with the audit map. These equations are not decorative authority. They are review handles for the mathematical spine, recovery route, boundary bookkeeping, and typed sector language. Open featured audit cases.
Action-level entry

The CHC-min spine is the right first formula.

LCHC=MH22XHMΦ22XΦU(H,Φ)+Ω(Φf(H))\mathcal{L}_{\mathrm{CHC}} =-\frac{M_{\mathcal H}^{2}}{2}X_{\mathcal H} -\frac{M_{\Phi}^{2}}{2}X_{\Phi} -U(\mathcal H,\Phi) +\Omega(\Phi-f(\mathcal H))
Read as
A constrained scalar-sector grammar whose boundary conditions and reduction assumptions have to be checked in the root manuscripts.
Do not read as
A standalone proof that the whole archive is physically correct.
Recovery condition

Effective stiffness turns recovery into a checkable condition.

Meff2(H)MH2+MΦ2(f(H))2,ΞΛΞ4Meff2Hbg2M_{\mathrm{eff}}^{2}(\mathcal H) \equiv M_{\mathcal H}^{2} +M_{\Phi}^{2}\left(f'(\mathcal H)\right)^{2}, \qquad \Xi\sim \frac{\Lambda_{\Xi}^{4}} {M_{\mathrm{eff}}^{2}\lVert\nabla\mathcal H\rVert_{\mathrm{bg}}^{2}}
Read as
A reader-facing handle for asking where GR-like recovery, positive stiffness, and background limits are assumed.
Do not read as
A universal perturbation parameter that can be moved across every manuscript without its declared boundary.
Boundary term

Boundary conditions are part of the claim, not decoration.

SbdryCHC=Mh(MH2HnH+MΦ2ΦnΦ)S_{\mathrm{bdry}}^{\mathrm{CHC}} =\int_{\partial M}\sqrt{|h|} \left(M_{\mathcal H}^{2}\mathcal H\,\partial_{n}\mathcal H +M_{\Phi}^{2}\Phi\,\partial_{n}\Phi\right)
Read as
A reminder that Neumann or mixed-boundary readings need variational bookkeeping before being used in physical interpretation.
Do not read as
An extra term to invoke where ordinary Dirichlet conditions or manuscript assumptions do not call for it.
Phase loading

Sector exchange is an exact-identity style claim only where derived.

λ(a)=1ΛΞ4gδS(a)δH,μT(a)μν=ΛΞ4λ(a)νH\lambda_{(a)} =\frac{1}{\Lambda_{\Xi}^{4}\sqrt{-g}} \frac{\delta S_{(a)}}{\delta\mathcal H}, \qquad \nabla_{\mu}T_{(a)}^{\mu\nu} =\Lambda_{\Xi}^{4}\lambda_{(a)}\nabla^{\nu}\mathcal H
Read as
A route for discussing cross-sector exchange and phase-loading language under typed claim status.
Do not read as
A license to treat every particle-physics or cosmology statement as an empirically verified CHC residue.
Gate examples

Partial, failed, and non-overturn labels should be easy to see.

A researcher-facing archive becomes more credible when it does not flatten outcomes. These examples keep detailed evaluation material in bounded review language.

Open public-data labels
DE-VP0

Background non-exclusion

Useful as a bounded question about whether phase-flat background behavior remains inside ordinary posterior envelopes. It should not be presented as dark-energy closure.

CMB-VP0

Primary diagnostic partial

Width, acoustic-angle, linked-ruler, and later-transfer checks should be separated so a reader can challenge the exact gate that is being invoked.

FRC-VP2

Selection stress

The CHIME route is a strong public negative example: high selection-response variability is preserved as stress, not converted into support.

TDC-VP2

Relaxed proxy non-overturn

The time-delay lensing route is best read as proxy-level stress language with mass-profile and kinematic limitations explicit.

ULS

Typed claim promotion

Exact, Recover, Struct, Exclude, and Compat roles help readers avoid mixing theorem-like identities, recovery limits, public-data labels, and conjectural bridges.

Phase Origin comparison

The name is useful because phase origins matter in several technical settings.

The cryo-EM and quantum-chemistry comparison is valuable as naming and orientation. It should be stated as an analogy about phase readability and gauge discipline, not as evidence that CHC is true.

Domain Technical setting Phase-origin role Boundary
CHC Covariant scalar-tensor and field-theory archive Uses a phase-background reference route to organize recovery, boundary, and sector-exchange questions. Scientific value still depends on manuscript-level assumptions and external review.
Cryo-EM Fourier-space image processing Phase-origin handling makes Fourier phase structure readable against the intended real-space reference. An analogy for phase readability, not evidence for CHC physics.
DIRAC / DALTON Relativistic quantum chemistry Gauge or phase-origin choices help keep magnetic-response and London-orbital calculations interpretable. An analogy for origin discipline, not a cross-domain proof.
Reader router

Pick the route closest to your question.

Open full archive
PATH 01

Core theory

I want the framework spine.

Start with the root and background papers, then move into recovery and calibration anchors.

PATH 02

Measurement and records

I care about measurement, clicks, and shared facts.

Follow propagation into event statistics, detector-local commit, durable records, and objectivity criteria.

PATH 03

Empirical skeptic

I want public-data and stress-test surfaces.

Open the declared public witness windows first, then read each boundary as part of the result.

PATH 04

Boundary auditor

I am checking what is not being claimed.

Use the root, source-authority, and witness-window papers to track exclusions before details.

Reader-safe terms

These terms help orientation. They do not widen manuscript claims.

Term Reader-safe meaning Do not read it as
Source-authority lane The manuscript sequence used to keep the website and paper list aligned. A blanket owner-level theorem closure for every paper.
Public support lane A bounded support or witness surface described by its source paper. An unrestricted empirical confirmation claim.
Per-paper guide A web guide page for manuscript-based orientation, structure, status, and future links. A web-only scientific statement.

FAQ

Why not keep the old first-paper guide exactly?

The release plan changed. The richer guide structure is useful, but the page now needs to orient the full parent-and-companion map.

Should videos be on the homepage?

No. The homepage should stay manuscript-first. Videos belong on guide or media pages when they are ready.

Where should research readers start?

Use the research entry or series pages before opening individual paper guides.

What gets added as the release matures?

Additional version notes, companion-paper links, verification-package records, and final media packages.

Release boundary. This guide can become richer over time, but the order stays: manuscript records first, the canonical archive link second, companion/support records third, media/guide embeds fourth.