The downloadable repository is the durable copy of InfoPreserver. Use the full archive to create a local baseline, then apply periodic incremental ZIP files in sequence. The archive contains the source PDFs, folder READMEs, printable *_Wiki_Page.pdf guides, manuals, assets, and theme files.
Verify the checksum before unpacking. Apply incrementals in release order, allowing newer files to replace older files at the same relative path. Do not delete files merely because they are absent from an incremental. Preserve local edits separately and record each applied release.
This section is the authoritative steward fallback while the dedicated download route is repaired.
ReadMe Maps are the editorial orientation layer for InfoPreserver. These pages explain how to use the library, how the A0-A5 Rebuild Ladder works, how promotion decisions are made, and how practical roles mature into long-term professions.
This section is not ordinary topical content. It is the map for the rest of the repository. Readers should use it before judging where a PDF belongs or before assuming that a modern subject automatically belongs at a high A-level.
Start with How to Use This Library, then read the Rebuild Ladder. Use Promotion Rules and Gates when a document seems to fit more than one level. Use Dependency Stacks when a capability appears to require a chain of prerequisites. Use Professional Pipelines when the question is not only where a technology belongs, but who must learn, maintain, teach, and institutionalize it.
This branch contains the map PDFs used to build these pages:
_Docs/Editorial_and_Manifest_Guide.pdfHow_to_Use_This_Library/How_to_Use_InfoPreserver_v1.8.pdfRebuild_Ladder_A0-A5/Rebuild_Ladder_A0-A5.pdfPromotion_Rules_and_Gates/Promotion_Rules_and_Gates.pdfDependency_Stacks/Dependency_Stacks.pdfProfessional_Pipelines_Overview/Professional_Pipelines_Overview.pdfThe ReadMe Maps should be reviewed before broad public use because they shape every later classification decision. If these rules are wrong, the whole library drifts. If these rules are clear, future submissions can be placed, corrected, and promoted without turning the repository into a pile of disconnected PDFs.