First Orientation — FAQ

A non-specialist should begin with orientation rather than claims. Discover explains the site structure and routes readers into the construction body, consequence surfaces, and inspection routes. The safest reading order is orientation first, obligations second, construction third, results fourth, verification always.

The site is organized as a research observatory. Discover orients; Program states identity and scope; Agenda defines obligations; Corpus carries construction; Results reports consequence surfaces; Verify exposes inspection, bridge, and falsification routes; Publications holds citable artifacts; Impact maps conditional relevance.

The Corpus is where the theory is built rather than merely announced. It is not identical to the books, the Registry, or TauLib; those are projections of the Corpus. A reviewer asks there what was constructed, in what order, from what earlier obligations, and with which dependency anchors.

Results show what the framework currently says follows across mathematics, physics, life, and metaphysics. They must be read with status markers: internal stance, verification route, and external-acceptance boundary are separate. A result can be internally addressed without being externally accepted.

The homepage intentionally surfaces striking claims early, but it also tells readers these claims are not equivalent in status. First orientation should identify high-signal claims and then route them into Results and Verify rather than accepting them from the homepage alone.

The master constant is one of the first red-team questions. The physics surface depends on whether ι_τ is genuinely forced by the kernel/scalar-readout construction or effectively fitted. The site routes this through a research paper, Corpus H3 page, Step 2, Registry anchors, and TauLib evidence.

The first question is not whether downstream numbers are impressive. It is whether ι_τ is fixed before physical calibration enters. If the derivation fails, the downstream zero-parameter physics claim weakens substantially.

Claims are routed through construction steps, hinge pages, Registry entries, TauLib modules, and Verify surfaces. If a hinge fails, the relevant downstream claims need to be relabeled, weakened, repaired, or withdrawn according to dependency.

TauLib is the Lean formalization projection. If a theorem is encoded and compiles, Lean checks that theorem relative to the formal environment, trusted computing base, and disclosed assumptions. Bridge claims and empirical interpretations remain separate burdens.

Formal checking can certify encoded formal claims; prediction surfaces can expose commitments; falsification packs can identify failure paths. None of those alone establishes that a mathematical construction describes the physical world or that a public-good application is ready.

Failure is not one thing. Mathematical hinges can fail; formal builds can fail; bridge claims can fail; empirical predictions can fail; public-good translations can fail. The site should route each kind of failure to the right inspection surface.

A practical route is: Discover for structure; Verify for inspection boundaries; Master Constant for physics skepticism; Results for consequence surfaces; Corpus/Construction Spine for construction burden; Journalist FAQ for responsible coverage. Do not start by reading all seven monographs.