Question
Which claim is under review?
Name the exact page and boundary before evaluating evidence. Avoid reviewing a stronger claim than the source permits.
Reviewer packet / human review pending
Use this route as an inspection order, not as a claim summary. It starts with what is not claimed, then routes you to current state, burden evidence, ontology documents, and source authority.

Packet status
The packet exists because prerequisite authority and orientation pages now exist. It does not report review completion or scientific approval.
Claim boundaries first
The current-state snapshot is useful only when read with its forbidden implications. The boundary below appears before source inspection so the review target cannot silently expand.
Inspection order
Internal pages explain the reader job and boundaries. Source links and manifests remain available as provenance once the review question is precise.
01
Start with the rule that upstream source files, registries, and governed records own claim status.
Open route02
Inspect allowed, forbidden, and gate-required wording before reading any stronger summary.
Open route03
Read the active task, latest handoff, blocked claims, and next source-side action.
Open route04
Review derivation burdens and blockers without treating them as a progress score.
Open route05
Use the reading guide for registered TeX sources and generated PDF derivatives.
Open route06
Choose the physicist, mathematician, AI/agent, or system-engineering path matching your review question.
Open routeDeeper inspection
These pages help separate benchmark status, derivation roadmap, source extension, frozen routes, validation limits, and publication evidence.
01
Separate exact-GR benchmark compatibility from first-principles derivation and benchmark promotion.
Open route02
Inspect source, metric, matter-coupling, equation, and promotion burdens as separate obligations.
Open route03
Read proposal-only and draft/control work without treating it as adopted source law.
Open route04
Distinguish scoped obstruction and frozen local routes from global theory rejection.
Open route05
Check why command PASS is bounded checked-state evidence, not theorem proof.
Open route06
Inspect route maps, page provenance, source manifests, asset manifests, and hash limits.
Open routeReviewer questions
Question
Name the exact page and boundary before evaluating evidence. Avoid reviewing a stronger claim than the source permits.
Question
Find the registry, handoff, TeX source, or source-analysis artifact before relying on a website summary.
Question
Identify whether the issue is source-law adoption, MetricData(E), g_eff, matter coupling, Einstein equations, or benchmark promotion.
Question
Look for the next bounded packet, acceptance criteria, obstruction, freeze, or human gate named by the source-state page.
Safe reading