Inspect & Verify

Core Idea

Inspect & Verify is for readers who want to test the work structurally. The route begins with a visible claim, traces it into the corpus, and checks the relevant verification surface.

The program should not be evaluated only at the level of prose. Serious inspection follows identifiers, dependency structure, formalization status, empirical exposure, and stated scope.

Inspection Paths

Start from Results

Choose a result, read its status, then inspect related corpus and verification references.

Trace to Corpus

Use registry identifiers, object types, aliases, and book provenance to locate the source object.

Check Verify

Use scientific rigor, verification framework, domain verification, and operational surfaces.

Inspect TauLib

Open the formalization surface and trace machine-checked parts back to public claims.

Practical Workflow

Pick a claim in Browse All Results.
Note its type, status, domain, and related links.
Follow registry, Monograph Corpus, or artifact references into Corpus and Publications.
Use Verify to select the relevant verification mode: formal, empirical, comparative, or protocol-based.
If the claim is formalized, inspect TauLib. If it is empirical, inspect Predictions & Falsification.

What Good Inspection Produces

Good inspection names a specific object and a specific test. Examples include a broken dependency, a missing assumption, an unearned Core Semantics term, a missing semantic bridge, a mismatch between prose and registry source, a formalization gap, a prediction that should be reclassified, or a prior-art overlap that needs explicit treatment.

For structured public objections, continue to Public Discussions or Critique & Challenge. Use Issues for concrete defects and Contact for private or institutional routes.

If inspection finds a concern

Use GitHub Discussions if the concern needs interpretation, review, or discussion.

Use GitHub Issues if the concern is concrete and actionable: broken link, wrong metadata, missing source, bad status label, or reproducible build problem.

For formalization concerns, use the TauLib / Formalization discussion category or the relevant repository issue tracker.

Discuss an inspection concern Report a concrete issue