Pre-Launch Checklist
This checklist should be completed before the LMR site is made public.
It is a practical review tool. It does not define theory.
Core Rule
Do not launch the site until the public structure, document statuses, citations, and downloads are internally consistent.
The site should make LMR easier to read, not easier to misread.
Content Structure
Confirm that the site includes:
- Home
- Start Here
- Papers
- Concepts
- Diagrams
- Supplements
- Working Notes
- Reference
- Roadmap
- Downloads
- About
Confirm that each section has an index page.
Confirm that the site structure matches:
content/site-map.mdcontent/navigation.md
Foundational Papers
Confirm that the Papers section includes:
- Paper 0
- Paper I
- Paper II
- Paper III
- Paper IV
- Paper V
Confirm that each paper page includes:
- status
- authority
- role in LMR
- what the paper establishes
- what the paper does not do
- related materials
Published Paper Links
Confirm that published papers have:
- official title
- version
- DOI or official release link
- public PDF link if available
- Release Registry entry
- Downloads entry
Published papers should not be linked only through temporary upload names, private paths, or Overleaf preview links.
Manuscript Links
Confirm that formal manuscripts have:
- title
- status
- version or draft label
- date if available
- public PDF link if available
- Release Registry entry
- Downloads entry
Manuscripts should be clearly distinguished from published papers.
Supplements
Confirm that supplements are labeled as supplements.
Supplements must not be presented as governing sources.
Confirm that S1 and S2 link back to the papers they support.
Confirm that internal Paper VII seeds are not grouped as public Arc 1 supplements.
Working Notes
Confirm that working notes are labeled as exploratory, frontier, or future-paper material.
Working notes must not be presented as codex authority.
Confirm that each working-note section states that Arc 1 governs.
Companion Volumes
Confirm that companion volumes are labeled as interpretive architecture.
Companion volumes may organize reading, overlays, and correspondence layers.
They must not modify Arc 1.
Tier Discipline
Confirm that Tier 1, Tier 2, and Tier 3 are clearly distinguished.
Check that:
- Tier 1 pages do not import forces, fields, or dynamics
- Tier 2 pages are declared as overlays
- Tier 3 pages are declared as SI correspondence
- Tier 3 claims are not promoted into Tier 1 ontology
- overlays are not treated as foundational primitives
Corridor Discipline
Confirm that no page introduces new primitive corridors.
The site should preserve the closed corridor discipline of Arc 1.
Allowed foundational corridor language includes:
- c corridor
- √c
- X corridor
- √G′ corridor
- Rabs as structural support signature
Do not introduce new roots, new hidden constants, or new primitive operators unless they are explicitly marked as later exploratory material.
Dynamical Language Audit
Search the site for the following words:
- force
- field
- dynamic
- mechanism
- interaction
- particle
- potential
- energy transfer
- propagation
- attraction
- repulsion
- orbit
- curvature
- spacetime
- collapse
- cause
These words are not automatically forbidden, but they require context.
If they appear in Tier 1 material, confirm they are either:
- explicitly denied
- carefully fenced
- used only as contrast with standard physics
- used outside Tier 1
Notation Audit
Confirm that notation is consistent.
Check especially:
- M′
- λ
- f
- X
- q′
- √G′
- Rabs
- ℓm
- mid₁
- Ẑ
- ξ̂
Confirm that ℓm is not promoted into a final Tier 1 primitive.
Confirm that M′ is not described as ordinary SI mass.
Confirm that q′ is not described as standard electric charge except in Tier 3 comparison.
Confirm that √G′ is not described as Newtonian G.
PDF Assets
Confirm that all public PDFs are stored in:
public/pdfs/
Confirm that public PDF filenames use underscores.
Confirm that no public PDF filename contains:
- spaces
- “final final”
- “latest”
- “real”
- temporary Overleaf labels
- private upload names
Confirm that Downloads, Release Registry, and actual PDF files agree.
Link Audit
Check every Markdown link.
Confirm that:
- relative links resolve
- PDF links resolve
- navigation links resolve
- paper pages link to Downloads
- Downloads links to Release Registry
- Release Registry links to Status and Versioning
- Reference pages cross-link correctly
Private Path Audit
Search the site for private paths.
Remove or replace any path containing:
- local machine directories
- user home folders
- private Overleaf project URLs
- temporary uploads
- unsanitized file names
- private working folder names
Public site links should not expose private file organization.
Citation Audit
Confirm that citation guidance is consistent.
Published papers should use DOI or official release links.
Formal manuscripts should use title, version, and date.
Supplements should be cited as supplements.
Working notes should be cited as working notes.
Concept pages should not be cited as primary theory sources.
Homepage Audit
Confirm that the homepage states:
- what LMR is
- what LMR is not
- where to begin
- why Arc 1 matters
- how to access papers
- how to avoid category errors
The homepage should not overclaim.
Avoid language such as:
- proves everything
- final theory
- replaces all physics
- experimentally confirmed
- derives all constants
Use restrained codex language.
Start Here Audit
Confirm that Start Here provides:
- basic orientation
- reading order
- tier discipline
- concept map
- warning against dynamical misreadings
- link to Paper I
- link to Reading Paths
Start Here should be the safest first reader experience.
Visual Assets
Confirm that diagram images are:
- clear
- labeled
- connected to diagram pages
- not presented as literal particle diagrams
- not presented as dynamical mechanisms
Diagram captions should explain that diagrams are grammar.
Final Human Review
Before launch, read the site in this order:
- Home
- Start Here
- Papers index
- Paper I page
- Concepts index
- Diagrams index
- Reference index
- Downloads
- Release Registry
- Status and Versioning
Confirm that a first-time reader can understand the hierarchy before encountering frontier material.
Launch Decision
The site is launch-ready when:
- the content tree matches the Site Map
- all links resolve
- all public PDFs resolve
- status labels are consistent
- tier discipline is preserved
- no private paths remain
- no unfinished placeholders appear on primary pages
- no lower-status page overrides a formal paper
Related Materials
content/site-map.mdcontent/navigation.md- Status and Versioning
- Release Registry
- PDF Assets and File Naming
- Codex Import and Build Workflow