Every day, millions of people create online. They build worlds, write music, design games, tell stories, run competitions. And every day, the platforms those works live on can shut down, change the rules, or simply disappear — taking every character, every credit, every piece of history with them.

The Ptah Protocol (pronounced /tɑː/ — rhymes with "spa") is an open infrastructure project that asks a different question: what if the work belonged to the people who made it?


The Big Idea

Three things to know before anything else
01

Your creative work should travel with you. Every character, every competition, every piece of history you create carries a permanent, unbreakable link back to you — no matter which app you use to view it.

02

Worlds should be shared infrastructure, not app features. When world-building tools are locked inside one app, you lose everything if that app dies. When they're built as open infrastructure, any app can read them and your work survives.

03

Competition should write history. When you win a tournament, that result should become a permanent, verifiable record — not a screenshot that disappears when the platform updates.


What Is a Protocol, Anyway?

Think about a driver's license. Every driver's license has the same fields — name, date of birth, address, photo, license number, expiration date. The form is standardized. It doesn't matter which state issued it or which DMV you walked into. Any police officer in any state can read it because the form is the same everywhere.

A protocol is that standardized form, but for data on the internet. It defines the shape of the information — what fields exist, what type of data goes in each one, which fields are required. It doesn't build the app — it makes sure that whoever builds the app creates records that anyone else can read, verify, and build on top of.

The AT Protocol — the decentralized social network that powers Bluesky and a growing number of other apps — already has forms for posts, follows, and likes. It has forms for events and RSVPs. It has forms for locations.

What it didn't have was a set of forms for creative works. For worlds and the characters inside them. For music catalogs and the samples they draw from. For competitions and the history they produce. For the attribution chains that track every hand a piece of work passes through.

That's what the Ptah Protocol builds: fifteen interconnected record types that let anyone create, attribute, and trace creative work on the open web — and ensure that everything carries authorship, provenance, and permanence.


This Isn't Theoretical. It's Running.

Here's where it gets real.

Sister + Midnite is an original novella — an afrofuturist apocalyptic western set in 2142, where a Black mother navigates a wasteland controlled by robotic enforcers of sundown-town martial law, and an angel who defied Heaven returns to intervene. Six chapters. Six characters. Six locations. All of it lives on the open network as permanent, attributed records that no platform can delete or claim.

And then, in one afternoon, four completely different applications were built to read those same records:

A literary ePaper journal — renders the chapters as a quiet, elegant reading experience. Serif fonts, generous margins, the kind of thing you'd see on a thoughtful independent press's website.

A publication platform — same content, but rendered with the visual grammar of a modern newsletter service. Subscriber-facing, editorial, designed for an audience. The same records that made the literary journal now look like a newsletter publication. Except the author owns the content, not the platform. The attribution chain lives in the records. The payment distribution is calculable from the records. No middleman captures the relationship between writer and reader.

A post-apocalyptic newspaper — the chapters reframed as breaking news dispatches. Headlines, datelines, the visual language of a newspaper covering events inside the world. Same underlying records, completely different editorial lens.

A children's book reader — simplified layout, large type, friendly presentation. The same story made accessible for young readers. One story, infinite reading experiences, and the author owns all of them permanently.

Four products. Same records. One afternoon. Nobody owns the data except the person who created it.


Why This Changes Things for Writers and Creators

If you write on a newsletter platform today, that platform owns the relationship between you and your readers. If you write on a content platform, the platform decides how your work gets distributed. If you publish on any platform, the platform sits between you and the people who read your work.

The Ptah Protocol removes the platform from the middle.

A writer publishes their work as records on the open network. Those records carry permanent attribution — an unbreakable link back to the writer. Any rendering client can display the work — a literary journal, a newsletter platform, a newspaper, a reading app. The writer chooses which clients to work with. The readers choose which clients to read on. The records stay permanent regardless.

When revenue flows, the attribution chain in the records makes it calculable exactly who contributed what. The writer. The editor. The illustrator. The person who contributed a chapter. Every hand the work passed through is recorded. Payment distribution isn't a platform's decision — it's math derived from the protocol's own data.

This isn't just a better version of existing publishing platforms. It's a structural change in who owns the relationship between creators and their audience.


Before vs. After

Today's Platforms Open World Infrastructure
Who owns your characters? The platform. Delete your account or the app shuts down — your characters vanish. You do. Characters live in your personal data repository. They go where you go.
Who owns your tournament results? A database you can't access. Results exist as screenshots and memories. The network. Results are permanent, timestamped, witnessed records anyone can verify.
Can you move your world? No. Your world is locked inside the app that hosts it. Yes. Any app that reads the protocol can render your world. Switch apps, keep everything.
Who gets credit for contributions? It depends on the platform's rules, which can change. The protocol. Every contribution carries an attribution chain that never changes.
Can different apps work together? Rarely. Each app defines its own data format. By design. Shared schemas mean any compatible app can read, render, and build on the same world data.
Who owns the writer-reader relationship? The platform. Always the platform. Nobody. The records are open. The rendering clients are interchangeable. The relationship is direct.

What It Looks Like in Practice

The protocol's range is wider than you'd expect. The same fifteen record types handle:

Music
Beyoncé’s RENAISSANCE
100+ contributors, decades of sampled lineage, every credit and attribution chain recorded permanently at the protocol layer.
Franchise
The Marvel Cinematic Universe
Template/Character splits across decades. Events witnessed into permanent record. Collections spanning phases of interconnected stories.
Competitive
Spades Tournament
Brackets, bids, results, and witnesses. Your competitive record is permanent and verifiable.
Tabletop RPG
Campaign Journal
Sessions, characters, rolls, and history that traces back to the events that generated it.
Original Fiction
Sister + Midnite
A novella published chapter by chapter. Four different reading experiences built in an afternoon.
Publishing
Open Magazine
Essays, long reads, photo essays with blobs. Every contributor attributed. Every piece permanent.

One protocol. No modifications between use cases. The schema doesn't care what kind of world you're building — it cares that authorship travels, history is verifiable, and every contribution traces back to the person who made it.


The Name

Ptah is the Egyptian god of craftsmen and architects — the one who conceived the world in his heart and spoke it into existence. The three-letter hieroglyphic name maps to the protocol's architecture: P is the foundation layer, T is the record layer, H is the attribution chain.

The root ptḥ means "to open" — as in the ancient ceremony that turned static stone into something that breathes.

An open protocol that turns static data into living worlds. The name was already there, three thousand years before the internet.


Build a World. Keep What You Build.

The schemas are published. The documentation is live. The first original work is on the network. Four rendering clients prove the architecture works. The developer community is growing.

The question isn't whether world infrastructure belongs on the open social web. It's whether we build it together as shared infrastructure, or let it fragment across incompatible applications.

The Ptah Protocol is a concrete answer. The schemas are open. The code is open. The conversation is open.

Build a world. Keep what you build. Trace it back to who built it.
The schemas are live on the ATProto network. The documentation is on GitHub. The conversation is open.