PhaseOrigin
Audit map

Where to test CHC first.

The archive is broad, but the first review move is narrow: choose one boundary, identify the closest standard comparator, and ask whether CHC wording is same, orientation-only, limited residue, likely redundant, candidate-only, blocked, failed, or retired.

Start with featured cases Choose a reading route Open status ledger Zenodo DOI
Three-step audit

Review one claim boundary at a time.

The map is meant to lower review friction: start narrow, compare against ordinary language first, and only then change the status label.

Open status effects
Step 1

Choose one bounded case.

Pick a detector family, objectivity criterion, interface budget, or public-data window before reading the full archive.

 Step 2

Name the strongest ordinary comparator.

Use the closest standard model, public reference, selection function, or calibration requirement as the default explanation.

 Step 3

Record the status effect.

A useful review produces a bounded status change: no change, narrow wording, downgrade, blocked on data, or retire label.
What moves a case?

Useful criticism changes status, not just opinion.

A helpful review names the case, comparator, evidence source, and the proposed effect: no change, narrower wording, downgrade, blocked route, or retired label.

Open status effects Open review lanes
Upgrade

Show bounded classification value.

A CHC term can move upward only when a named case shows classification or exclusion value beyond the strongest ordinary comparator.

Downgrade

Show a cleaner ordinary account.

If standard detector, objectivity, interface, or public-data language already does the work, CHC wording should narrow, retire, or remain orientation-only.

Block

Name the missing object.

A route stays blocked when the required dataset, calibration map, selection function, covariance, or public rerun artifact is missing.

Status-effect vocabulary. Reviews are recorded as No change, Narrow wording, Downgrade, Blocked on data, Retire label . The action is always a bounded status change, not a general vote for or against CHC.
Reading routes

Start with a technical surface, not with the whole archive.

Pick the route closest to your expertise, then use the status ledger to see what would narrow, block, or retire the claim.

Mathematical spine

What assumptions make the root route well-posed?

CHC-min action, constrained scalar sector, effective stiffness, and branch assumptions.

Current posture: formula anchors for review, not proof of whole-framework validation

Useful contribution: Name the assumption, lemma, or translation step that fails, weakens, or makes the root route well-posed only in a narrower window.
Recovery limits

What exactly is recovered, and at what order or window?

Controlled recovery, ordinary GR/QFT limits, and declared exclusion criteria.

Current posture: ordinary limits remain the default comparator

Useful contribution: Bring the closest ordinary limit, expansion order, or exclusion condition that forces the CHC route to narrow, retire, or state a clearer residue.
Detector records

Does any record layer survive beyond ordinary detector/readout language?

SPAD, SNSPD, CCD, PMT, bubble-chamber, readout, latch, and durable-output rows.

Current posture: orientation-only across completed detector-family rows

Useful contribution: Bring a detector model or public reference that upgrades, retires, or confirms the orientation-only verdict for a named record layer.
Objectivity

Is the CHC certificate redundant, weaker, or stricter than standard objectivity criteria?

SBS, quantum Darwinism, pointer stability, and shared-fact certificate comparisons.

Current posture: likely redundant or equivalent-or-weaker in the named SBS case

Useful contribution: Identify a non-SBS shared-record case, or show that the current CHC certificate collapses fully into standard SBS/objectivity language.
Interface budgets

Can one public calibration artifact close the branch budget?

Externalized, retained, and dissipated channels under a fixed calibration map.

Current posture: candidate-only and blocked without a public fixed calibration artifact

Useful contribution: Provide a public calibration map or show why the branch-budget split is underdetermined, redundant, or not measurable for the named interface.
Public-data gates

Which labels are non-exclusion, partial, failed, blocked, or rerunnable?

DE, CMB, TDC, FRC/CHIME labels and rerun or blocked-artifact status.

Current posture: bounded labels: non-exclusion, partial, proxy, blocked, or failed

Useful contribution: Attack the declared window, baseline, selection function, or downgrade condition before treating any public-data route as support.
Typed sector language

Does the type discipline clarify claims without promoting unlike evidence?

Exact, recovery, compatibility, exclusion, and public-data labels across sectors.

Current posture: claim governance only, not evidence promotion

Useful contribution: Find a label that promotes evidence across unlike sectors, or propose a stricter type name that prevents over-reading.
Choose by expertise

Where a reviewer can help fastest.

CHC does not need general approval. It needs narrow objections, sharper comparators, public reruns, and case-level upgrades or retirements.

Cosmology / public-data readers

FRC/CHIME, DE-VP0, CMB-VP0, TDC-VP2

Start where public labels are already bounded as non-exclusion, diagnostic partial, proxy non-overturn, blocked, or failed stress.
Detector / instrumentation readers

SPAD, SNSPD, CCD, PMT, bubble chamber

Current first-pass rows are orientation-only; the useful outside input is a cleaner collapse, exclusion, or upgrade condition.
Open-systems / foundations readers

SBS, quantum Darwinism, pointer stability

The named SBS case is likely redundant; the sharp question is whether any non-SBS shared-record case survives.
Interface / materials readers

Photoemissive thin-film branch-budget case

The current route is candidate-only until a public calibration map closes externalized, retained, and dissipated channels.
Current safe verdicts

The value is in keeping different outcomes visibly different.

CHC does not need every term to survive. A useful result may be orientation-only, likely redundant, candidate-only, blocked, failed, or public-rerunnable without support.

Open status at a glance
Detector records

orientation-only

SPAD, SNSPD, CCD, PMT, and bubble-chamber rows currently narrow the detector-record route rather than validate it.

Open the status basis
Objectivity

likely redundant

The named SBS-classical-record case currently reads CHC shared-fact wording as equivalent-or-weaker.

Open the status basis
Interface budgets

candidate-only / blocked

The photoemissive thin-film case needs a public fixed calibration map before branch-budget language carries weight.

Open the status basis
FRC / CHIME

public-rerunnable selection-stress failed

The public rerun package improves transparency, but preserves the failed selection-stress label rather than converting it into support.

Open the status basis
Evidence status

Inspectable is not the same as externally validated.

The same verdict can have different evidence status. Public-reference-anchored, public-rerunnable, external-review, and blocked remain deliberately separate.

Open full evidence ladder
maintainer-self-audit

Internally structured comparison by the site maintainer; useful for routing criticism, not external validation.

public-reference-anchored

The comparison can be inspected against public references, while the verdict remains maintainer-scoped.

public-rerunnable

A public artifact can reproduce the declared classification, including a failed or stress label.

external-review

A named outside review input has stated evidence and a status effect in the ledger.

blocked

A required dataset, reference, calibration map, selection function, or artifact is missing.

Concrete gates

Examples worth inspecting.

These cases show how the archive keeps non-exclusion, partial diagnostics, proxy routes, and failed stress results separate.

Concrete audit gates with status labels, evidence posture, safe readings, and reviewer prompts.

DE-VP0

Phase-flat background response compared against ordinary BAO, SN, and CMB-informed envelopes.

bounded non-exclusion public-reference-anchored

Bounded non-exclusion.

Review prompt:Challenge the declared comparison envelope, baseline choice, or whether ordinary background modeling already absorbs the route.

Do not infer:Do not infer dark-energy proof, full background-chain closure, or replacement cosmology.

Inspect case
CMB VP0

Primary width, acoustic-angle, linked-ruler, and later-transfer diagnostic checks.

primary diagnostic partial public-reference-anchored

Primary diagnostic partial.

Review prompt:Challenge whether the width, acoustic-angle, linked-ruler, or transfer diagnostic is already fully handled by ordinary CMB analysis.

Do not infer:Do not infer full CMB likelihood closure, Boltzmann-code replacement, or cosmology validation.

Inspect case
FRC / CHIME

CHIME/FRB injection-selection response surface, efficiency-CV stress, and standalone rerun package.

selection-stress failed public-rerunnable

Public-rerunnable selection-stress failed.

Review prompt:Check whether the released rerun reproduces the failed selection-stress label and what stronger selection-function treatment would change it.

Do not infer:Do not infer CHC support, source-population inference, or full CHIME selection-function closure.

Inspect case
TDC-VP2

Visible mass-profile, kinematic, public-chain, and modeling limits around time-delay lensing.

relaxed proxy non-overturn public-reference-anchored

Relaxed proxy non-overturn.

Review prompt:Challenge the mass-profile, kinematic, and public-chain assumptions before treating the proxy route as a cosmological result.

Do not infer:Do not infer a new H0 number, full time-delay inference, or model-family closure.

Inspect case
Public-data windows

Public rerun can also preserve failure.

Public-data labels are review objects. They do not become support unless the declared window, baseline, and downgrade conditions allow it.

Open full public-data ledger
Window Label Reproducibility Boundary
FRC-CHIME-SELECTION-STRESS selection-stress failed public-rerunnable Retrospective public-data stress only; not a predictive holdout or full CHIME selection-function closure.
DRK1-CHIME-CATALOG2-VOEVENT-HOLD blocked internal Retrospective durable-record reconciliation only; not a predictive holdout, source-count inference, or CHIME selection-function closure.
DE-CMB-SAME-STACK-NONEXCLUSION non-exclusion internal Non-holdout compatibility surface; not a CMB reanalysis and not a DE paper closure.
BH-TDC-CMB-REPRODUCIBILITY-LEDGER diagnostic partial internal Reproducibility ledger only; not LVK/EHT replacement, TDCOSMO full-likelihood closure, CMB likelihood or Boltzmann reanalysis, or parent-paper theorem closure.
QAC-OBS-PROXY diagnostic partial partial Proxy diagnostic only; no TNG same-instance holdout and no finite-window certificate closure.
CBL-PUBLIC-PILOT-SAME-INSTANCE-OPEN diagnostic partial internal Public-pilot diagnostic only; not same-instance branch tomography or parent-paper closure.
LBD-REINTEGRATION-CANDIDATE diagnostic partial partial Reintegration-candidate status only; not restoration to an active series member.
Count boundary. The audit-entry count above is a representative boundary-audit surface, not a complete count of all CHC claims or an external-validation score.