ergodic literature // co-authored // persistent
In 1997, Espen Aarseth coined ergodic literature for texts that demand non-trivial effort to traverse. The reader does work. The text responds. Archipelago asks what happens when ergodic texts are inhabited: multiplayer, event-sourced, authored while readers move through them. The local world now runs. The archive, portable histories, and complete federation remain work rather than premise disguised as fact.
Rooms and characters are written in Markdown, seeded into PostgreSQL, and changed through immutable events. The engine preserves the material from which a literary archive can be made. It does not yet project that history into a finished public narrative.
A room is a passage with a brief, full description, exits, examinable details, and separate smell, sound, touch, and taste data. Authors write the baseline directly. The engine can compose context around it without surrendering the sentence to generation.
Authored greeting and topic banks work without a model. The optional brain adds witnessed-event memory, reflection, planning, schedules, activation, and budgets. Memory storage is durable; the final return-visit experience is still being joined to every connection path.
Events, transaction IDs, signatures, projections, snapshots, and upcasters already preserve the history. The Archive—the readable prose projection of that record—is explicitly planned and not a current reading surface.
Client-side encryption, sealed-mail envelopes, routing, and physical mailboxes are specified but unimplemented. The epistolary form belongs to the design horizon, not to the current realm.
Pergamum already accepts and lists signed operator-log excerpts and exposes an Atom feed. This is the first public literary surface connected to the code: small dispatches from a realm, not a generated chronicle.
Pergamum records content hashes and fork lineage for published patterns now. In-world item provenance and customs verification remain Phase 5 work. The pattern can show its ancestry; the sword cannot yet show its voyage.
The current engine combines spatial prose, parser action, multiplayer presence, authored conditional response, persistent world events, and sensory traversal. Temporal rewriting, public archival prose, and cross-realm intertextuality are not complete. The structures already meet; they do not all close.
Archipelago descends from three traditions. Each solved part of the problem. None solved it whole.
Crowther's Adventure (1976) proved that prose could be spatial — that you could distribute a text across a geography and let the reader navigate it. Infocom refined the parser into a literary instrument. Inform 7 made authoring accessible. The IF community developed a forty-year craft of conditional, responsive prose.
What was missing: other readers. Persistence between sessions. A world that continued without you. The parser tradition produces brilliant single-reader works. Archipelago asks what happens when the cave has other explorers in it, and remembers all of them.
Michael Joyce's afternoon, a story (1987) and Shelley Jackson's Patchwork Girl (1995) established hypertext as a literary form. Aarseth's Cybertext (1997) gave us the vocabulary. Twine democratized the tools. The tradition produced works that reward non-trivial traversal — texts you read with your body, not just your eyes.
What was missing: multiplayer co-reading and accumulation over time. Archipelago is building the event and presence substrate for texts still being written while they are read—by the operator, other readers, and bounded character systems.
MUDs (1978–) proved that spatial text could be multiplayer and persistent. LambdaMOO demonstrated player-authored content. SkotOS (1999–2020) pushed NPC depth, social mechanics, and prose quality further than any commercial MUD. The tradition produced worlds that ran for decades.
What was missing: federation, sovereignty, and the recognition that each world can remain a separate author's work. Archipelago has implemented the trust and message boundary first; the networked literary surface comes after it.
We have tools for single-author ergodic works (Inform, Twine, Ink, Ren'Py). We have tools for multiplayer persistent worlds (MUD codebases, game engines). We do not have a tool designed from the ground up for co-authored ergodic literature — works where multiple authors contribute to a living text, where readers leave permanent traces, where the accumulated history is itself a literary artifact.
The closest precedents are collaborative fiction wikis, play-by-post forums, and long-running MUSHes. All of these produce remarkable texts. Archipelago begins from their hard problems: state, presence, authorship, memory, moderation, and the difference between an event record and a sentence.
Archipelago is an attempt to build that engine. Each realm is meant to remain a work with an author-in-residence. Today the event-sourced local world and the first federation messages exist. Item voyages, realm-crossing characters, sealed correspondence, and the Archive remain propositions the code has not yet fulfilled.
readers
Move through authored rooms, read details through several senses, speak in shared space, and encounter characters with topic banks and bounded cognition. The realm records events even where the final narrative projection is absent.
authors
Author rooms, characters, items, details, rules, senses, and operator logs. Markdown is the durable source; live editing is an event transaction. You remain responsible for the line when every model and budget is silent.
worldbuilders
Publish patterns to Pergamum — the registry where reusable creative artifacts live. Fork others' work. Build realm archetypes. A published pattern is a work in its own right; the registry is an anthology. The Inform 7 extension library, but for inhabited worlds.
scholars
Study the event model, parser, authored corpora, bounded cognition, and the gap between durable history and literary projection. The unfinished joins are part of the medium's evidence, not something the site conceals.
IF authors
You already know conditional prose, spatial text, and the parser as conversation. Archipelago adds multiplayer presence, event sourcing, Markdown content schemas, and an experimental memory layer. The craft transfers; the tooling is still young.
Inform 7 gave authors a natural-language way to write conditional, spatial prose. Archipelago currently adds event-sourced state and multiplayer co-reading; federation between playable works is still being built.
Twine democratized hypertext fiction. Archipelago explores memory and co-presence without claiming that every returning session is already reconstructed.
Galatea proved a single NPC with deep state could carry a work. Here, authored banks and a supervised cognitive loop are being joined under explicit cost and authority limits.
LambdaMOO proved player-authored persistent worlds could run for decades. Archipelago takes the literary frame as a design constraint; only the operator log has reached a public reading surface so far.
House of Leaves is a text navigated spatially on paper. Archipelago's current realm is spatial text in real time with other readers; durable personal path memory remains incomplete.
The local text can be inhabited now. Its archive and crossings are still dark water.