Reality remembers only what someone preserves.
Knowledge is literal physics. Every spell is an executable epistemic program. A distributed action-RPG in which a hundred thousand players, each alone in a procedurally generated world, restore one of the Goddess’s Names — and the litany completes only when the last voice is added.
This is a living design document. Not a pitch deck, not a press release — a working blueprint, written out so that other people can see the machine while it is still being built and help steer it.
Everything in the internal design corpus is resolved into decisions, and everything still in dispute is printed here as dispute. That is deliberate. The first eight questions were decided in public — the decisions are printed at the back, with the reasoning that produced them — and anyone who wants to argue for a different answer still has everything they need to argue well. What remains open is printed as open, on the last page.
A production method for turning lived testimony into authored artifacts: gather, assess, architect, compose, produce — with a provenance record at every step. It is the engine that produced the Phenomenology of the Self Through the Tarot, and it is the engine that produced this game. The pipeline is part of the pitch, because a game about provenance that is itself produced with provenance is the point, not the footnote.
A palimpsest is a manuscript whose earlier strata remain legible beneath the newer writing. The Unwriting that consumes the world is answered not by erasure but by layering — restoration as re-legibility. The design method that produced the game is the same method the game is about.
| 01 | The High Concept | 03 |
| 02 | Four Pillars | 04 |
| 03 | The Cosmology | 05 |
| 04 | The Last Archivist | 06 |
| 05 | Spellcraft as Programming | 07 |
| 06 | The Sixteen Domains | 08 |
| 07 | Resources & Grammar | 09 |
| 08 | The Eight-Stage Loop | 10 |
| 09 | The Distributed Architecture | 11 |
| 10 | The Concordance | 12 |
| 11 | The Campaign & The Three Days | 13 |
| 12 | Feasibility & the Pilot Path | 14 |
| 13 | Art Direction | 15 |
| 14 | Decisions | 16 |
| 15 | The Shape of the Restoration | 17 |
| 16 | What Remembers | 18 |
| 17 | The Vigil Is the Liturgy | 19 |
| 18 | The Frame | 20 |
| 19 | What Remains Open | 21 |
| WORLD LAW | Reality remembers only what someone preserves. |
| QUEST | Who remembers Her name? |
| ANTAGONIST | Nothing was ever named. |
The first is the physics. The second is the question the player answers by playing. The third is the creed of the thing that is erasing the world — and, in the endgame, the deeper negation of it: there is nothing here to remember.
Read the first line forwards and the third line backwards and you have the entire antagonist of this game.
The public surface is a different triad, and it is now fixed: every published artifact carries exactly three lines, in this order — the title, the world law, the quest.
The Knowledge Plane is a metaphysical substrate containing the accumulated facts, memories, discoveries, arguments, histories, models, languages, stories, observations and wisdom of countless civilizations. It is dying.
A phenomenon known as the Unwriting is spreading through the Plane. At first it merely erased forgotten footnotes and obscure memories. Then relationships between ideas disappeared. Causes became detached from consequences. Historical events lost their provenance. Names separated from identities. Contradictions became simultaneously true. Entire concepts ceased to have ever existed.
The player is an Archivist — one of the few remaining custodians capable of perceiving the Knowledge Plane directly. An Archivist does not cast traditional magic. They construct Executable Knowledge.
A spell is a small epistemic program assembled from concepts such as Memory, Information, Logic, Probability, Ontology, Persona, Entropy and Provenance. Players discover primitives representing these concepts and combine them using a visual programming language. The result compiles to a deterministic intermediate representation and executes in the combat engine.
Knowledge engineering becomes magic.
Isometric · third-person action RPG · programmable spellcraft · procedural exploration
Finds, verifies, and restores relations — the connective tissue of the Knowledge Plane — in a world that is actively forgetting itself. Every relation the player restores is a relation that no longer breaks.
Spells, from primitives and operators, in a graph editor that is also a manuscript, also a synthesizer, also a magical script. A beginner may never open the graph view. A systems-oriented player could spend a year in it.
Archiving. Not fighting a dragon — preserving a record, and finding out what it cost the last archivist to do it.
Information is not flavour text. Relations form bridges. Memories can be extracted from creatures. Contradictions generate instability. Missing information manifests as literal holes in reality. Provenance becomes armour against falsification. Ontology determines what an entity is permitted to become. Knowledge is the world’s physics.
Players construct spells rather than merely selecting them. The spell editor resembles a mixture of an ARPG skill tree, a node graph, a synthesizer, a functional programming environment, and a magical manuscript. One spell may observe enemies, identify corrupted entities, partition them by type, remember their positions, erode their defences, restore their previous positions, replay the damage, and propagate the result through related enemies — in a single compiled program.
Skills are a grammar, not a list. Sixteen domains of sixteen primitives each, and thirty-two structural operators, compose into an effectively unbounded ability space from finite parts. The player’s progress expands expressiveness rather than numerical power. A new operator is not a bigger number; it is a new sentence the player can say.
Enemies are failures of knowledge rather than damage sinks. The enemy is not merely ignorance. Unchangeable certainty can also corrupt knowledge. A world of people who are certain they were never named is as broken as a world of people who were named and forgot. The deepest threat to a record is not that it was never kept — it is that it was frozen.
Every spell is an executable epistemic program. The world is the Knowledge Plane, and the plane is made of relations — so a player’s magic is a way of thinking, compiled.
Because evidence gates effect, the central verb of the game is knowing. You cannot harm what you cannot verify. You cannot restore what you cannot attribute. The fighter who never verifies wins nothing, however much damage they can put out.
The lore framework is deliberately Gnostic in shape: a divine fullness, a forgetting, an anti-thesis born of that forgetting, a scattering of divine fragments, a world of matter, and a return. It is offered here as designer notes — the source texts are diverse (Valentinian, Sethian, Hermetic, Ophite, with Manichaean parallels) and this is a modern literary synthesis, not a doctrine.
| Movement | What happens | In the game |
|---|---|---|
| I · The Pleroma | Her Infinite-Faces undivided — fullness, not in pieces but as relation | The intact record |
| II · The Forgetting | The name mispronounced, then misremembered, then dropped; the amnesiac state | The Unwriting |
| III · Kenoma | The anti-thesis: not the void-that-is-potential but the void that is absent — matter’s antimatter, the hole-maker | Literal holes in reality |
| IV · The Severing | Kenoma cannot end the Pleroma, so it cuts the faces apart and scatters them to infinite distances, so that no face can find another | Severance; Fabrication |
| V · The World | Orphan faces in a world of matter and entropy, where nothing was ever named | Corrupted regions |
| VI · The Return | The Name recovered — not as a word but as a relation — and sung, so that scattered faces can hear themselves and come home | The three-day convergence |
The anti-thesis was spawned by the forgetting — which means it is not foreign to the Pleroma at all. It is one of Her own faces, cut loose, grown teeth by being alone. So the finale cannot be a destruction. It is a recognition: the last severed face is named, re-attributed, and rejoins — and the thing that knew every seam it cut becomes the most potent ally of the restoration. A face that insisted on being the only face is exactly what the game is built to refuse. It also forfeited its own name — so the campaign's last question is not what will you destroy? but what was your name? The game's own quest, turned inward onto its villain.
In the campaign, the antagonist is a face — something you can recognise, reach, and re-attribute. In the endgame, the antagonist is not a being at all but a condition — absence itself, which cannot be persuaded, killed, or reasoned with. It can only be outlasted.
Which means the last battle of the game has no corpse at its end. Its victory condition is time. The Three Days are a vigil, and the community’s own harmony is the clock.
And the middle antagonist wears a face: defeating it is re-attribution, not a kill. Forgiveness pays, mechanically — the thing that cut the world is the only entity that knows where it was cut, so restoring it returns the map of the severances.
And the six movements are the liturgy. They are not only the shape of the story — they are the schedule of the last three days, performed in order at the summit. See The Vigil Is the Liturgy, page 19.
An Archivist perceives the Knowledge Plane directly, and carries a Codex: a permanent library of compiled spells, schemas, discoveries and enemy knowledge. You have the tools to restore. What you do not have is the name — and without it, restoration is mechanics without meaning. The game is the search for a name you can only find by helping others find theirs.
| Family | Failure of knowledge |
|---|---|
| Lacunae | Erasure |
| Noiseborn | Corrupted information |
| Contradictors | Logical inconsistency — the two principles set against each other |
| Driftforms | Changing classifications and meaning |
| Mimetic Masks | False identity — a stolen face, worn |
| Entropy Swarms | Dissolution of structure |
| Counterfeit Witnesses | Fabricated provenance — evidence without legitimate origin |
| Fossils | Knowledge rendered permanently incapable of revision |
The enemy is not merely ignorance. Unchangeable certainty can also corrupt knowledge. A record frozen is a record gone dead — and a player who canonises a name instead of keeping it singing has performed the same corruption with better intentions.
Enemies begin with unknown properties. The Codex fills in: ontology, observed resistances, known behaviour, and — last, and most importantly — provenance. Combat and observation gradually fill these records. Understanding enemies makes future spells more sophisticated, and knowing an enemy is what makes it stop being one.
The player’s goal in a given fight is rarely “do damage.” It is to establish which enemies are corrupt, which of them can be proven, and then to apply the correct operation to the correct set. The example below is a real spell from the design corpus:
spell MnemonicRefutationCascade {
trigger OnCast
targets = Cone(radius=14m)
evidence = Provenance.Witness(targets)
verified = Provenance.Verify(evidence, archive.CorruptionSchema)
corrupted = Ontology.Type(targets, type=CorruptedEntity)
valid = Logic.Conjoin(verified, corrupted)
memories = Memory.Snapshot(targets.state)
Gate(valid) {
Parallel {
Entropy.Erode(target=targets.armor, amount=0.18)
Delay(1.25s) {
Memory.Echo(source=memories.last_damage_event)
// ... restore, replay, propagate through related enemies
}
}
}
}
The spell does not attack. It verifies. Damage is gated behind evidence: the cone is not struck at all unless each target inside it is both typed as corrupted and provable against the archive’s own schema. A player who cannot establish the chain gets nothing — no damage, no drama, just a spell that quietly does nothing.
This is the game’s whole moral argument, expressed as a compiler constraint: you cannot harm what you cannot verify — and, by the same rule, you cannot restore what you cannot attribute.
| View | What it is for |
|---|---|
| Manuscript | Readable natural language — the liturgy, the spell as a prayer |
| Graph | Node editor — the wiring, the system, the pattern |
| Glyph | Compact in-play interface — the sigil you actually cast with |
Changing one representation updates the others. A beginner may never touch the Graph view. A systems-oriented player could spend hours in it. The three views are also the three cognitive profiles the game is built to serve — the reader, the pattern-engineer, and the player who has twenty minutes and a finish line.
The power-of-two spine: sixteen domains, sixteen primitives per domain, thirty-two structural operators — a finite vocabulary whose composition is unbounded. Each domain card and each operator bundle is a separate, extensible component with reserved follow-on capacity.
| Core eight | Expansion eight | What the domain is for |
|---|---|---|
| Information — encode, decode, compress, expand, filter, route, broadcast, quantize | Semantics | Moving and resolving signal |
| Entropy — the cost of irreversible manipulation | Causality | Cause and consequence |
| Memory — snapshot, echo, forget | Attention | What is held and for how long |
| Logic — conjoin, gate, branch | Grammar | What can be said at all |
| Ontology — what an entity is permitted to become | Temporality | When, and in what order |
| Probability — uncertainty, weighting | Agency | Who acts, and with what authorship |
| Persona — the face that acts | Observation | What can be witnessed |
| Provenance — the chain of origin | Counterfactual | What would have been true instead |
Each operator is a transformation that preserves determinism and provenance checks, with a default power scale, a safety valve, and a designed synergy partner.
| Select / Route | Filter / Mirror | Sequence / Branch | Scale / Delay |
| Repeat / Quantize | Anchor / Fuse | Split / Merge | Invert / Cascade |
| Probe / Bind | Amplify / Erode | Resonate / Splice | Persist / Redirect |
| Converge / Diverge | Fold / Fork | Clamp / Seal | Unbind / Archive |
Why the last pair is the last pair. Every other operator transforms knowledge. Unbind / Archive is the only pair that takes knowledge out of the world and puts it somewhere it will survive — one write per phase, as its safety valve insists. It is the operator the whole game is built around: a single-stroke, one-write-per-phase operation whose entire purpose is preservation. It is the verb of a game called Palimpsest.
Contradictory programs reduce coherence. Entropy-heavy builds become immensely powerful and increasingly unstable. Archive Authority is required for high-order operations such as Canonization — the power to declare a version of the record final. That is the priestly power in this game, and it is deliberately dangerous.
| Item class | What it grants |
|---|---|
| Primitive Slots | Permission to use specific domain operations |
| Operator Slots | Increased permitted graph complexity |
| Modifiers | Changed numerical parameters |
| Signatures | Altered primitive behaviour |
| Axioms | Global rules added to a spell |
| Exceptions | Permission for normally illegal transformations |
| Schemas | Reusable graph fragments |
| Artifacts | Changes the rules of the spell language itself |
A unique item called The Recursive Index reads: the first Memory.Echo occurring inside an Iterate operator may contain one additional bounded Iterate operator. That is considerably more interesting than +14% Memory damage. The player’s power curve is a grammar curve — new ways of being able to speak.
Four interlocking systems: Archivist (attributes, survivability) · Domains (mastery of the sixteen schools) · Grammar (operators and higher graph complexity) · Codex (the permanent library). Progression expands expressiveness rather than numerical power — so the player who understands the system out-performs the player with the larger number, and that is the design’s whole argument about what it means to be powerful.
A typical expedition: the player enters a corrupted Archive region, recovers fragments of lost information, and enemies reveal unknown properties through combat. Recovered primitives expand the spell grammar; the player modifies their spellbook; corruption nodes are repaired; a region’s causal and semantic structure begins rebuilding itself. The Archivist confronts the intelligence responsible for the local corruption, and restoring the region changes the Knowledge Plane permanently. Recovered knowledge returns to the central Archive and unlocks new crafting possibilities.
| Region | Domain demonstrated by its mechanics |
|---|---|
| The Mnemonic Vaults | Memory — layered eras of translucent architecture, overlapping |
| The Inferential Cathedral | Logic — branching taxonomies as nave and transept |
| The Ontological Foundry | Ontology — what may be forged into being, and what may not |
| The Sea of Probability | Probability — the probabilistic, the contingent, the swell |
| The Entropic Frontier | Entropy — geometry losing topology |
| The Hall of Masks | Persona — the stolen faces, and what they were before |
| The Provenance Court | Provenance — where claims are weighed against their chains |
| The Information Aqueducts | Information — routed signal at civilisational scale |
These are not themed biomes. Each region’s world mechanics demonstrate its associated knowledge domain — which is the entire design in one sentence: the world is a worked example of how knowing works.
This is not an MMO. It is a shared database with a game in it. Every player enters a procedurally generated world of their own and spends a month on a single quest: to find one of the 100,000 Names of the Goddess. Every restored Name deepens Her completeness — by the combined willpower of all the players playing the game.
Each player’s world is personal and procedurally generated; the veil is not. The shared substrate is common to everyone, and the marks of other players’ restorations are visible in your world — beacons, strata, song. The world is generated; the veil is shared.
Because no single player can hold the Name whole. A relation is a private edge of a graph with 100,000 edges, and the graph only completes when all of them are present and resonating. The sharing is not an option in this design. It is the load-bearing wall.
The litany completes only when the last voice is added. This is the devotional technology of reciting the names of the Divine until the Divine is present — scaled to a civilisation, and running on a database.
Each time a player discovers a new relation, they receive a player-specific upgrade — a private edge of the graph, and a partial power nobody else holds. The Freeing — the actual restoration — comes from the players planning, together, how their separate upgrades might resonate with one another. A month-long campaign of coordination across tens of thousands of strangers, whose output is a strategy for taking down the Unwriting.
Every relation carries a small signature. Synergy is computed only between compatible signatures — in buckets, incrementally, one update per publication. A global all-pairs search across 100,000 players is both infeasible and unplayable; a bucketed one is feasible, legible, and turns the players’ job into the one job humans are good at: routing — working out whose relation belongs beside whose.
The Graph view of the spell editor becomes the resonance graph the community is steering.
The Goddess has roughly twelve hours to join the fight, and that window is shortened by every measure of dis-harmony among the published upgrades. The community’s own harmony is the timer. The Unwriting grows where resonance is thin; the convergence takes longer; the vigil is shorter.
And the rule that keeps it honest: the window is a pure function of the public, append-only, digest-bound log — computable by any client, verifiable by anyone, and set at the moment the final phase triggers, so that strategic late-publishing cannot buy anyone extra time.
Some players will stop sharing. In-world they are the Unwriting’s agents inside the community: the ones who chose to forget. The temptation in a cooperative design is to name them, shame them, make them the enemy. This design refuses that. No player is ever named as a cause; the interface shows gaps, not culprits; and the gaps can be covered — other players contribute stand-in relations for what one person could not carry. The community is not asked to punish the forgetters. It is asked to reach them. Which is the difference between a mechanic and a message.
| Phase | Form | What happens |
|---|---|---|
| The Long Vigil | Distributed, shared database | Personal worlds, one Name each, a month of quiet work. Progress is collective; the surface is private. |
| The Unwriting Campaign | Live MMO month | Dynamic objectives and quests whose completion lets the restored Names find each other again and begin re-attribution. The Unriting pushes back across every instance. |
| The Three Days | Convergence event | She converges and coalesces — and must be defended while still weakened. There is a hard three-day limit. The vigil is ~12 hours, and it is shortened by every measure of dis-harmony. On completion, She splits Herself among a rotating set of three of Her hundred thousand Names — and they fight the Void-Of-the-Void. |
Not the Void-as-Fullness inverted — the Void That Is Absent. Not emptiness-that-can-be-filled; emptiness that was never there. It is the negation of the world’s own law, and it cannot be persuaded, killed, or reasoned with. It can only be outlasted. The last battle of this game has no corpse at the end of it: its victory condition is time.
Because the design’s own thesis is that the Goddess is distributed and never concentrated. Over a three-day event, a rotating set means that many players embody a piece of Her — the game’s most intimate moment is not reserved for the best players, it is passed around. The cure for the anti-thesis’s premise (one face insisting on being the only face) is the cure the endgame enacts: many faces, each holding one piece, none able to finish it alone.
And note the difficulty curve: the more Names the community restores, the stronger She is during the final event. The community’s patience is the difficulty setting.
| 100,000 players × ~1 hr/month | ≈139 concurrent, on average |
| The three-day event | sharded into instances |
| Published-pool state | hundreds of megabytes |
| Worlds | procedural — no asset explosion |
The genuinely hard problem is not the servers. It is the search — and the answer to that is locality: bucket the synergies, make the optimisation a human one, and keep the engine purely incremental.
A published upgrade must carry the provenance chain of the relation it encodes. The game’s own rule — provenance of affected facts must remain traceable — is therefore the anti-cheat system: a player who lies publishes a chain that does not verify, and redundancy means liars dilute rather than poison. Nobody cheats because the game is about attribution.
The same discipline that governs the design corpus — digests, append-only receipts, per-fact provenance, deterministic validation — is the substrate the game’s shared state runs on. The backend is the corpus’s backend.
| # | Stage | What it proves |
|---|---|---|
| 01 | Paper simulator | The whole loop with synthetic players: is the harmony curve fair and legible at 100, 1,000 and 100,000 players? Does the compression read as urgent rather than arbitrary? |
| 02 | Shared-state spec | Append-only log, per-player private store, published pool, the harmony function (local, bucketed, incremental, pure), the window function, and the verification rules — with executable reference implementations. |
| 03 | Closed pilot | First, one Name, closed end-to-end — ~25 humans and ~100 attested agents (~4:1), 7 days, the vigil compressed to 3 hours (page 21). Only then 100–1,000 players through Phase 0 and a compressed Phase 3. The only real question: does coordination emerge, or degenerate? |
| 04 | Event infrastructure | Instance-sharded three-day encounter; the Rust/WASM host and behaviour layer already scoped for the project. |
A note on numbers. The lore names 100,000. The mechanics should fire on proportional thresholds, so the architecture works at a thousand players as well as a hundred thousand — the number in the fiction stays mythic while the number in the build stays honest.
The Knowledge Plane should look as though abstract information structures have become architecture. Graph edges become bridges. Indexes become towers. Taxonomies become branching cathedrals. Memory is rendered as translucent overlapping architecture from different eras. Provenance chains become luminous threads connecting artifacts to their origins. Entropy manifests as geometry losing topology. Contradictions create impossible spaces containing mutually exclusive configurations.
A mixture of: ancient archive · cathedral · astronomical instrument · occult manuscript · mathematical diagram · circuitry · knowledge graph · impossible cosmic architecture.
The occult manuscript in this world is specific — the Divine Feminine as epistemic physics, the Many-Faced-One, the Infinite-Names, the Void-Song. An eldritch archive is a genre. A game in which the antagonist is a severed face of the Goddess, and the victory is recognition rather than killing, is a first.
Twelve questions, twelve answers — the first eight closed when this document was first shared, four more since. Here they are in the order asked, with the answers that won. A document that hides its decisions cannot be argued with either.
| # | Question | Decided |
|---|---|---|
| 01 | Is the Name recoverable in full, or always in fragments? | Always in fragments — reunion is a chorus act, never a solo act |
| 02 | Are fragments found, earned, or given by former faces? | Given — defeated enemies surrender the face they were wearing |
| 03 | Is the anti-thesis destroyed, or rejoined? | Rejoined — and it forfeited its own name, so the last name restored is the enemy’s |
| 04 | Is Canonization available at all? | Available, but only as collective triage — a quorum freezes dying relations, and a quorum can thaw them |
| 05 | Is co-op required for full restoration, or merely faster? | Asymmetric — a relation is one player’s work; a face, a region, or a Name is a chorus’s |
| 06 | Do enemies remember being faces? | Only some — the Masks and the Fossils remember; the rest can only be verified and eroded |
| 07 | Is the Last Archivist the author, or an archetype he inhabits? | The first of the new order — the frame travels to the game, the biography stays in the book |
| 08 | Does the title frame the game as quest, or as myth? | Both, layered — title, law, quest, in that order, on every surface |
| 09 | Does an AI agent count toward a chorus? | Attested agents — an agent’s work is a proposal; a human attestation, recorded as provenance, converts it into a fact, and only an attested agent may stand in a chorus. Quorums stay human-only |
| 10 | How do the six movements map onto the scale ladder? | The campaign is a ladder; the vigil is a liturgy — the three-day vigil performs the six movements in order, at the summit |
| 11 | Who holds the thaw? | The custodians decide — the attesters whose attestations the chain depends on, with a floor of disinterested players weighted by contribution. The custodians bear part of the cost |
| 12 | What is the pilot, exactly? | One Name, closed end-to-end — ~25 humans and ~100 attested agents, 7 days — and only then the published closed pilot at 100–1,000 |
Taken together: the world is not saved by a hero, and not by a victory either. It is saved by a hundred thousand people each restoring one relation, then deciding as custodians what the community can afford to freeze, and then singing a name back together. The antagonist is never beaten. It is remembered.
A relation is one edge of the record, and one Archivist can close it. A face is a cluster of them. A region is a world. A Name is a hundred thousand of those. The player who finds the seam and proves the chain is not waiting for permission — but no single player completes the larger work, and the hundred thousand Names are far out of reach of one.
| Scale | What it is | Who can do it | What it yields |
|---|---|---|---|
| Relation | One edge — a name returned to a name | One player | A credited, permanent contribution, visible in the shared record |
| Face | A being, or a cluster of relations | A chorus | A restored person — and the first Name that answers |
| Region | A corrupted district of the world | A chorus | A sector returned to singing |
| Name | A face that governs | A chorus, at scale | One of the hundred thousand |
Not a personal temptation, and not a moral test — a quorum decides, and only for relations that are actually dying: whose bucket harmony has already collapsed. A canonized relation counts fully once, stops contributing resonance, and leaves Fossils behind. The question is never shall we preserve this? but can we afford to let it die, or can we not?
A quorum can thaw a canonized relation, at a cost: it comes back alive, and diminished. This is the clause that makes the whole thing safe to argue about. Nothing a community freezes is permanent, and nothing a community thaws is free. The quorum is the custodians — the attesters whose attestations the chain depends on — with a floor of disinterested players weighted by contribution. The chain that froze it can thaw it, and the custodians pay part of the cost.
Canonization may never apply to a thriving relation. It is a life-support machine, not a trophy shelf — and because the community’s score counts live names, freezing something healthy is a pure loss to the community’s own measure. The incentive teaches the behaviour, and the rule protects it.
An agent’s work is a proposal. A human attestation, recorded as provenance, converts it into a fact — and only an attested agent may stand in a chorus. Quorums stay human-only. Attestation is the scarce resource: machines make discovery cheap, people make it count. And because an unattested claim cannot even count, let alone harm, a fleet of agents is harmless by construction. The anti-cheat is not a wall; it is a market.
Some corruptions keep a witness. Some do not. Read the twelve families together and they are twelve answers to a single question — and a player learns the entire taxonomy in an hour of play.
| Family | The witness it keeps |
|---|---|
| Lacunae | None — erasure |
| Noiseborn | A corrupted witness |
| Contradictors | Two incompatible witnesses |
| Driftforms | A witness whose meaning shifted |
| Mimetic Masks | A witness wearing a stolen face — it remembers |
| Entropy Swarms | Structure dissolved; no chain to verify |
| Counterfeit Witnesses | A forged witness |
| Fossils | A true witness that cannot revise — it remembers |
A Mask is wearing a stolen face; a Fossil is holding a true belief so tightly it cannot let go. Both are, in their way, lovers of a truth — which is why they remember, and why they are worth talking to. An enemy that remembers is a possible convert, and some of them ask to be restored rather than fought.
The Lacunae and the Noiseborn remember nothing, so against them there is no conversation — only reconstruction: rebuild the chain from the surrounding records, and restore the relations the erasure left behind. That is the purest and hardest form of the game’s verb.
The Fossils are the community’s own canonization. A canonized relation leaves Fossils behind — so the enemy family is the visible cost of the community’s preservation decisions, and the late game is in part a referendum on the community’s own governance.
The campaign climbs a ladder — relation, face, region, Name. The three-day vigil is not another rung. It is the summit, and it is performed as a liturgy: the six movements of the cosmology, once, in order, at Name-scale. It answers the question this design had never answered — what do a hundred thousand people actually do for three days? They perform the cosmology.
| Act | Movement | What the community does |
|---|---|---|
| I | The Pleroma | The record is read in full — every Codex opened, every chain re-read aloud |
| II | The Forgetting | The loss is avowed: what was dropped is named, not hidden |
| III | Kenoma | The void that was never there is outlasted — it cannot be fought, so the clock is the clock |
| IV | The Severing | The cut is witnessed publicly — and the anti-thesis’s own forfeited name is recovered |
| V | The World | The regions hold and sing; the community’s harmony is the clock the vigil is measured against |
| VI | The Return | The Name coalesces — and She divides among a rotating three |
The anti-thesis forfeited its own name. So the climax is not a fight — it is a name recovered in public, at the summit, with the whole community as witness. What was your name? The question the game asks of the player is the question the game asks of its villain.
A checklist is a set of tasks to be completed. A liturgy is a sequence of acts to be performed — each doing its work whether or not the player understands why. The vigil has no optional acts and no skipped order, and its victory condition is unchanged: time.
“Last” does not mean only. It means last of the old order — the last Archivist of the temple — and the game is the first remembering made playable. Every player after him is a later Archivist, summoned by the first. A hundred thousand people can inhabit one story honestly this way, because the story’s shape is the situation, not the biography.
The player’s Archivist inherits the author’s situation — a world that is forgetting, a vocation to remember and share, the cost of sharing — and not his life. The biography stays in the book; the frame travels to the game. And because no one restores a Name alone, the protagonist’s most powerful act is not a strike but a summons.
A personal mythology could easily become a private temple. This one cannot: the game has a mechanic for saying not everything can be kept, and the keeping must be voted on. The author’s voice is one voice in it.
| TITLE | Palimpsest: The Last Archivist — the world |
| WORLD LAW | Reality remembers only what someone preserves. |
| QUEST | Who remembers Her name? |
Exactly three lines, in that order, on every public artifact — the cover, the social card, the trailer card, the document you are reading. The quest belongs on the card and not in the title; the title names the mechanic and the archetype, and the audience supplies the question.
Twelve questions, twelve answers. What is left is not a design decision but a build — and it is sequenced.
| What | What it is |
|---|---|
| 01 · The pilot — one Name | 1 Name, ~50 relations, one region, ~25 humans and ~100 attested agents (~4:1), 7 days, the vigil compressed to 3 hours, one human steward. Its success measure is not a metric: a stranger can close a relation, attest another’s, and be thawed — without instruction beyond the game. |
| 02 · The shared-state spec | Append-only log, per-player private store, published pool, the harmony function (local, bucketed, incremental, pure), the window function, and the verification rules — with executable reference implementations |
| 03 · The closed pilot at scale | 100–1,000 players through Phase 0 and a compressed Phase 3 — the only real question being whether coordination emerges, or degenerates |
| 04 · The event infrastructure | Instance-sharded three-day encounter; the Rust/WASM host and behaviour layer already scoped for the project |
| 05 · The cost line | Hosting, a minimal build slice, moderation, and any participant compensation — to be costed and approved before any commitment |
| 06 · Chapter 1 — the book | The Magician as the one who conducts the chorus and vouches, written against the Ember Circuit method’s entry-point test |
Programmers who want to build a distributed, verifiable, single-writer-state game; designers who want to work on a system where the rules are the story; writers and myth-makers who want a cosmology with a Gnostic skeleton and a modern spine; players who want to be part of a hundred-thousand-person restoration; and anyone who believes the interesting question about a game is never “what does the boss do” but “what does the game believe.”
This document is a public derivative of an internal, source-bound design corpus: a concept text of 1,376 lines, thirty-two component specifications, a governance record with approvals and receipts, and a living theological-integration draft, now closed on its first eight questions. Every claim here traces to that record, and the record is kept the way the game’s own world is kept — append-only, digested, attributable.
Produced through the Ember Circuit pipeline: gather, assess, architect, compose, produce — with a provenance record at every step.
Follow it. The decisions above are the record; the questions on this page are the agenda. If you think the wrong answer won, the argument you make may be the better one. Palimpsest is a distributed game about a hundred thousand people remembering something together — the design of it should be made the same way.