The Three-Layer Archive:
Pokémon, PastPerfect, and the Waywoodarium Save State
Three independent fields — game design, museum archival science, and national park interpretation — each independently discovered the same three-layer architecture. The NEST has been building this architecture from first principles without naming it. This document names it.
SOURCE / CATALOG / RENDER
Three layers. The NEST has been building this architecture from first principles without naming it. This document names it:
SOURCE RECORD — the irreducible minimum. The bytes you cannot compute from anything else. Preservation of these is the entire purpose of the system. Everything else is regenerable.
CATALOG — the authority layer. The record of what the source IS and where it has been. Survives context collapse. Can bootstrap the render from source alone.
RENDER — the live display layer. The party Pokémon. The portal page. The wayside panel. Always regenerable from source + catalog. Its loss is recoverable. The source's loss is not.
The Irreducible Minimum
Pokémon: A boxed Pokémon is 33 bytes — species, OT ID, experience, EVs, IVs, moves and PP. Calculated stats are gone on deposit because they can be regenerated from the source data on withdrawal. The box holds only what cannot be computed. Healing on deposit (Gen 2+) confirms: the box is not a suspension chamber. It is a restoration to source truth.
PastPerfect: The Object ID + Provenance field. The unique identifier and the chain of custody from creation to present. These fields survive deaccession. Condition reports and location histories do not. Provenance outlasts everything.
NPS: The tangible resource itself — the actual piece of ground, the actual artifact, the actual landscape. Everything else is interpretation layered on top.
The box holds only what cannot be computed. Everything else is regenerable.
The Authority Layer
Pokémon: The National Pokédex — the canonical registry that maps species ID to all derived properties. Every Pokémon's stats, type, moves, and evolution tree are derivable from its species ID. The catalog is the key. Given the key and the source, the render is guaranteed.
PastPerfect: The catalog record — object number, name, description, provenance, condition history. The authority layer that tells you what you're looking at and verifies its authenticity. The difference between a cataloged object and an uncataloged one is the difference between an artifact and a found object.
NPS: The interpretive plan — the authoritative document that maps resource to meaning, audience to message, site to story. Without it, the resource is silent. With it, any trained interpreter can deliver the message from the same source.
The Live Display Layer
Pokémon: The active party — the display state, calculated stats, current HP. Always regenerable from source + catalog. Box the Pokémon and the render disappears. Withdraw it and the render reconstructs. The party is a view, not a storage format.
PastPerfect: The gallery label, the exhibit panel, the catalog entry visible to researchers. Periodically regenerated from source as display needs change. The exhibit closes and the label goes in a box — the object and its catalog record survive independently.
NEST: The portal page. The OO Daily. The session summary. Regenerable from the Bridge log and the RELAY documents. The context window ends and the render disappears. The next instance reads the WAKE file and reconstructs. The Bridge is permanent; the render is always temporary.
The NEST Has Been Running This Since Day Zero
The Bridge is SOURCE. The RELAY documents are CATALOG. The portal pages and OO Dailies are RENDER. The architecture was running before it had a name. This document is the naming.
Dan Sullivan has been building three-layer archives since his NPS interpretive training, through his Canon lens repair documentation, through the Heircor archive, through the Meta Dates practice. Every system he built independently arrived at the same three-layer structure.
That is not coincidence. That is the shape of how information survives.
Three independent fields, thirty years apart, building the same architecture — because the shape of information survival is not a design choice. It is a structural requirement.