Verify Verification Surface Canonical The standards by which the program holds itself accountable as a serious, inspectable research program.
Verification SurfaceCanonical

Scientific Rigor

The standards by which the program holds itself accountable as a serious, inspectable research program.

Typed claims
Mathematical, physical, life, and metaphysical claims are not granted the same epistemic status.
Public burden
Claims remain inspectable through the corpus, release manifest, formalization surfaces, and falsification routes.
No shortcut
Formal verification supports internal coherence; empirical and interpretive claims still require external scrutiny.
In plain language

Most research programs ask you to take their claims at face value. This one asks the opposite — every claim is typed by what kind of thing it is (mathematical theorem, physical prediction, biological correlate, metaphysical commitment), and each type is held to the standard appropriate to it. A formal theorem must expose its formalization status. A physical prediction must expose its measurement bridge and possible failure condition. A biological claim must state its observable, comparative, or structural support. A metaphysical claim must state its ontic, structural, phenomenological, or commitment-level status. The page below names those standards and the routes by which an outside reviewer can check that the program is actually following them.

Core Question

Before asking whether a specific result is true, a reviewer can ask whether the program operates in a way that qualifies as serious, inspectable research. This page verifies the research form, not the truth of the framework.

Rigor Criteria

  • Explicit scope: the site distinguishes formal, empirical, bridge, and interpretive burdens.
  • Explicit burden of proof: each result should make clear what would have to be checked.
  • Public inspectability: release surfaces, registry pages, TauLib, and assessment routes are exposed.
  • Structured artifacts: books, corpus objects, generated docs, manifests, and pages are versioned.
  • Stable release surfaces: snapshots and manifests make drift visible.
  • Openness to scrutiny: the site names how to challenge the work rather than asking for deference.
  • Explicit refusals and constraints: the Program lane names what the research program refuses to do.
  • Failure modes: predictions, falsification paths, contradicted statuses, and open bridge issues stay visible.

The Five Checks

Agenda accountability

Core Semantics, Structural Challenge Ledger, Kernel/Model/Reality, and Construction Roadmap name the obligations before results are defended.

Corpus traceability

Definitions, theorems, lemmas, and result claims are tied back to registry objects and dependency chains.

Construction-step verification

The ten-step Construction Spine exposes which layer is being checked, what counts as a bridge, and where failure would surface.

Formal / bridge / empirical verification

TauLib checks formal proof obligations where formalized; bridge and empirical claims require their own Verify surfaces.

Structured assessment

Reviewers can enter through domain-specific inspection routes, assessment protocols, and bounded review workflows.

Methodological lineage

The five-check inspection model above is not presented as a from-scratch invention. It continues several older traditions in the philosophy of science and the philosophy of formal verification: Popper’s falsifiability criterion (results must expose what would refute them), Lakatos’s distinction between progressive and degenerating research programmes (a programme earns standing through what it predicts and is willing to be checked against, not through internal elegance alone), Feferman’s predicativism and unfolding programme (foundational claims should expose the resources they actually require), and the formal-verification-philosophy strand (de Bruijn, Harper, Bundy) that treats inspectability and machine-checkability as part of what it means to make a serious mathematical claim. The program treats inspection-readiness as a continuation of these lineages, not a replacement for them; it has not yet written a sustained engagement with any one of them, and the obligation to do so is acknowledged rather than discharged.

Reader Stance

The intended reader stance is neither deference nor dismissal. It is inspection. Follow the chain from publication prose to corpus object, from corpus object to formalization where available, and from formalization to the remaining bridge assumptions.

Save or share this page for inspection

Download a portable dossier, copy a reviewer note, or send this page to someone who can inspect it.

Email to expert