Public trust boundary

Source Authority

The website is a reader-facing presentation layer. It can explain, organize, and link reviewed material, but upstream source files and registries decide scientific, mathematical, governance, and workflow state.

Read the boundary Back to overview

Visual orientation only: readable pages are useful maps, not the authority that defines project state.

Authority ladder

Start with the source lane that owns the claim.

The public trust rule is simple: use website and generated surfaces to find the right source, then inspect the registered source file and registry row before treating a claim as current.

Canonical science

Registered TeX

Physics and derivational claims belong to registered scientific sources and their stated claim status.

Control state

Registries

CSV registries carry routing, provenance, source-object hashes, generated-output tracking, and memory metadata.

Guidance

Registered Markdown

README files, AGENTS instructions, publication briefs, source specs, role contracts, skills, and design notes guide public and operator work.

Derivatives

Generated surfaces

Website pages, GitHub-facing Markdown, HTML explainers, PDFs, wiki notes, semantic extracts, and local caches orient readers but do not override sources.

Reader rules

Clear public material still has limited authority.

A page can be well designed, accurate as a summary, and useful to a reader while still remaining downstream from the source record it describes.

Website pages

Explain and organize

A website page can make the project readable, connect real routes, and state claim status. It cannot create a physics result or change workflow authority.

Generated explainers

Use as maps

Generated public material is useful for orientation after its source binding is known. If it conflicts with a registered source, the source wins.

Validator passes

Treat as bounded evidence

A validator pass means a deterministic check accepted the checked state. It is not a scientific verdict or role-authority grant.

Memory and cache

Search, then inspect

Memory, wiki, semantic extracts, Obsidian mirrors, and local caches help find sources. They are retrieval aids, not citation authority.

Reading path

Move between public pages without losing the source boundary.

These links are real current routes or upstream source surfaces. No generated page, including this one, replaces the source material it points toward.

Project overviewReturn to the public two-track overview.Physics ResearchRead the physics track with the open GR-derivation boundary preserved.AI Research-Agent SystemRead the AI workflow track without treating workflow evidence as physics proof.ResourcesInspect current website resource indexes and scaffold/sample labels.

Upstream source repositoryCanonical source files, registries, and control records remain upstream.Source authority explainerReviewed generated noncanonical guide to source authority and derivatives.Publication brief registryRegistry surface for reviewed public explainer pages and source-material bindings.

Claim status

This page is an orientation surface.

It cannot change the hierarchy, replace a registry, promote ontology, certify a benchmark, issue a Gate Chair verdict, expand roles, modify routing behavior, or make generated outputs authoritative.