Product intent. discord-rpg is a Discord RPG server bot built from scratch that turns a roleplay community's creative output โ original characters, faction and guild applications, and server lore โ into a durable, staff-governed archive. It is configurable by server admins, and it delivers an inviting, polished interactive experience through Discord slash commands, embeds, buttons, select menus, and modals where appropriate.
Audience. The bot serves four accepted human roles inside a Discord roleplay server: Server Admin (owns configuration and the lore source), Staff Reviewer (reviews original character submissions and runs roleplay support), Faction/Guild Leader (decides applications for their own group), and Player (submits characters, applies to factions and guilds, discovers lore, and uses roleplay support). A companion first-party web surface presents the archive, the faction route map, the lore provenance view, and the review queue with the ceremonial, museum-grade identity described in the creative direction.
Scope of this document. This SRD specifies the current, accepted product: the four core feature areas, secure token configuration, persistence, permission checks, error handling, and setup documentation. It also specifies the identity and access boundaries required to make those journeys executable, and it records the explicit constraint that no code is reused or migrated from the existing Discord Chatbot project.
discord-rpg is delivered as a Discord bot (slash commands, embeds, buttons, select menus, modals) backed by a persistent service, plus a first-party web surface that renders the archive, faction route map, lore provenance, and review queue. The bot is the invisible archivist of a shared world: it receives player submissions and applications, routes them privately to the correct reviewers, records decisions, and communicates outcomes back to applicants.
Actors.
Accepted behavior. (1) OC submissions via an interactive form, posted to an admin-configurable review channel, with accept/decline/comment and applicant communication. (2) Faction and guild applications with an interactive picker offering exactly the seven configured choices, decided by the relevant leaders, with per-group configurable workflow. (3) An RPG lore assistant drawing on an editable, staff-managed source that clearly distinguishes official lore from generated suggestions and never invents canon. (4) Roleplay support for staff and players: scene prompts, character hooks, event ideas, and staff utilities.
Ownership and privacy. Review actions are restricted; private submissions are never exposed publicly beyond the configured review channel and applicant communications. The Discord bot token is configured securely and never appears in public application content.
Narrow exclusions. No code is reused or migrated from the existing Discord Chatbot project. No photographic or illustrated character art is used in the web surface; the generative canvas is the only imagery. No blue, indigo, or violet appears in UI chrome.
Delivery ownership. The product is delivered as a Discord bot that owns the interactive workflows inside Discord (slash commands, embeds, buttons, select menus, modals) and a first-party web surface that owns the archive, faction route map, lore provenance view, and review queue. The bot's token is a deployment secret owned by the Server Admin and the deployment environment; it is never rendered as public application content.
Identity and access. The web surface establishes application-owned identity so that a Player's submissions and applications, a Staff Reviewer's review history, a Faction/Guild Leader's group decisions, and a Server Admin's configuration remain bound to the correct participant and resumable across visits. First use is anonymous: the Landing page is reachable without identity, and Sign Up establishes identity; Login verifies returning participants. Protected destinations (OC Submission, OC Review, OC Outcomes, Faction Apply, Faction Review, Bot Configuration, Lore Management, Lore Assistant, Roleplay Tools) require established identity. Inside Discord, the bot enforces permission checks so that only the correct reviewers can act on a given record.
Current vs. future. Everything specified in this document is current. No future-horizon features are accepted; nothing in this document should be read as committing to adjacent account-management, moderation, or analytics capabilities.
No reference directive in this project declares content_source; therefore no source content inventory is included.
DISCORDยทRPG in Instrument Serif, flush left on the canvas baseline. A single line of Space Grotesk in muted slate reading live archive counts (1,204 characters ยท 318 applications ยท 96 lore entries), numbers in bone, labels in muted. A thin aquamarine rule runs the full viewport width at the height where the particle field is densest โ the only horizontal line on the screen.Begin your character, pinned to the left margin.Read the lore to the right of the primary pill; navigation into Sign Up and Login.01 ARCHIVE, 02 FACTIONS, 03 LORE, 04 REVIEW); seven full-width colour-coded faction bands, each with sigil, name, and current applicant count; sticky context rail (current faction, active review queue count, provenance legend).0 characters ยท 0 applications ยท 0 lore entries with the same typographic treatment. Success: counts render live and the canvas drifts continuously. Error: if counts cannot be fetched, the count line renders a muted archive unavailable label and the canvas renders one static frame; the primary action remains available. Recovery: counts retry on next visit; no user action required.No submissions awaiting review in muted slate. Success: the card's top edge pulses ember for 400ms and the record is sealed with the decision and reviewer identity. Error: a failed decision leaves the card unchanged and surfaces an inline retry. Recovery: retry re-applies the same decision without duplicating the record.No decisions yet with a link to OC Submission. Success: decision and comments render with the archive ID and timestamp. Error: unavailable outcomes render an inline retry. Recovery: retry reloads the outcome list.No applications awaiting your decision in muted slate. Success: the card's top edge pulses ember for 400ms and the record is sealed with the decision and leader identity. Error: a failed decision leaves the card unchanged and surfaces an inline retry. Recovery: retry re-applies the same decision without duplicating the record.configured. Error: invalid channel or workflow settings render inline messages and preserve prior values; token errors never echo the value. Recovery: correct and re-save; prior configuration remains in effect until a successful save.No official lore yet with a prompt to create the first entry. Success: the entry persists and appears in the official source used by the assistant. Error: save failure preserves the draft and surfaces an inline retry. Recovery: retry saves the same draft.OFFICIAL / GENERATED. Nothing generated is ever shown without its official source beside it.No official lore matches that question with a link to the official source. Success: the official excerpt and the labelled generated restatement render side by side with the provenance diagram. Error: retrieval failure renders an inline retry and never substitutes generated content for official lore. Recovery: retry the question; the official source remains authoritative.Nothing drawn yet with a prompt to generate. Success: the prompt, hook, or event idea renders with its author and timestamp. Error: generation failure renders an inline retry. Recovery: retry regenerates without losing prior outputs.Each requirement is stated as a story point with provenance, lifecycle facts, and observable acceptance.
FR-1 โ Build from scratch. As a Server Admin, I should run a Discord RPG server bot built from scratch, so that the server's roleplay archive is owned by this product alone.
FR-2 โ Admin configurability. As a Server Admin, I should configure the bot for my server, so that its workflows match how my community runs.
FR-3 โ Polished interactive experience. As a Player, I should interact with the bot through slash commands, embeds, buttons, select menus, and modals, so that submissions, applications, lore, and roleplay support feel inviting and polished.
FR-4 โ OC submission form. As a Player, I should submit an original character through an interactive form, so that my character enters the server's archive.
FR-5 โ Review-channel routing. As a Server Admin, I should set the review channel where OC submissions are posted, so that review happens where my staff work.
FR-6 โ Staff decisions on OC submissions. As a Staff Reviewer, I should accept, decline, or comment on an OC submission, so that the applicant receives a clear decision and feedback.
FR-7 โ Applicant receipt of outcomes. As a Player, I should receive the outcome and comments on my OC submission privately, so that I know the decision and what to improve.
FR-8 โ Faction and guild application requirement. As a Player, I should apply to a faction or guild through the bot, so that joining requires an application.
FR-9 โ Exact faction picker choices. As a Player, I should choose from exactly the configured faction and guild choices, so that I apply to the right group.
FR-10 โ Leader decisions on applications. As a Faction/Guild Leader, I should accept or decline applications for my own faction or guild, so that my group's applicants receive decisions.
FR-11 โ Per-group workflow configuration. As a Server Admin, I should configure the faction/guild application workflow per group, so that each group runs its own process.
FR-12 โ Editable staff-managed lore source. As a Server Admin, I should manage the official lore source, so that the assistant answers from lore my staff control.
FR-13 โ Lore discovery. As a Player, I should ask the lore assistant about server lore, so that I can discover what is established.
FR-14 โ Official vs. generated distinction. As a Player, I should see official lore clearly distinguished from generated suggestions, so that I never mistake a suggestion for canon.
OFFICIAL / GENERATED) with a provenance diagram; failure/recovery โ if no official source matches, the assistant says so rather than generating canon; continuation โ the Player relies on the official excerpt.FR-15 โ Roleplay support. As a Player, I should draw scene prompts, character hooks, and event ideas, so that I can start and sustain scenes.
FR-16 โ Staff roleplay utilities. As a Staff Reviewer, I should use staff utilities alongside roleplay support, so that I can run scenes and events for the server.
FR-17 โ Secure bot token configuration. As a Server Admin, I should configure the Discord bot token securely, so that the credential is never exposed.
FR-18 โ Persistence. As a Server Admin, I should have submissions, applications, and configuration persisted, so that the archive survives restarts.
FR-19 โ Permission checks. As a Server Admin, I should have permission checks enforced, so that only the right people act on the right records.
FR-20 โ Sensible error handling. As a Player, I should see sensible errors when something fails, so that I can recover without losing work.
FR-21 โ Setup documentation. As a Server Admin, I should follow setup documentation, so that I can install, configure, and run the bot.
FR-22 โ Privacy of review and applicant communication. As a Player, I should have my submissions kept private, so that they are not exposed publicly.
FR-23 โ Self-service enrollment. As a Player, I should establish my own identity, so that I can begin using the bot's protected workflows.
FR-24 โ Returning verification. As a returning participant, I should verify my identity, so that my submissions, applications, reviews, and configuration remain bound to me.
FR-25 โ Server-admin permission for configuration and token. As a Server Admin, I should be the only one who can change configuration and the bot token, so that server settings stay under my control.
FR-26 โ Reviewer permission for restricted actions. As a Staff Reviewer or Faction/Guild Leader, I should act only on records I am responsible for, so that review stays private and correct.
Product context. The Server Admin owns the bot's configuration for one Discord server. They are the person who decides where OC submissions land, how each faction and guild runs its own application workflow, what counts as official lore, and how the bot token is handled. They are accountable for the server's privacy posture.
Primary goal. The server's submission, application, and lore workflows run with the settings they chose, and the bot token stays secret.
Distinct accepted responsibilities. Setting the OC review channel (FR-5); configuring each of the seven faction/guild application workflows independently (FR-11); managing the editable staff-managed lore source (FR-12); configuring the Discord bot token securely (FR-17); relying on persistence for submissions, applications, and configuration (FR-18); enforcing permission checks (FR-19); following setup documentation (FR-21).
Relevant inputs and decisions. Which channel receives OC submissions; what each group's workflow requires; which lore entries are official; the bot token value, entered once and never echoed.
Interactions with other participants. The Server Admin's configuration determines what Staff Reviewers see in OC Review and what Faction/Guild Leaders see in Faction Review. The lore source they manage is what the Lore Assistant answers from, so their editorial decisions directly shape what Players read as official.
Observable success. Saved settings take effect for the server; the token status reads configured without the value ever being shown; the lore source the assistant cites is the one the admin last saved.
Product context. The Staff Reviewer works the OC queue in the configured review channel and also runs roleplay support for the server. They are the server's editorial gate for original characters and a source of scene and event material.
Primary goal. Applicants receive clear decisions and feedback, and review actions stay private to the review channel and applicant communications.
Distinct accepted responsibilities. Accepting, declining, or commenting on OC submissions (FR-6); using staff roleplay utilities (FR-16); contributing to the staff-managed lore source (FR-12); acting only on records they are responsible for (FR-26).
Relevant inputs and decisions. The submission content and its archive ID; whether the character fits the server; what comment to send the applicant; which scene prompt, hook, or event idea to draw.
Interactions with other participants. The Staff Reviewer acts on what Players submitted and what the Server Admin routed to the review channel. Their decision and comments are what the Player reads in OC Outcomes. Their lore edits change what the Lore Assistant presents as official.
Observable success. Each reviewed card is sealed with a decision and reviewer identity, the applicant receives the decision and comments privately, and no submission content appears outside the configured review channel and applicant communications.
Product context. The Faction/Guild Leader handles applications for one of the seven groups โ\x20\xf0\x9f\x93\x9a The Eternal Archive,\x20\xf0\x9f\x8c\x91 The Umbral Covenant,\x20\xf0\x9f\x97\xa1๏ธ The Iron Vanguard,\x20\xf0\x9f\x94\xae The Arcane Conclave,\x20\xf0\x9f\x8f\xb9 The Verdant Wardens,\x20\xf0\x9f\xa7\xaa The Alchemical Circle, or the Adventurers Guild โ under the workflow the Server Admin configured for that group.
Primary goal. Their group's applicants get decisions under the group's own configuration.
Distinct accepted responsibilities. Accepting or declining applications for their own group (FR-10); acting only on records belonging to their group (FR-26).
Relevant inputs and decisions. The application content and its archive ID; the group's configured workflow; whether the applicant fits the group; what comment to send.
Interactions with other participants. The leader receives what Players submitted through Faction Apply and decides under the Server Admin's per-group configuration. Their decision and comments reach the applicant privately.
Observable success. Only their group's applications appear in their queue, each decision is sealed with their identity, and the applicant receives the outcome.
Product context. The Player is the creative participant: they submit original characters, apply to factions and guilds, ask the lore assistant about the world, and draw scene prompts and character hooks for play.
Primary goal. Their submissions and applications are resolved with feedback, and they can find lore while official lore stays clearly distinguished from generated suggestions.
Distinct accepted responsibilities. Submitting an original character through the interactive form (FR-4); receiving outcomes and comments privately (FR-7); applying to a faction or guild through the bot (FR-8); choosing from exactly the seven configured groups (FR-9); asking the lore assistant (FR-13); seeing official lore distinguished from generated suggestions (FR-14); drawing scene prompts, character hooks, and event ideas (FR-15); establishing identity (FR-23) and verifying on return (FR-24).
Relevant inputs and decisions. The character's details; which faction or guild to apply to; what to ask the lore assistant; which prompt or hook to use.
Interactions with other participants. The Player's submission is what the Staff Reviewer decides on; their application is what the Faction/Guild Leader decides on; the lore they read is what the Server Admin and Staff Reviewer published as official.
Observable success. Each submission and application carries an archive ID and a private outcome; lore answers show the official excerpt beside the labelled generated restatement; nothing they submitted appears publicly outside the configured review channel and their own communications.
configured.Begin your character.OFFICIAL, and the assistant's restatement in Space Grotesk on the dark ground on the right, labelled GENERATED, separated by a hard vertical rule. A thin-line provenance diagram shows Source โ Excerpt โ Assistant restatement.OFFICIAL column in future answers.The creative direction is authoritative for this section. Muse: Refik Anadol. Headline idea: data made physical โ the bot's own submissions rendered as a living archive.
Mode. Dark mode only.
Colour tokens (exact hex by role).
| Role | Hex | Use |
|---|---|---|
| Background | #07070C | Near-black ink ground for every surface |
| Surface | #11121B | Layered slate for embeds, cards, review panels |
| Text | #F2F0EA | Warm bone; 92% opacity for body, 100% for headings |
| Primary | #7CE3D4 | Luminous aquamarine; reserved for OFFICIAL states, accepted outcomes, generative flow lines |
| Accent | #FF6B3D | Hot ember; only for pending/attention states, decline markers, and the single call-to-action on each screen |
| Muted | #7A7F93 | Metadata, timestamps, IDs, provenance labels |
Colour rules. Never use blue or indigo anywhere. The only cool hue is the aquamarine primary, and it must always read as light, not as UI chrome colour. The generic indigo/blue-on-white SaaS template is forbidden.
Typography. Headings: Instrument Serif, weight 400 only, tight tracking -0.02em, sentence case for editorial headers, all-caps for micro-labels at 11px with +0.18em tracking. The serif never appears below 28px. Body and UI: Space Grotesk at 15โ16px with +0.01em tracking, tabular numerals for counters, IDs, timestamps, and vote tallies.
Type scale. 1.333 modular: 96 / 72 / 54 / 40 / 30 / 22 / 16 / 14 / 12. Display sizes clamp: hero headline clamp(40px, 9vw, 128px); section headlines clamp(28px, 4.5vw, 54px); card titles 22px; body 16px; micro-labels 11px.
Shape language. Full-bleed canvases with soft, organic boundaries; section transitions are long horizontal sweeps rather than hard rules. Cards use 20px radii with a 1px inner hairline at rgba(242,240,234,0.08) and no drop shadow โ depth comes from a faint inner glow at the top edge. Status chips are pill-shaped; data rows are ruled with 1px slate lines. Nothing is sharp-cornered except the vertical rule separating Official from Generated columns.
Spacing rhythm. A single wide column dominated by the generative canvas in the hero, then a two-column asymmetric grid: 8 of 12 columns for the archive stream, 4 columns for a sticky context rail showing the current faction, the active review queue count, and the provenance legend. Section boundaries are marked by a 1px full-bleed rule with a small numbered label at the left margin (01 ARCHIVE, 02 FACTIONS, 03 LORE, 04 REVIEW). The seven factions each get a colour-coded, full-width horizontal band rather than a card grid, so the picker reads as a route map, not a menu.
Imagery style. The generative canvas is the imagery. No stock photography, no clip art, no character illustrations. Secondary imagery is schematic: a thin-line provenance diagram (Source โ Excerpt โ Assistant restatement) and faction sigils drawn as pure geometric marks in each faction's band colour โ never emoji-as-art. The seven faction emoji exist only inside Discord-side copy.
Readable text and controls. Headlines, wordmarks, labels, numbers, cards' text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit, and no other element covers any part of them. Imagery, decoration, and motion may be cropped, bled off an edge, rotated, overlapped, or cut as the direction asks, as long as it covers no readable text or control. Moving and scrollable content may cross the viewport or container edge by design; with prefers-reduced-motion it stops and shows whole items, wrapping into rows or sitting in a horizontally scrollable row (overflow-x: auto).
The archive renders itself.
The public entry is a full-bleed near-black canvas occupying the first 78vh. A slow-drifting particle field condenses visibly toward the lower third; its density is driven by the real count of submissions, applications, and lore entries in the database. The wordmark DISCORDยทRPG is set in Instrument Serif at clamp(40px, 9vw, 128px), flush left, sitting on the canvas baseline โ not centred, not boxed. Directly beneath it, a single line of Space Grotesk at 16px in muted slate reads the live archive counts (1,204 characters ยท 318 applications ยท 96 lore entries), with the numbers in bone and the labels in muted. The primary action is one ember-outlined pill, Begin your character, pinned to the left margin, with a secondary ghost link Read the lore to its right. A thin aquamarine rule runs the full viewport width at the exact height where the particle field is densest, and it is the only horizontal line on the screen.
On scroll, the particle field collapses into a single 1px horizontal rule that becomes the section divider, so the hero's motion resolves into the page's structure. Faction selection is a full-width colour-coded band list โ seven bands, each with its sigil, name, and current applicant count โ and choosing a faction scrolls into that band's application form inline. Lore answers render as a two-column provenance block: the verbatim official excerpt in Instrument Serif on a lighter surface on the left, the assistant's restatement in Space Grotesk on the dark ground on the right, separated by a hard vertical rule and labelled OFFICIAL / GENERATED. Nothing generated is ever shown without its official source beside it. Every review card in the staff queue carries a numbered archive ID in tabular numerals at its top-right, and a 400ms ember pulse sweeps its top edge on accept or decline โ a small ceremonial mark that the record has been sealed.
No gradient blob, no centred stack, no blue button, no hover-lift cards, no rounded-corner glass panels with backdrop blur.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: webgl
Focal subject. A real-time particle field derived from the live count of submissions, applications, and lore entries โ the archive rendering itself.
Input โ transformation โ outcome thesis. As the participant scrolls from the hero into the archive, the particle field collapses into a single 1px horizontal rule that becomes the section divider; the hero's motion resolves into the page's structure. The field's density is driven by real archive counts, never random noise.
Motion vocabulary. Continuous slow generative drift in the hero canvas; scroll-linked morph from particle field to section rule; a single 400ms ember pulse along a review card's top edge on accept or decline. No bounce, no spring, no hover-lift.
Composed first frame. Near-black canvas, particle field condensing toward the lower third, DISCORDยทRPG flush left on the baseline, the live count line beneath it, the ember-outlined Begin your character pill pinned to the left margin, the ghost Read the lore link to its right, and one thin aquamarine rule at the field's densest height.
Reduced-motion state. With prefers-reduced-motion, the canvas renders one static frame and all reveals become instant; the section rule is present without the collapse animation, and the ember pulse is replaced by an immediate state change.
A single crafted real-time object: a luminous particle field whose density and condensation are driven by the live archive counts (characters, applications, lore entries). The scene shows the product's defining state โ a growing, searchable archive โ as a slow-drifting volume that condenses toward the lower third of the frame and, on scroll, collapses into the 1px section rule. The scene uses only the palette tokens (#07070C ground, #7CE3D4 flow lines, #FF6B3D attention, #F2F0EA bone, #7A7F93 muted) and renders one static frame under prefers-reduced-motion.
NFR-1 โ Secure token handling. The Discord bot token is configured securely and never rendered as public application content or echoed back to any participant. Provenance: explicit. Rationale: the token is a deployment credential; exposing it would compromise the bot.
NFR-2 โ Privacy of submissions and review. Review actions are restricted, and private submissions are not exposed publicly beyond the configured review channel and applicant communications. Provenance: explicit. Rationale: the server's creative work is private until its owner chooses otherwise.
NFR-3 โ Persistence durability. Submissions, applications, comments, decisions, configuration, and lore source data persist across restarts. Provenance: explicit. Rationale: the archive is the product's core value.
NFR-4 โ Permission enforcement. Permission checks are enforced on every restricted action: server-admin configuration and token changes require server-admin permission; OC review requires staff permission; faction/guild decisions are limited to the relevant group's leaders. Provenance: explicit (permission checks) and required_inference (the specific boundaries). Rationale: privacy and correctness depend on the right participant acting on the right record.
NFR-5 โ Error handling. Failures produce clear, non-technical messages with a retry path and never silently discard a submission, application, comment, decision, or configuration change. Provenance: explicit.
NFR-6 โ Setup documentation. Setup documentation covers installation, permissions, configuration, and workflow continuity. Provenance: explicit.
NFR-7 โ No code reuse. No code is reused or migrated from the existing Discord Chatbot project, and no such claim is made. Provenance: explicit.
NFR-8 โ Faction picker exactness. The faction picker offers exactly the seven configured choices and no others. Provenance: explicit.
NFR-9 โ Lore provenance integrity. The lore assistant clearly distinguishes official lore from generated suggestions and never invents canon; nothing generated is shown without its official source beside it. Provenance: explicit.
NFR-10 โ Readable text and controls. Headlines, wordmarks, labels, numbers, cards' text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, and no other element covers any part of them. Provenance: explicit (creative direction). Rationale: legibility is a hard constraint of the direction.
NFR-11 โ Reduced motion. With prefers-reduced-motion, the canvas renders one static frame and all reveals become instant. Provenance: explicit (creative direction).
NFR-12 โ Palette restriction. No blue, indigo, or violet appears in UI chrome, including focus rings and link colours. Provenance: explicit (creative direction).
discord.py (or an equivalent Python Discord library) implementing slash commands, embeds, buttons, select menus, and modals. [Default โ not specified by user][Default โ not specified by user][Default โ not specified by user][Default โ not specified by user][Default โ not specified by user][Default โ not specified by user]No source-specified technology choices exist beyond the Discord platform itself; the items above are labeled defaults and do not constitute product behavior.
Constraints (binding).
Assumptions (narrow, labeled).
[Assumption] The bot operates inside Discord servers where the Server Admin has the permissions needed to install and configure it.[Assumption] Application-owned identity is required so that a participant's submissions, applications, reviews, and configuration remain bound to them and resumable; this is a required_inference from the accepted durable workflows.[Assumption] The web surface and the Discord bot share the same persistence so that a submission made in Discord is visible in the web review queue and vice versa.[Assumption] Generated lore restatements are produced by a language model grounded strictly in the staff-managed official source; the source remains authoritative.[Assumption] The seven faction emoji are used only inside Discord-side copy and never as visual marks in the web interface.Explicit exclusions.
GENERATED and never presented as canon.
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.

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!