town atlas • lore system • structured memory
Town Atlas
This is the structured world bible for RPG Wednesday and related story material. Practical visitors can stop at the route links and leave. World-builders can use the atlas to keep guides, districts, factions, objects, and sessions retrievable without scattering the canon across flavor text.
The page is deliberately split: utility on one side, story substrate on the other. That makes the site easier for humans to design against and easier for external models to review without guessing which details are canon, which are route metadata, and which are just decorative atmosphere.
The page is also discussion-ready: each major block should be able to turn into a reply, a quote, a remix, or a playable scene within a few seconds.
Page job
Visitor use
Find the town memory you need without being forced through the rest of the site first.
Story use
Keep a civic archive where quests, prompts, guides, and recurring forces can stay stable enough to reuse.
Canonical status
Active. The atlas can grow, but it should stay indexed and separate from the practical route sorter.
Next action
Choose a district, then move to the guide or object that answers the current question fastest.
Discussion payload
Claim
Readable systems make promises easier to inspect.
Question
What kinds of promises need proof before trust?
Tension
Speed of posting versus durability of record.
Example
A proof card for a public offer.
Reply invite
What would you put on the first card?
Quote post
“A town is a memory system before it is a place.”
Reply ladder
Level 1
What is one object you would put in the Town Library?
Level 2
What kind of memory does your community fail to preserve?
Level 3
Is public proof care, control, or both?
Level 4
An artifact arrives at the library with no name. Who claims it, and why?
Town index
civic archive
Library
The practical learning interface for quests, guides, and portfolio artifacts. In story terms, it is the town's memory engine: the place where unstable material becomes inspectable record.
learning interfaces
Guides
Recurring characters that teach by function: Grounding Rod, Cask, and Avalanche Evan are good examples because they each carry a clear job and a clear lesson path.
recurring districts
Districts
Boon, Bane, Bone, Bonk, Honk, and Boof work well as district names because they are memorable, tonal, and easy to sort by mood or force.
Use them as neighborhoods, pressures, or named areas of attention rather than as decoration.
recurring forces
Factions
Keep groups small enough to name and tension-rich enough to matter. Examples include library keepers, working tables, caretakers, referrers, and the people who turn prompts into durable records.
objects and artifacts
Objects
Proof cards, sealed objects, recipes, screenshots, and artifacts all belong here when they become town memory rather than one-off material. Recipes and pies matter here because culinary science, homegrown food, and preserved ingredients are part of how a town remembers time. A pie is useful worldbuilding because it can carry weather, season, scarcity, hospitality, and a character's level of care in one object.
gardens and kitchens
Gardens and kitchens
Use this panel for homegrown practice, cooking intuition, garden prompts, and the small scientific questions that make a meal or crop feel repeatable instead of mystical. That includes pie crust texture, fermentation, soil moisture, seed timing, and the way a recipe becomes easier to trust when you can repeat it by feel and measurement.
dated source of truth
Sessions
RPG Wednesday logs are the time axis. Use dated sessions when the page needs actual events before interpretation.
Story hooks for practical content
Proof cards
A proof card becomes a sealed civic artifact used to stabilize promises before they decay into rumor.
Membership
Membership becomes the role system for who can witness, sponsor, work, or keep the archive in motion.
Services
Services become the commission hall where useful work enters the town as a request, an offer, or a repair.
RPG Wednesday
Sessions become the weather report that decides what the atlas should remember next.
Library and medium bridges
actual libraries
Why visit a real library
An actual library gives a scene more than research. It gives maps, local history, archives, zines, cookbooks, field guides, magazines, seed catalogs, and the feeling that a place has already been paying attention longer than the current story has. That is useful when a character needs a specific texture, a regional detail, or a fact that cannot safely be guessed from the internet.
Use the visit to extend a character, check a setting detail, or find the kind of object that would plausibly exist in that world.
new media pivots
Pivoting a literary universe
A literary universe becomes easier to adapt when it can move into other media without losing its core logic. The same canon can turn into a comic, audio drama, animation, zine, recipe card, short video, worksheet, or game prompt if the world already knows how to hold scene, voice, and object clearly.
This is a good place to think about authorship, audience, and how much of the world should remain implied instead of rendered.
Practical mirrors
If you arrived here by accident, these are the routes that keep the site useful without requiring the atlas to explain itself first.