PhaseOrigin
Critical review

Do not start by accepting the full CHC program.

This page is for skeptical readers, reviewers, and technical critics. The intended first test is not whether the full CHC program is true. Choose one bounded claim family, compare it against the relevant standard tools, and decide whether it survives as more than retrospective reinterpretation.

Choose a review route One-page overview Review status Open public review issues Open CHC archive Zenodo DOI Reader guide
Review boundary. A useful criticism may reject, narrow, correct, or reclassify a CHC claim. Agreement with the full framework is neither expected nor requested.
Active review surface. The active review surface covers all 70 manuscript entries: 45 parent papers and 25 companion verification, support, public-stress, or validation-surface manuscripts. Companion manuscripts are independently reviewable, but their evidentiary weight is evaluated through the parent-paper claim, public-data window, or support lane they serve. Adding companion manuscripts to the active review surface does not upgrade validation, residue strength, external review status, or parent-paper closure.
Review routes

Start with one bounded claim family.

Each route states what standard tools remain in force, what CHC claims to add, and what would count as failure.

ROUTE 01

Detector records

When does a threshold crossing become a recorded event?

Claim family
Detector-local event closure and durable record formation.
Standard tools retained
Propagation, detector physics, thermodynamic switching models, and ordinary readout models remain in scope.
What CHC adds
A typed separation between threshold crossing, detector-local commit, latching, durable output, and record-counting status.
Failure condition
The route fails or retires for a detector family if ordinary detector/readout/DAQ language accounts for the local event, durable record, and count-status structure at the stated resolution with no residual exclusion value.
70-entry scope
Primary parent-paper route over Papers 05-07 and 10 inside the 70-entry review surface.
Companion intake
No companion manuscript currently carries an independent detector-record upgrade. Any companion objection that changes detector-record wording should be evaluated through the relevant parent-paper record claim and the detector comparison artifact.
Smallest reproduction entry
Start by comparing Papers 05-07 and 10 against a named detector family where threshold, commit, latch, durable output, and record counting are already explicit.

Useful criticism

  • Known detector models where threshold crossing, latching, and durable record status cannot be separated.
  • References that already formulate the same distinction more cleanly.
  • Cases where the CHC terminology adds no constraint beyond standard detector or decoherence language.
05 CHC-OPL Operational Phase-Link and Local Commit Grammar for Detector-Local Opening and Thresholds in the CHC Framework 06 CHC-DBC Dynamic Boundary Insertion, Detector Memory, and Pre-Latch Trigger Sinks in Wave--Detector Systems 07 CHC-DTM Detector Thermodynamics, Metastable Amplification, and Irreversible Readout 10 CHC-RSF A Durable-Record Certificate Ladder from Detector Semantics to Shared-Fact Conditions
Detector route Failure condition, standard tools, and public criticism route. Current risk Latest collapse risk and desired outside input. External review request Concrete prompt for detector/instrumentation readers to test the orientation-only verdict.
Open this public review issue
ROUTE 02

Classical objectivity

When is decoherence not enough for a shared fact?

Claim family
Redundant-record objectivity and shared-fact certification.
Standard tools retained
Open-system dynamics, decoherence, pointer-state analysis, and fragment-access models remain in scope.
What CHC adds
A certificate layer separating decohered states from publicly recoverable, consensus-bearing records.
Failure condition
The route fails or retires for a case if ordinary decoherence, quantum Darwinism, spectrum broadcast structure, pointer-stability, or fragment-access language accounts for the shared-fact structure at the stated resolution.
70-entry scope
Primary parent-paper route over Papers 08-10 inside the 70-entry review surface.
Companion intake
Companion objections are admissible when they affect the record/objectivity chain, but they should be routed through the parent-paper certificate claim rather than treated as separate validation.
Smallest reproduction entry
Start by mapping Papers 08-10 onto one established objectivity criterion such as quantum Darwinism, spectrum broadcast structure, pointer stability, or fragment-access consensus.

Useful criticism

  • Examples where the proposed record certificate is weaker than established objectivity criteria.
  • Missing references in quantum Darwinism, spectrum broadcast structure, pointer-state, or open-system literature.
  • Cases where the shared-fact ladder overstates what the underlying physics can certify.
08 CHC-RIF A Fail-Closed Plateau Protocol for Residual Irreversibility Floors in Interference and Echo Observables 09 CHC-OBJ Classical Objectivity from Redundant Records: Fragment Inference and Certificate Ladders 10 CHC-RSF A Durable-Record Certificate Ladder from Detector Semantics to Shared-Fact Conditions
Objectivity route Comparison target for decoherence, redundancy, and shared-fact criteria. Current risk Latest duplicate-criteria risk and desired outside input. Objectivity comparison table Current QD/SBS/pointer/fragment-access comparison verdicts and next tests.
Open this public review issue
ROUTE 03

Interfacial branch budgets

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

Claim family
Interfacial branch budgets for absorbed excitation and material response.
Standard tools retained
Maxwell/QED calculations, material response, transport, dissipation, and detector microphysics remain in scope.
What CHC adds
A record-facing budget grammar for externalized outcome, retained/internal ledger, and dissipative sink branches.
Failure condition
The route fails, blocks, or retires for a case if ordinary optics, transport, material-response, or detector-interface language accounts for the interface budget at the stated resolution, or if the channels cannot be measured on one calibration map.
70-entry scope
Parent Paper 29 plus its CBL companion entries within the 70-entry review surface.
Companion intake
CBL-VP0 and CBL-VP1 are reviewable as bounded public-pilot/support companions for Paper 29. They can narrow, block, or retire interface-budget wording, but they do not validate the parent branch-budget claim by themselves.
Smallest reproduction entry
Start with Paper 29 and a concrete material-interface example where externalized, retained, and dissipated channels can be measured or shown not to be conserved.

Useful criticism

  • Material-interface cases where the proposed branch labels are not conserved or measurable.
  • Established optical, detector, or transport formulations that make the CHC branch grammar redundant.
  • Evidence that the proposed branch-budget language overstates what a public dataset can support.
29 CHC-CBL Interfacial Commit Branching Laws and Conditional Branch-Budget Estimation for Electromagnetic Carrier Conversion 29-1 CHC-CBL-VP0 Public Branch-Law Pilot Gates for CHC-CBL 29-2 CHC-CBL-VP1 Same-Window Public Optical Branch-Budget Gate in IGDB for CHC-CBL
Interface route Budget-language failure condition and criticism route. Current risk Latest measurable-budget risk and desired outside input. Interface budget case Candidate calibration-map requirements and public-artifact status.
Open this public review issue
ROUTE 04

Public-data stress windows

Can bounded CHC constraints survive public-data checks?

Claim family
Public-data witness windows, exclusions, reproductions, and holdout-style stress tests.
Standard tools retained
Public catalogs, standard statistics, astrophysical/cosmological baselines, and reproducibility checks remain in scope.
What CHC adds
A claim-boundary discipline for separating support, stress, non-exclusion, block, and failure labels.
Failure condition
The route fails, blocks, or retires for a window if ordinary statistical, astrophysical, or public-data language accounts for the result at the stated resolution, or if the window requires post-hoc retuning, overstates support, or fails to produce bounded exclusions.
70-entry scope
Parent public-data routes plus all VP/KP validation, support, public-stress, and public-source companion entries inside the 70-entry review surface.
Companion intake
Each companion entry is reviewable on its own source basis, reproducibility boundary, label, and downgrade condition. Its evidentiary weight is still local to the parent claim or declared public-data window it supports.
Smallest reproduction entry
Start with one declared public-data window and ask whether the label survives a stronger baseline, selection-function check, and holdout or pre-registration discipline.

Useful criticism

  • Cases where a public-data result is better labeled as null, unresolved, or ordinary model compatibility.
  • Statistical or selection-function objections to any stated support, stress, or holdout label.
  • Datasets or baselines that should be used before a result is treated as more than a retrospective interpretation.
02 CHC-DE Homogeneous Phase-Flatness and Dark-Energy-Like Background Response in the Covariant Expansion-Phase Framework 02-1 CHC-DE-VP0 CHC-DE-VP0: Public BAO-SN-CMB Background-Stress Witness for the Homogeneous Phase-Flatness Branch 19 CHC-QTT Barrier-Mediated Phase-Link Transmission and Tunneling Spectroscopy in the CHC Framework 19-1 CHC-QTT-VP0 Public Computational and Analytic Benchmark Gates for CHC-QTT Support-Registration Factorization 19-2 CHC-QTT-VP1 Public Literature Support-Action Gates for CHC-QTT 19-3 CHC-QTT-VP2 QTT-VP2: Figure-Derived Same-Fabrication-Family Partial Gates for MIM/FN Tunneling Windows 21 CHC-CCL Task-Fixed pi Readout within a Declared Solar-System Calibration Window 22 CHC-PTM Conditional Planck-Triad Readouts and a Mass-Modulus Branch Ledger in the CHC Framework 22-1 CHC-PTM-VP0 Metrology-Reference Checks for CCL/PTM Declared-Class Readouts in CHC 23 CHC-FRC Fast-Radio-Burst Source Counts and Log-Shell Event-Rate Inference in a Near-Euclidean Window 23-1 CHC-FRC-VP0 CHC-FRC-VP0: Official CHIME/FRB Catalog 1 Selection-Stress Gates 23-2 CHC-FRC-VP1 CHC-FRC-VP1: Official CHIME/FRB Exposure-Injection Selection-Stress Gates 23-3 CHC-FRC-VP2 FRC-VP2: CHIME Catalog 1 Injection-Selection Surface Gates in CHC 23-4 CHC-FRC-KP1 FRC-KP1: A Catalog1-Frozen CHIME/FRB Catalog2 Public Holdout Prediction Test for CHC-FRC 24 CHC-TDC Strong-Lens Time-Delay Cosmography in the CHC Framework: Fermat Potentials, Distance Factors, and Inference Control 24-1 CHC-TDC-VP1 CHC-TDC-VP1: Public-Posterior Residual Gates for Time-Delay Cosmography 24-2 CHC-TDC-VP2 TDCOSMO-IV Public-Chain Mass-Profile Stress Gates in CHC Time-Delay Cosmography 26 CHC-BH2 JT-Bath Evaporation, Schwarzian Memory, and Non-Markovian Return Kernels 26-1 CHC-BH-VP0 CHC-BH-VP0 Compact-Object Diagnostic Gates: Public EHT Morphology/Polarization Surfaces and GWOSC Remnant/Response Surfaces 26-2 CHC-BH-VP1 BH-VP1: GWTC-3 Tests-of-GR Posterior Diagnostic Gates in CHC 26-3 CHC-BH-VP2 CHC-BH-VP2 Surface-Commit Return Suppression: A Bounded Public Literature-Summary Support Audit of Black-Hole Candidates and Neutron-Star X-ray Transients 27 CHC-CMB Primary-Sector Width and Linked-Ruler Constraints in a Restricted Phase-Field Description of the Cosmic Microwave Background 27-1 CHC-CMB-VP0 CMB-VP0: Primary-Sector Linked-Ruler Public Gates in CHC 28 CHC-QAC Quasi-local Angular-Momentum Compensation Grammar on Declared Cosmological Domains in the CHC Framework 28-1 CHC-QAC-VP0 Public Simulation-Observation Proxy Bridge Gates in CHC 28-2 CHC-QAC-VP1 Public-Data Expansion and Covariance-Prep Proxy Gates in CHC 28-3 CHC-QAC-VP2 Public Environment/Covariance Bridge-Partial Gates in CHC 28-4 CHC-QAC-VP3 GEMA Observational-Environment Covariance Gates in CHC 28-5 CHC-QAC-VP4 Dual Environment Harmonization and Covariance-Partial Gates in CHC 28-6 CHC-QAC-VP5 Mock-IFU Observable-Family Bridge Gates in CHC 28-7 CHC-QAC-VP6 Mass-Weighted Observable-Family Bridge Gates in CHC 29 CHC-CBL Interfacial Commit Branching Laws and Conditional Branch-Budget Estimation for Electromagnetic Carrier Conversion 29-1 CHC-CBL-VP0 Public Branch-Law Pilot Gates for CHC-CBL 29-2 CHC-CBL-VP1 Same-Window Public Optical Branch-Budget Gate in IGDB for CHC-CBL 35 CHC-PFW Collider, Precision-Electroweak, and Leptonic-Flavor Fit Windows on a Declared CHC Gauge--Chiral Family 35-1 CHC-PFW-VP1 CHC-PFW Public Scalar, Covariance, Contour, and ROOT Support Gates for Precision-Observable Windows
Public-data route Stress-window failure condition and criticism route. Current risk Latest selection-function and retrospective-compatibility risk.
Open this public review issue
Status handoff

From route to current status.

Use this page to choose a bounded review route. Use the review-status page to see which objections, downgrades, missing references, failed gates, and next checks would most naturally move the public record.

Open review status Inspect public issues
No goalpost motion

The manuscripts stay authoritative.

The status page does not upgrade claim strength. It only makes uncertainty, criticism pressure, and correction paths visible around the fixed archive.

The repository policy for ledger changes is maintained in docs/review-ledger-policy.md. Public pages summarize the rule; the fixed archive remains the scientific authority.

How to write a useful issue

  1. Name one bounded claim family rather than commenting on the full framework at once.
  2. State the standard theory, method, dataset, or reference that should control the comparison.
  3. Identify whether the concern is a missing reference, false distinction, mathematical gap, overclaim, reproducibility issue, or empirical-selection problem.
  4. Quote the relevant paper, guide passage, equation, or status label when possible.
  5. State the proposed status effect: no change, narrow wording, downgrade, blocked on data, or retire label.
Submit or inspect criticism Open review repository

What this page is not

  • Not a peer-review claim.
  • Not a request for endorsement of the full framework.
  • Not a product or implementation disclosure.
  • Not a substitute for the manuscripts or Zenodo archive.
  • Not a guarantee that submitted criticism or proposals will be accepted.
Archive authority. The manuscripts and DOI archive remain authoritative for definitions, assumptions, equations, status labels, and exclusions. This page is only a review router.

Last updated: 2026.05.25