PDF Assets and File Naming
This page defines how official LMR PDF files should be named, stored, linked, and referenced by the website.
The purpose is to prevent Codex, future site builders, or deployment tools from guessing file names.
⸻
Rule
Every public PDF should have: • a stable file name • a document title • a status • a version label • a release date or draft date • a matching Release Registry entry • a matching Downloads entry
The PDF file name should not change unless the version changes.
⸻
Recommended Folder
Store public PDFs in public/pdfs/.
This gives each PDF a stable public path.
Example file path: public/pdfs/lmr_paper_i_codex_v1.0.pdf
The website link would then point to /pdfs/lmr_paper_i_codex_v1.0.pdf.
⸻
File Naming Pattern
Use lowercase names with underscores.
Recommended pattern:
lmr_[document_type][identifier][short_title]_[version].pdf
Examples: • lmr_paper_0_geometric_foundations_v0.1.pdf • lmr_paper_i_codex_v1.0.pdf • lmr_paper_ii_lattice_v1.0.pdf • lmr_paper_iii_emergence_structure_v1.0.pdf • lmr_s1_routing_modes_v0.1.pdf • lmr_s2_hourglass_walkthrough_v0.1.pdf
⸻
Avoid
Avoid spaces, special punctuation, duplicate version names, and unclear draft labels.
Do not use names like: • Paper V final final.pdf • LMR latest.pdf • New Paper.pdf • Paper_III_Updated_REAL.pdf
These names are useful privately but not suitable for public release or site linking.
⸻
Document Identifiers
Use these identifiers consistently:
Document Identifier Paper 0 paper_0 Paper I paper_i Paper II paper_ii Paper III paper_iii Paper IV paper_iv Paper V paper_v S1 s1 S2 s2 Companion Volume I companion_i Companion Volume II companion_ii Tier 3 Crawl tier_3_crawl Tier 3 Dissemination tier_3_dissemination Position Paper 0 position_paper_0 Position Paper 1 position_paper_1 Position Paper 2 position_paper_2 Position Paper 3 position_paper_3 Position Paper 4 position_paper_4
⸻
Recommended Public PDF Names
Foundational Papers • lmr_paper_0_geometric_foundations_v0.1.pdf • lmr_paper_i_codex_v1.0.pdf • lmr_paper_ii_lattice_v1.0.pdf • lmr_paper_iii_emergence_structure_v1.0.pdf
Supplements • lmr_s1_routing_modes_v0.1.pdf • lmr_s2_hourglass_walkthrough_v0.1.pdf
Companion Volumes • lmr_companion_i_overlay_architecture_v0.1.pdf • lmr_companion_ii_lm_reduced_si_correlation_v0.1.pdf
Tier 3 Notes • lmr_tier_3_mass_is_inverse_length_v0.1.pdf • lmr_tier_3_kilogram_redundant_dynamics_v0.1.pdf • lmr_tier_3_shared_dimensional_backbone_v0.1.pdf • lmr_tier_3_fine_structure_constant_v0.1.pdf • lmr_tier_3_crawl_v0.1.pdf • lmr_tier_3_dissemination_v0.1.pdf
Position Notes • lmr_position_paper_0_what_lmr_is_v0.1.pdf • lmr_position_paper_1_three_tier_discipline_v0.1.pdf • lmr_position_paper_2_mass_is_inverse_length_v0.1.pdf • lmr_position_paper_3_kilogram_redundancy_v0.1.pdf • lmr_position_paper_4_hourglass_architecture_v0.1.pdf
⸻
Metadata Rule
Each PDF should eventually include visible frontmatter or first-page metadata: • Title • Author • Document Status • Version • Date • Canonical Citation • Website URL
Example:
Length–Mass Reduction Paper I: Codex and Foundational Grammar
Author: Jacob Rollins Status: Published Paper Version: 1.0 Date: TBD Citation: DOI / official link TBD Website: TBD
⸻
Link Rule
Downloads pages should link directly to the public PDF path.
Example:
PDF path example: /pdfs/lmr_paper_i_codex_v1.0.pdf
Do not link to temporary upload names, local machine paths, Overleaf project URLs, or private filenames.
⸻
Registry Rule
Every PDF listed publicly should appear in: • Release Registry • Downloads
The file name in the Release Registry and Downloads page should match the actual file in public/pdfs/.
⸻
Overleaf Export Rule
When exporting from Overleaf:
- Download or compile the final PDF.
- Rename the PDF according to this guide.
- Place it in public/pdfs/.
- Update the Release Registry.
- Update the Downloads page.
- Run a link check.
Do not use Overleaf’s temporary compiled PDF name as the public website file name.
⸻
Codex Rule
When Codex is used to build or update the site, it should not invent PDF file names.
Codex should use only file names listed in this guide, the Release Registry, or the Downloads page.
If a PDF file is missing, Codex should report it rather than create a guessed link.
⸻
Related Materials • Release Registry • Status and Versioning • Citation • Downloads