Frequently asked questions.
For the full standard, validation rules, and a worked example, see the technical documentation.
Question 1: Why Pergamon and Archimedes?
You have probably heard of the Library of Alexandria, where knowledge was gathered onto papyrus scrolls.[^1][^3] Less familiar is Pergamon, Alexandria’s great rival, which became traditionally associated with parchment as an alternative writing substrate.[^1][^2] The lesson we take from that history is simple: knowledge becomes less fragile when it is no longer bound to a single medium. Project Pergamon takes its name from that principle. We are building an institution around the problem of preserving knowledge at historical timescales.
The Archimedes Series and ARCHI archival standard are named for the Archimedes Palimpsest. This artefact supports our thesis that preservation efforts must extend to material for which the means of interpretion have not yet been invented. You can learn more about how new technology decoded an ancient message through the Walters Art Museum's website on the project
Question 2: Why “public” rather than “open source”?
We use “public” because “open source” has become a contested term in AI, especially in cases where model weights are publicly released but training data or other components remain undisclosed.[^4][^6][^7] “Publicly released,” by contrast, is a verifiable fact: the rights-holder made the model available for public download on documented terms.
Pergamon is designed to record those distinctions rather than blur them. Our metadata profile distinguishes a component that was withheld — for example, when a rights-holder chose not to release training data — from one that is merely unknown, where public evidence was insufficient to establish provenance with confidence. That accession record gives future researchers a clearer account of institutional decision-making, including the present-day drift toward decoupling public weights from open training.
Question 3: Why not just leave this to existing online repositories like Hugging Face?
Online availability is not the same thing as durable survival.[^8][^9] Publicly released models can be delisted, neglected, censored, fragmented across platforms, or rendered unusable when the surrounding technical context disappears. A live download link is a convenience left to someone else’s discretion, without any preservation guarantee.
Physical, independently held copies add custody, independence, and durability that networked distribution alone cannot promise.
Question 4: Isn’t this what OAIS and existing preservation standards already do?
The OAIS Reference Model (ISO 14721) is part of the foundation we build on, and Pergamon is designed to conform to it wherever it applies.[^10][^11] But OAIS is a general preservation reference model, not an AI-specific archival profile. The information needed to interpret a generative AI model is not exhausted by its source code, nor by any other single technical artifact.
On this frontier, the work of future historians may resemble philology more than direct reference: inferring meaning from a bundle of materials without full access to the people and institutions that produced them. Pergamon’s metadata format is expressed as a profile of the widely used BagIt packaging standard (RFC 8493), and it maps onto OAIS concepts while addressing the distinctive preservation problem posed by generative AI.[^12]
Question 5: Why not existing software archives?
Because most existing software archives solve an adjacent problem, not the full preservation problem for public AI. Code archives are essential for preserving repositories, version history, and source files. But a generative model is not reducible to source code alone. Its historically meaningful record includes weights, architecture, tokenizer, provenance, documentation, and the terms under which different components were released or withheld.
Project Pergamon is designed to complement those archives, not replace them. The problem is not just storing files. It is preserving the conditions under which historically significant public AI systems can still be understood, verified, and reconstructed in the future.[^10][^12][^13]
Question 6: Isn’t this just LOCKSS?
LOCKSS — “Lots of Copies Keep Stuff Safe” — is one of our aspirational models.[^13][^14] Its core insight is social as much as technical: many independently administered copies, continually checking one another, are stronger than any single custodian. That is a standard Pergamon’s emerging governance model will need to meet.
But LOCKSS was built to preserve web-published, renderable records gathered by crawl. A frontier AI model is much larger, not ordinarily web-harvestable, and better understood as a technical system to be interpreted rather than a page to be rendered. Pergamon extends the LOCKSS logic to that new kind of artifact. Our packaging approach is designed to remain interoperable with adjacent archival systems rather than locked inside a single preservation silo.[^12][^13][^15]
Question 7: Isn’t tape obsolete? Why build on it?
The Linear Tape-Open (LTO) format remains one of the proven, scalable, and low-energy choices used in working archives today.[^16] It is not a magical forever medium, and we do not present it that way. Real preservation depends a disciplined archival format and workflow: the institutional challenge that no one medium solves once and for all. Our initial preservation horizon is measured in planned migration cycles, while our logo, a snake who sheds his old skin for the new, speaks to the growth of knowledge across materials. Over longer timescales, the archive may well move onto other media, including ceramic- or silica-based substrates, if and when they become viable.[^17][^18]
Question 8: Will these models still run in the future?
We do not guarantee that the future computing environment will run today’s models exactly as they run now. What Pergamon preserves is the record future custodians would need to reconstruct, emulate, or meaningfully interpret them.
That includes weights, architecture, and the surrounding documentation needed to recover a model’s technical logic as honestly as possible. Future performance may in fact depend on a world we do not control; That is why we strive to improve the odds that reconstruction and emulation remain possible.
Question 9: What about models that are dangerous or legally restricted?
This concern is real. Publicly released models can be used against the public's interests, and Pergamon does not dismiss that risk. But preservation does not create public access where none existed before: the models we preserve are already publicly released.
Pergamon also does not position itself as a universal arbiter of which models are acceptable everywhere. Instead, we are designing an archival framework in which different jurisdictions and institutions can govern access to weights, training data, execution requirements, or other components differently. Just as important, those restrictions become part of the archival record itself.
Question 10: How do you preserve training data and checkpoints?
Models with pubicly available training data are linked to that corpus by reference: a practical and legal decision. Practically, an LLM with final weights measured in gigabytes may have been trained on a corpus of tens of terabytes. And embedding every corpus inside every model's record would be redundant, since a single corpus is often shared across many models. The legal concern runs deeper: A training corpus is usually not the model-maker's to give away. Pre-existing works that belong to others and are held elsewhere (web pages, books, code, images) fall outside the responsible mandate of a public AI archive. Where a corpus is openly liscenced and seperately stewarded, we point to it as its own preserved artifact. Our records remain comapct, lawful, and honest: we never pretend to hold what is better served elsewhere.
Notes
- 1 Encyclopaedia Britannica, “Parchment,” https://www.britannica.com/topic/parchment
- 2 Encyclopaedia Britannica, “Pergamum,” https://www.britannica.com/place/Pergamum
- 3 Encyclopaedia Britannica, “Library of Alexandria,” https://www.britannica.com/topic/Library-of-Alexandria
- 4 Open Source Initiative, “The Open Source AI Definition – 1.0,” https://opensource.org/ai/open-source-ai-definition
- 5 Open Source Initiative, “Open Source AI,” https://opensource.org/ai
- 6 Open Source Initiative, “Openwashing: An accusation against some A.I. companies…,” https://opensource.org/press-mentions/openwashing-an-accusation-against-some-a-i-companies-that-they-are-using-the-open-source-label-too-loosely
- 7 Nature, “‘Open source’ AI isn’t truly open — here’s how researchers can reclaim the term,” https://www.nature.com/articles/d41586-025-00930-6
- 8 Hugging Face Docs, “The Model Hub,” https://huggingface.co/docs/hub/models-the-hub
- 9 Hugging Face Docs, “Hugging Face Hub documentation,” https://huggingface.co/docs/hub/main/index
- 10 ISO, “ISO 14721:2025 — Reference model for an Open Archival Information System (OAIS),” https://www.iso.org/standard/87471.html
- 11 CCSDS, “Reference Model for an Open Archival Information System (OAIS),” https://ccsds.org/Pubs/650x0m3.pdf
- 12 IETF Datatracker, “RFC 8493: The BagIt File Packaging Format (V1.0),” https://datatracker.ietf.org/doc/rfc8493/
- 13 LOCKSS Program, “How LOCKSS Works,” https://www.lockss.org/use-lockss/how-lockss-works
- 14 LOCKSS Documentation Portal, https://docs.lockss.org/en/latest/
- 15 NDSA, “Levels of Digital Preservation,” https://www.ndsa.org/publications/levels-of-digital-preservation/
- 16 LTO Program, “LTO Ultrium: Reliable and Scalable Open Tape Storage Format,” https://www.lto.org/
- 17 LTO Program, “Linear Tape File System (LTFS),” https://www.lto.org/linear-tape-file-system/
- 18 IBM Docs, “LTFS format,” https://www.ibm.com/docs/en/storage-archive-le/2.4.7?topic=overview-ltfs-format