Codex Protocol
Distributed Cultural Heritage
The Challenge
The Problem of Permanence
Image API
Presentation
Annotation
Search
Content State
IIIF built five rings. Each solves access. None solves permanence.
We built cathedrals of knowledge on rented land.
Core Innovation
Content Addressing
Location-Based
museum.org/image.jpg
Server dies → content gone
Fragile. Centralized. Ephemeral.
Content-Based
bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi
The content is its own address
Resilient. Distributed. Permanent.
No one owns it. Everyone can serve it.
Content-Addressed Storage
01
IPFS Protocol
Files distributed across network nodes — any node with a copy can serve it
02
Content Identifiers (CID)
Hash derived from content itself: bafy...7xk2
03
Key Insight
Content is its own address — change one pixel, hash changes
If I create an annotation and store it on IPFS, anyone with that CID can retrieve it — not from my server, but from any node on the network that has a copy
Boston Creates
Annotation → CID generated
Berlin Retrieves
Requests same CID instantly
Berlin Preserves
Pins content as steward
Technical Foundation
How It Works
01
Content Snapshot
Capture full state at moment of engagement
02
Content Addressing
Generate cryptographic identifier (CID)
03
IPFS Distribution
Store across peer network
04
Metadata Mapping
Translate to/from 20 canonical elements
05
Network Retrieval
Access from any participating node
Universal Translator Layer
IIIF
Scholarly intent preserved
Dublin Core
Institutional metadata
Four Corners
Authorship & credit
MODS/VRA
Scientific & archival
20 Canonical Elements
Derived from established standards — enough to round-trip between formats without data loss
Format-Agnostic
Nested metadata, multiple formats. Translation preserves intention, not just information
The Hinge
Foundation Layer
Not an extension—a substrate beneath. Codex sits as a foundational layer underneath IIIF, Dublin Core, MODS, VRA Core, and Four Corners.
20 Canonical Elements
Full round-trip compatibility with all major metadata standards
Zero Lock-In
The hinge connects without coupling—preserving institutional autonomy
Universal Substrate
A common foundation that makes every platform survivable
Beyond Self-Hosting
Pin your own content = abandonment with extra steps
  • Single point of failure remains
  • No redundancy guarantee
  • Institutional mortality unchanged

True preservation requires mutual commitment across institutions.
The commons has no consumers — only participants
Harvard
Stores Yale's snapshots
Smithsonian
Stores small museum's content
Local Archive
Stores Harvard's metadata
Storage is the currency. Participation is the price of preservation.
Curiosity creates the archive.
Permanence
Distribution
Stewardship
Authenticity
Resilience
The substrate that makes all platforms survivable.
Participation is PERMANENCE
Curiosity is Collaboration
Let's Connect
@thetechmargin
IG: @TheTechMargin