Documents / Reading Paths

Reading Paths

Choose the path closest to your question or discipline. Each path begins with an internal explanation, preserves the strongest inference it does not authorize, and leads to source inspection only when needed.

Choose a specialist path General-public path Documents overview

Diagram showing one reading-path hub routing physicists, mathematicians, AI and agent researchers, software and system engineers, and external reviewers to internal prerequisite pages while preserving the no-new-claims boundary. — The diagram illustrates audience reading paths connecting each discipline to internal routes and source-authority context.

How to use this index

Read by question, then inspect source authority.

These paths are navigation layers. They lower the cost of finding the relevant pages without replacing the records that own claim status.

Route type: Canonical reading-path indexOne Documents route organizes the general-public path and anchored specialist paths through existing pages.
Audience: General readers, specialists, and reviewersChoose the path that matches your question, then move from internal explanation to source inspection.
Boundary: No new claimsReading order does not update source state, promote a result, or replace the records that own a claim.
Reader rule: Internal route before provenanceUse the page that explains the question first; inspect source and manifest evidence when an audit is needed.

Audience paths

Pick the route family that matches your review question.

Every path follows one rule: read canonical internal pages first, then use source links and manifests as provenance when auditing a claim or artifact.

Physicists

Start with current status, then inspect the derivation boundary.

This path is for readers asking what the physics program currently claims, where the open GR burden sits, and which stronger claims remain blocked.

01

Current physics state

Read active task, latest handoff, open burden, blocked claims, and next action.

02

Distance-to-GR dashboard

Inspect derivation burdens as ledger-backed blockers, not as a progress score.

03

Ontology

Read vocabulary and ontology status before treating terms as derived physics.

04

Exact-GR benchmark

Separate benchmark compatibility from first-principles derivation.

05

Claim gates

Check proposal, audit, obstruction, freeze, and gate boundaries.

Do not infer: Boundary for this pathDo not infer completed first-principles GR derivation, `g_eff`, matter coupling, Einstein equations, benchmark promotion, or downstream GR promotion.

Mathematicians

Follow definitions, construction burdens, and obstruction scope.

This path is for readers checking formal objects, route constraints, finite examples, no-target-import discipline, and local negative results.

01

Ontology

Start with definitions and status boundaries before reading technical routes.

02

GR derivation roadmap

Inspect open source, metric, matter-coupling, equation, and promotion burdens.

03

Metric response ladder

Read why response tokens remain below metric data and `g_eff` construction.

04

No-target-import discipline

Check the fail-closed boundary around target topology, atlas, metric, and benchmark imports.

05

Negative results and frozen routes

Read local obstruction scope without converting it into global rejection.

Do not infer: Boundary for this pathDo not infer existence, uniqueness, regularity, or global impossibility from a reading path, diagram, local freeze, or finite toy result.

AI and agent researchers

Read workflow authority before evaluating agent behavior.

This path is for readers studying bounded AgentJobs, role records, parent-child synthesis, memory retrieval, validators, and completion evidence.

01

AI Research-Agent System

Start with the track landing for workflow scope and authority boundaries.

02

Workflow walkthrough

Read the bounded request, Director, AgentJob, validation, completion, and handoff sequence.

03

One bounded AgentJob

Inspect the single-job envelope for reads, writes, validators, outputs, and stop conditions.

04

Role authority inspector

Check why role authority requires current task-local records.

05

Memory registries

Read source-first retrieval discipline and generated-memory limits.

Do not infer: Boundary for this pathDo not infer that AI workflow owns physics decisions, validator PASS is proof, or role labels grant authority without task-local records.

Software and system engineers

Inspect operation, validation, publication, and tool boundaries.

This path is for readers reviewing system operation, maintainer workflows, validation evidence, project-system repair, and publication provenance.

01

Operations

Start with the operational landing for lifecycle, routing, validation, publication, repair, and tools.

02

Validator PASS limits

Read why command PASS is checked-state evidence, not theorem proof or role authority.

03

Publication process

Inspect brief, source spec, public page, screenshots, human review, and manifest discipline.

04

Governance and control

Check publication, provenance, registry, retrieval, and source-authority boundaries together.

05

Technical requirements

Read tool tiers without confusing capability with authorization.

Do not infer: Boundary for this pathDo not infer that tool availability is authorization, build success is scientific truth, or manifest presence replaces source review.

External reviewers

Establish claim and source boundaries before direct inspection.

This path prepares a reviewer to inspect source status, current burdens, and authority boundaries before opening research artifacts.

01

General-public reading path

Begin with the public first path if the project framing is unfamiliar.

02

Current physics state

Read the active source-state snapshot before inspecting deeper claims.

03

Distance-to-GR dashboard

Inspect open derivation burdens and blocked downstream promotions.

04

Source authority

Read the trust boundary for website pages, generated derivatives, and upstream records.

05

Research articles

Use the collection guide for registered TeX sources and corresponding PDF manifestations.

Do not infer: Boundary for this pathDo not infer that this path is a review verdict, a review invitation, or evidence that the scientific claims are complete.