Topology
Repository Map
Use folder classes and edit/read policy before choosing source bundles.
Open routeDocuments / Governance / Site Builder Guide
Site Builder Guide
Every page family starts from a source bundle: primary authority sources first, derivative seeds second, forbidden inferences always visible.
The safe build order is deliberate: identify the page family, inspect primary sources, map derivative seeds, write forbidden inferences, record freshness, then implement inside live control. A source bundle is a guardrail, not a shortcut around source reading.
This is a secondary maintainer route within Documents / Governance & Control, not a primary Documents dropdown destination. Internal routes carry the reader journey; GitHub is retained as provenance for exact implementation inspection.
Static diagram
Build pages from source bundles through provenance.
The publication-provenance diagram shows the source-bundle-first workflow: inspect source, build the route, update manifests, validate, and hand off without strengthening claims.
Source-bundle schema
Every planned page needs the same minimum evidence shape.
The schema keeps primary authority sources ahead of generated seed material and makes blocked inferences visible before implementation.
| Field | Purpose | Required boundary |
|---|---|---|
| Page family | Names the public route family or page type. | The family does not grant write permission by itself. |
| Reader job | States what the page helps a reader understand or decide. | Reader convenience cannot strengthen the source claim. |
| Primary authority sources | Lists the first files, registries, or governed records to inspect. | Primary sources outrank derivative seed material. |
| Supporting sources | Names context files, registries, handoffs, PRDs, or manifests that constrain copy. | Support does not override the primary owner. |
| Derivative seed material | Identifies generated Markdown, HTML, PDFs, wiki notes, or screenshots that can speed drafting. | Seed material is reusable only after source inspection. |
| Freshness policy | Defines inspection date, stale-data behavior, and refresh trigger for current-state material. | A stale snapshot must warn or block depending on route severity. |
| Forbidden inferences | Lists claims the page must not imply. | No public route may silently promote blocked or open claims. |
| Handoff requirements | Names inspected sources, validators, screenshots, skipped checks, and review status. | A handoff is evidence of implementation discipline, not claim proof. |
Bundle index
Page families map to source bundles before they map to designs.
This compact index is a starting map. Future packets still need live source inspection before making public route changes.
| Page family | Primary authority sources | Derivative seeds | Required PRDs |
|---|---|---|---|
| Documents architecture | Current implementation_control packet for write authority; the accepted Documents canonical plan for architecture; live route, catalog, and manifest files for implementation evidence. | Reviewed legacy Resources pages and completed Documents routes after direct comparison. | Documents navigation implementation plan and packet-scoped acceptance criteria. |
| Project overview | README.md, AGENTS.md, research_control/README.md, publication process notes. | Project overview GitHub-facing and HTML explainers. | PRD-01, PRD-05, PRD-06, PRD-10. |
| Physics pages | ontology/aether-and-aether-flow.md, ontology/tex/*.tex, TEX and claim registries. | Physics explainers, tracked HTML, briefs, and source specs. | PRD-02, PRD-05, PRD-09, PRD-10. |
| AI research-agent pages | research_control/README.md, .agents/ roles and schemas, .codex/ skills, task and registry sources. | Workflow, lifecycle, role, parent-child, and roles/skills explainers. | PRD-03, PRD-04, PRD-05, PRD-07. |
| Source-authority pages | AGENTS.md, registries/, FOLDER_MAP.md as generated orientation, source and derivative registries. | Source-authority, memory-system, and repository-topology explainers. | PRD-05, PRD-06, PRD-08. |
| Current-frontier pages | research_control/current_frontier.md, program state, latest handoff, Distance-to-GR ledger. | Dated current-state cards and reviewed derivatives after source check. | PRD-09, PRD-05, PRD-10. |
| Operator and contributor pages | README.md, Makefile, requirements, scripts/, tests/, .codex/skills/. | Technical requirements, validator workflow, project-system improvement explainers. | PRD-07, PRD-03, PRD-04, PRD-05. |
| Website publication pages | markdown/publication-briefs/, markdown/html-explainer-specs/, publication brief registry. | GitHub-facing, HTML, and publication QA evidence. | PRD-06, PRD-05, PRD-08, PRD-11. |
Build-first checklist
Source inspection happens before derivative reuse.
The checklist blocks a common failure mode: a generated explainer becomes the public claim owner because it was easier to read.
| Step | Action | Stop condition |
|---|---|---|
| Identify page family | Choose the source bundle before writing copy or page code. | Do not start from search results or a generated explainer alone. |
| Inspect primary sources | Read the source files, registries, handoffs, or control records that own the claim. | Do not let derivative seed material decide claim status. |
| Write the boundary | State source class, freshness, forbidden inferences, and validation expectations. | Do not hide uncertainty behind polished page structure. |
| Use derivative seeds carefully | Reuse generated Markdown, HTML, wiki, PDFs, or screenshots only as drafting support. | Do not cite derivative material as canonical authority. |
| Record the handoff | Name inspected sources, PRDs, validators, screenshots, skipped checks, and review status. | Do not push, deploy, mutate assets, or change manifests without live authorization. |
Contributor handoff
The handoff records what was inspected and what remains uncertain.
A useful handoff gives the next reviewer enough evidence to reproduce the route boundary without reconstructing the repository from memory.
| Item | Reason | Risk if missing |
|---|---|---|
| Source paths | Reviewers need to verify what was inspected. | The route looks source-backed but cannot be audited. |
| Inspection date | Current-frontier and topology material can drift. | A stale source map reads as current fact. |
| Relevant PRDs | Requirements planning constrains page structure and forbidden claims. | A page satisfies layout while violating the product boundary. |
| Claim boundary | The route must state what it can and cannot imply. | Publication polish silently promotes the claim. |
| Validation evidence | Validators, screenshots, and skipped checks show process conformance. | The packet cannot distinguish implementation quality from authority. |