
01 Identity
Players, reviewers, faction leaders and server admins verify here before a private record is opened.
Protected destinations require an established session. Review queues and private submissions are never readable without one.
Credential record
UNVERIFIEDNo archive record yet? Create an identity to submit characters, apply to factions and reach the lore source.
Create an identity1,204characters318applications96lore entries
A verified session is the threshold to the archive. It restores your own submissions, applications and outcomes, and unlocks the tools your role governs inside the server.
Each participant sees only their own state. A submission reaches the configured review channel and the applicant it belongs to — review actions stay restricted, and nothing private is surfaced publicly.

The living archive
1,204 characters·318 applications·96 lore entries
The archive renders itself
Each original character, faction application and lore entry is kept as a durable, staff-governed record. The stream below is ruled data, not a feed of tiles: one line per entry, its archive ID in tabular numerals, and the decision that sealed it.
The route map
Every group keeps its own ledger. Choose a territory to open its application and carry your name into that faction’s record.
Official lore · provenance
The assistant restates what the staff-managed archive already records. The excerpt sits on the left surface and the restatement on the dark ground at its right, so the official voice is always present and always larger.
Official
“Before the first faction raised its banner, the Archive was already keeping the names of everyone who would later swear to one.”
Generated
The Archive predates every faction. It recorded the names of people before those people had chosen a banner, which is why the Archive is treated as the oldest institution in the world and why its ledger is never rewritten.
Restatement onlyofficial source: The Founding of the Archive
Provenance · Source → Excerpt → Assistant restatement
Private submissions and decisions are never displayed in a public archive preview. Staff and group leaders review records in their configured, permission-restricted queues; outcomes are communicated directly to each applicant.
A character, faction or guild application reaches the configured review channel.
The responsible staff reviewer or group leader decides, with an optional comment.
A 400ms ember pulse marks the record as sealed with the reviewer’s identity.
The outcome reaches only the applicant — never a public feed.
No comments yet. Be the first!