Play Surface · Recurring Session
RPG Wednesday
Every Wednesday is a small canon furnace.
- session
- cast
- world
- arc
- library
A recurring Wednesday tabletop RPG session and a shared working surface for collaboration under enchantment. It has been developing for more than a year, so the public pages focus on what repeats: character sheets, session logs, the Town Library, and a readable record that can keep growing. Start with a character sheet, then move into the session log, world, and cast once the canon has enough weight to keep.
Character sheets arrive first. Sessions are dated events. The world and cast become persistent references once details recur enough to matter. The local gameplay kit stores private table state in this browser for use during play, including clay bodies, gustational protagonists, cartoon nemeses, spill prophecy, and relationship beats that read more like timing, ritual, and repair than formal declaration.
The party has met. Aetheris Solune and 'l'n'd'r are finding rhythm while a library is being built in town. That library is not background dressing. It is the current civic stage where records, magic, translation, and harmony across generations can take durable form.
It is also a pressure test for the rest of this site. If a prompt, card, or capture surface cannot survive a real table read, it probably needs another pass before it graduates into canon. Publishing starts as narration that can be revisited, cited, drawn, rehearsed, or converted into a prompt without losing the reason it existed.
Boonhonk is the wager here: boon, bane, bone, bonk, and honk functioning as readable transforms that can steer names, props, scene cards, and character logic. The public shape of the work matters too: captions, transcripts, and clear route labels let humans and external models review the page for education, entertainment, literacy, numeracy, and worldbuilding intent without needing to infer the purpose from the mood alone. The Town Atlas keeps the story bible separate so the play surface can stay focused on what is happening now.
Topic links are not here as decoration. They are metacognitive exits: algorithms for procedure, statistics for evidence, scale intuition for scope, nutrition for inputs, and mental health for return paths that help a practice keep going.
Culinary technique is a practical gameplay grammar here. A session can begin with mise en place, reduce to one playable pressure, emulsify character motives, ferment a slow mystery, and end with service: what the table can carry back into notes, art, or the next route.
Tropes and jokes need ingredient discipline. Some arrive as base stock, some as garnish, some as heat, some as acid, and some should stay unopened until the table has enough context to taste them. The goal is not to explain every joke; it is to give the world enough timing and dimension that the joke can land cleanly when served.
Spw interactions should teach the same distinction a table needs: a click projects you into the next surface, a deliberate hold acknowledges resonance, and a collected value becomes material for later play. That makes links, sigils, recipe terms, and character handles feel like interoperable props instead of decoration.
RPG Wednesday should feel like a recurring occasion where potential has been prepared in advance. Bring a specialty, a technique worth trying, a vocabulary word, a recipe question, a visual hypothesis, or a cheerful reason a concept deserves to exist. The table can then celebrate the material by testing what it does.
because live play should survive the night as usable memory, shotboard material, and episode pressure without losing the energy that produced it.
players, GMs, illustrators, filmmakers, actors, developers, and worldbuilders who want one table artifact to carry canon, staging, and promptability together.
session recaps, cast pressure, world rules, arc candidates, episode hooks, scene prompts, and visual-reference packets that can move into production.
A shared meal can carry etiquette, debt, care, refusal, repair, and rank. Library tea cake, market-day stew, or lantern broth can say what a speech would flatten.
meal -> relation
Seeds, pests, weather, storage, and harvest make time playable. A town remembers what it had to tend.
growth -> consequence
Some magic should behave like culture: it needs a vessel, a starter, a boundary, a temperature, and enough time to become itself.
conditions -> spell
If saffron, cacao, citrus, coffee, black garlic, or a magical salt is inconvenient to make nearby, let it arrive with a person, favor, rumor, substitute, guild habit, or small risk.
route -> character
Carrots, cucumbers, corn, peppers, potatoes, squash, and cabbage can become recurring comfort: dips, pickles, roasted edges, and small rewards between heavier scenes.
snack -> return
Gumbo can teach integration, chili can teach heat and variation, succotash can teach companion crops, and barbecue can teach slow systems under care.
dish -> concept
Lantern broth, market stew, gumbo, chili, or stockpot soup can turn many separate clues into one served context.
many -> bowl
A wing sauce, gravy, stock, herb oil, or brine can turn leftovers into value. That is good cooking and good campaign design: do not waste the residue.
residue -> reward
Pastry can stay in the background as an attention model: crust as boundary, filling as motive, slice as frame, lattice as relation, service as reveal. The joke works best when the geometry quietly teaches the room how to look.
pie -> attention
Mr. BoonWAP should be able to survive three tests: a table scene, an augmented-reality story prompt, and a restaurant or pop-up truck concept where flavor, mascot, ordering ritual, and lore all reinforce each other.
protagonist -> medium
#>rpg_wednesday
#:layer #!play
#:surface #!event_log
^"structure"{
sessions: ~"./sessions/" @event session log, dated /YYYY-MM-DD/
world: ~"./world/" ^object stable setting and lore
cast: ~"./cast/" ~refs character reference nodes
arcs: ~"./arcs/" ?[probe narrative thread groupings
}
Sessions are events at specific moments in time. The world is the stable setting those events happen inside. Cast members are references back into sessions. Arcs are open questions carried across multiple sessions.
The URL structure follows the Spw operator model. See the grammar surface and the deeper spw-workbench notes.
Start Here
This route works best when it gives you an immediate first move. Choose the path that matches how you arrived: as a player, a reader, an illustrator, or someone trying to understand the wider medium.
Use the session log and character sheet when you want play to stay legible after the table.
Use the library, scene material, and shotboard bench when you want a drawable object, gesture, panel sequence, or layout worth revisiting.
Use the cast and arc routes when you want timing, voice, and unresolved pressure that can be rehearsed later.
Why this card exists
Characters need a private place to form before they become public cast memory.
This route produces a starting point for players, illustrators, and collaborators who need a person before a whole session.
Why this card exists
This is the route for making play legible as study, documentation, and a public learning surface.
It keeps the campaign close to the library metaphor instead of letting it drift into a generic menu.
Why this card exists
This card exists for one-person development work that should remain editable before it is public-facing.
It is the place to sketch a portrait, voice, or pressure lane before promoting anything to cast status.
Why this card exists
The log is the source of truth because a campaign needs chronology before it needs theme compression.
It can produce recap seeds, episode pages, and durable memory of what actually happened at the table.
Why this card exists
This card exists so image work can stay close to campaign memory and not become a separate archive.
It helps collaborators stage visual canon, shotboards, copy-layout experiments, and prompt packets before rendering anything.
Why this card exists
This route keeps the site from collapsing every question into the same campaign vocabulary.
It gives the reader a place to move sideways when the current problem is really procedure, evidence, or scope.
Why this card exists
This card connects campaign play back to interface design so the site can learn from its own game surface.
It produces better hooks, better cards, and better handoff seams for the next session.
public canon should grow from actual play, not from a summary written too early.
you need session recaps, cast pressure, world rules, arc candidates, or a route that can teach the table back to itself.
episode pages, trope candidates, magic-system experiments, scene prompts, and reusable artifacts for collaborators.
Local Gameplay Kit
Enable JavaScript to use private localStorage and IndexedDB tools for character-sheet drafting, scene state, initiative, clocks, scratch notes, character beats, canon candidates, copyable recap seeds, and a local asset atlas for scenes, images, textures, and items. A scene can begin with only a title and deepen later. If you want the public-facing version first, begin with the character-sheet builder; the campaign pages remain readable without any scripting.
Why this kit exists
This kit keeps private table state close to the campaign while leaving the public routes clean, searchable, and usable without JavaScript.
It helps the table track temporary scene pressure and produce later recap seeds without forcing every note into canon immediately.
Code can be read out loud on TikTok. A group chat lets multiple creators share a rhythm of production, maintain momentum, and keep one person from burning out while the canon develops. The local kit is intended to make those live riffs easier to stage, regroup, screenshot, and describe aloud without pretending they are public canon yet.
The adjacent mental-health topic is part of the same question. Good play surfaces do not only store lore. They give people a light enough return path that a concept can keep growing across the week.
Journal to Canon
The local kit is most useful when each note lane has a job. Keep emotional residue private, but promote recurring beats and stable facts quickly enough that the campaign can remember itself. When a relationship is developing, write the offers, refusals, timing, and repair beats before trying to explain the whole theory around them.
Scratch notes
Use these for rulings, loose dialogue, and impressions you are not ready to share. They are for the table, not for publication.
Character beats
Write what changed in a person: fear, trust, obligation, self-image, appetite, or the shape of a ritual exchange. This is the bridge between gameplay memory and character development.
Canon candidates
Mark names, places, items, rules, and promises that should move into the cast or world registers once they recur.
Session recap seeds
Use short recap seeds for what other players, future collaborators, or author-you need to remember when the next session or public write-up begins.
Name fabric
Track when the wording itself changes the scene: acronym pressure, boon/bane/bone/bonk/honk drift, title mutations, or the point where a joke starts acting like a rule of the world.
Read-aloud hook
Every promoted note should be able to survive one spoken sentence. Give it a stable title, a clear subject, and one line that a player or screen-reading agent can carry forward without the whole context window.
Authors can use the same ladder outside of games: keep residue private, name character pressure, promote durable world facts, then publish only the notes that survive contact with the next draft.
Weekly Affairs: Crops, Recipes, Trade
A campaign can increment more than plot. Pantry state, crop experiments, local ingredients, recipes, and slow hobbies all give the week somewhere practical to accumulate. This is also a good place to practice small evidence habits, scale awareness, and layout as procedure without leaving the story surface behind.
Crops as world-state
Track which herbs, grains, beans, roots, or preserved goods are abundant this week. That gives trade, scarcity, hospitality, and travel a material basis instead of only flavor text.
Recipes as party memory
A shared stew, tea, flatbread, ferment, or market lunch can become a recurring object like any other piece of canon. Players remember tastes, rituals, and tools surprisingly well.
Ingredient loops reward return
Use the same crop loop outside the fiction. If a player is growing herbs, trying a bean dish, or refining a weekly breakfast, that can feed directly back into the table's imagination about labor and care.
Low-noise prompts are enough
Sometimes all you need is a title: Market greens, Rain cellar onions, Salt-fish week, Three-bean caravan soup. The rest can arrive later through card edits, screenshots, or exports.
The adjacent nutrition topic treats this as real weekly practice as well as worldbuilding. Let crops, recipes, and ingredients pull a little more weight for memory, imagination, and shared time.
Asset Atlas Protocol
The local gameplay kit already carries a working asset atlas in the local kit. This section is the protocol for what gets promoted out of it: which card shape earns a screenshot, which metadata stays attached, and how a stable table card becomes prompt material, a storyboard panel, or later SVG cleanup work.
The composable fundamentals are simple on purpose: title, kind, namespace, timeline, hook, proof. Scene, dice, swag, texture, item, and threat cards can all use the same grammar if the title stays speakable and the proof stays local enough to trust.
Table narrator: what if today only needs one good scene frame, one die-result card, and one piece of recurring swag? That is already enough to remember the session by.
Storage boundary
Images should live in IndexedDB. localStorage should keep only metadata such as ids, labels, namespaces, timelines, tags, sheet cues, selected motif, and the current preset or filter state.
Composable fundamentals
Every durable card should tell you its title, kind, namespace, timeline, spoken hook, and table proof. That is enough structure to stay flexible while still being easy to sort, read aloud, compress, and export later.
Storyboard pass
When a scene feels promising, split it into three handles: what the panel must show, what the caption must preserve, and what an artist can change without breaking the beat. That makes layout workshop-friendly before the image exists.
Prompt bundles
A saved card should export more than an image dump. Keep the screenshot, the short prompt hook, the tags, the namespace, and the timeline together so Midjourney, ChatGPT Images, Gemini, Firefly, Ideogram, or a later collaborator gets the same local contract.
Screenshot pass
Controls should recede, contrast should increase, and the card should lock to a predictable aspect lane while leaving a manual exit path. The screenshot stays manual because human judgment still decides when a card is ready.
SVG cleanup handoff
When a card keeps recurring, hand it off with the role, the stable silhouette, the material cues, and the mutation budget. A simpler coding model should know what may change and what has to stay anchored for the canon to remain readable.
Screen-reader hook
A good card keeps a plain-language title, a one-line spoken hook, and a concise caption explaining what matters in the image. That is useful for accessibility, but it is also useful for collaborators who meet the canon through read-aloud tools or voice notes first.
JSON and video lane
Later the same bundle should be able to feed a JSON export or a short video wizard: title, namespace, timeline, tags, prompt note, spoken hook, and image references arranged so a recap reel or narrated overlay does not have to guess the canon.
Recent generator shelf
As of April 22, 2026, the nearby shelf includes Midjourney, ChatGPT Images, Gemini, Adobe Firefly, and Ideogram. Mention image generators in general first, then name the shelf when the date actually helps the handoff.
Discord keeps the live memory, TikTok keeps the performance beat, and the atlas keeps the table from losing good material between sessions. I am also currently fundraising and storyboarding for an animated series with Raven of the Broken Biscuits; later this surface should have a credited place for Raven's art that does not imply it is mine.
'l'n'd'r
The character
'l'n'd'r Bjrnkptpf is the main campaign character: less a rock gnome than a clay golem shaped by years of meditation, prayer into wonder, and the desire to understand how claimed spells reverberate into body, speech, and action. Bluish-grey skin like modeling clay, gemdust freckles, and speech bubble physics treated as an actual material problem. The character exists to narrate and explore trope physics: what enchantment is made of, how language becomes embodied, and what has to stabilize for collaborative meaning to hold.
Rock gnome was an earlier sketch, but clay golem is closer to the real pressure behind the character. After losing insurance, income, and housing in the aftermath of 2022 site-stabilization work, I kept returning to the irony that so much engineering labor touches public stability without carrying enough care for human lives. 'l'n'd'r is one answer to that frustration: a wonder-made body for studying enchantment, stabilization, and the moral weight of the spells we claim through speech and practice. Words are still the spell. Boon materializes as a nucleation field, Bone as the lattice that carries structure, and HONK remains pure propagation.
When the sheet changes, update the builder first, then move stable versions into the cast register or Midjourney Bench once the canon settles.
Quinary Pressure
Part of the current campaign fabric turns on a touchy cluster of beings and performances. The rule for writing them is simple: treat existence as a live pressure rather than a cheap punchline, and let intimacy develop through timing, offers, refusals, and repair instead of heavy exposition.
Mr. BoonWAP
Mr. BoonWAP is a sentient pie, one of the quinary five, and a protagonist for developing augmented-reality storytelling as a medium. The name carries its own field note: WAP stands for Wonder About Pi(e). He already exists in the campaign logic; the deeper test is how the world handles a being who may be pastry, person, projection, offering, mascot, menu item, or some unstable braid of all six.
The dimensional pie relationship should be meaningful outside the page. If BoonWAP cannot suggest a table scene, a phone-camera overlay, a pop-up truck ritual, a shop sign, a flavor flight, and a reason to talk about attention, appetite, and service, the concept is not yet engineered well enough.
Slibbon Bap
Slibbon Bap is Mr. BoonWAP's magical elf-like assistant, friend, and something close to a life partner. Where BoonWAP draws projection and appetite, Slibbon Bap reads the room, translates small signals, and helps ritual exchange become legible before it hardens into doctrine.
Mr. BaneWAP
Mr. BaneWAP follows the ceiling of a classic cartoon villain: dramatic, mischievous, and hungry for trope-based trouble, but not built for true malice. He is officially Mr. BoonWAP's nemesis, though the pair function as a necessary duality and keep ending up on the same side of larger harmony quests.
How it should read
Let the series perform agency slowly. Early scenes can rely on gesture, staging, and mutual adjustment; later scenes can afford clearer language because the characters earned it. If a scene has to choose between theory and chemistry, keep the chemistry and let the notes lane carry the interpretation.
This material should move through the existing ladder: jot it in the local kit, log it in sessions once it happens, and only then let it harden into cast memory, arc naming, or asset-atlas portrait cards.
Boonhonk Research Genre
The combinatorics of names are part of the physics here. Boon, bane, bone, bonk, and honk are not only moods. They are small operational transforms, and acronym play like WAP can carry plot pressure, typographic humor, cultural texture, and scene direction at the same time.
Treat this section like a pantry, not a punchline glossary. The useful record is what a name can do: what it primes, what it withholds, what kind of entrance it permits, and what later reveal it makes possible.
Name drift
Boonhonk treats naming as operational. Boon adds arrival, bane adds cost, bone adds scaffold, bonk adds collision, and honk adds broadcast. Prefixes, postfixes, acronyms, and title swaps are allowed to shift the force profile of a character or object instead of serving only as decoration.
WAPboy
WAPboy is black, and his only characteristic so far is that he is trying not to spill 1pi. That is enough because the surrounding physics can carry the load. He works like a cherry on top of deeper lore: simple enough for shenanigans, precise enough that every wobble, shortcut, warning, or near-spill can reveal how Wonder About Pi(e) behaves.
Gravy Davis
It is prophesied that once WAPboy spills 1pi, he becomes Gravy Davis. Gravy Davis is a jazz musician who really does not care about spilling pies and has already spilled infinity pi(e)s. That makes him both a future self and a warning about what a looser relation to consequence looks like.
Honk Bazongas
Honk Bazongas is a clown and an okay detective. The name should land quickly, but the world should still treat Bazongas plainly: a high-quality shoe brand that can absolutely make clown shoes. That gives future design work a useful constraint without stopping the scene to explain the joke.
Canonical plane
WAPboy, Honk Bazongas, and Gravy Davis form three points for a canonical plane. If one point appears, ask how the other two are being implied: restraint, signal, and aftermath; innocence, clown logic, and consequence; or offer, broadcast, and spill.
Willby Spillzus
The Cult of Willby Spillzus worships the transformation point where WAPboy becomes Gravy Davis. They are useful because they treat the spill as destiny. That gives the campaign a pressure source that is mythic, silly, and still legible enough to track in a session log.
Mimes Against WAP
Mimes Against WAP care about WAPboy, but object to WAP as a force that makes clowns blurt boonhonk. They are a useful faction because their silence is not absence; it is discipline, protest, affection, and stagecraft held under pressure.
Some jokes run on boof and wabopie drift, where characters briefly think am WAPboy. Keep that in the notes lane as name physics, then promote only the versions that survive repeated play. Every good screenshot card from this genre should also carry a stable title, a one-line spoken hook, and enough plain language that a screen-reading agent can still wonder productively about the instantiation.
Current Arc
Arc
Working pressure only, not yet a formal arc: the town library going up, the party learning how to hold collective memory, Aetheris Solune and 'l'n'd'r gradually retelling a months-old surprise, the quinary five, Mr. BoonWAP's unstable personhood, the BoonWAP/BaneWAP duality, WAPboy's 1pi spill prophecy, the canonical plane with Honk Bazongas and Gravy Davis, and the slow conversion of attraction, timing, and repair into mutual ritual. Name the arc on the arc register only after sessions prove it can survive repetition.
Last Session
The party has met, but the dated public log has not been written yet. When the first session lands, capture how Aetheris Solune and 'l'n'd'r describe the earlier surprise, how the library build changes the room, how BoonWAP appears, what Slibbon Bap stabilizes, whether BaneWAP's mischief sharpened or softened the room, and whether WAPboy's spill pressure entered the canon. Start the log.
Next Session
Wednesday. Stage a small number of durable beats: one library-construction beat, one Aetheris/'l'n'd'r story fragment, one BoonWAP appearance, one Slibbon Bap translation or assist, one BaneWAP interference, one WAPboy pressure beat, and one moment where timing or repair says more than explanation. Details belong in the session log once the event is written.
Active Cast
'l'n'd'r remains the main anchor, with Aetheris Solune now part of the active memory lane. Mr. BoonWAP, Slibbon Bap, and Mr. BaneWAP act as the most immediate recurring companion cluster, and WAPboy, Honk Bazongas, Gravy Davis, and the newly arrived Deskar Null continue entering orbit as serial-lore pressure points. Move them into the cast register once session pages begin proving their recurrence.
Library Build
The town library is the current stage for development, magic, and intergenerational harmony. It is also the cleanest place to test whether a prompt, screenshot card, spoken hook, or image study can carry memory without flattening the story.
Use this section when the route needs a stable image seed for town memory, clay-body metaphysics, and wonder about how speech or enchantment takes material form.
Aetheris Solune and 'l'n'd'r are learning how to narrate a past surprise while the town builds a place sturdy enough to hold future memory.
The library lets the campaign ask better questions: what deserves indexing, what should remain touchy or provisional, what becomes public canon, and how older and younger readers might inherit the same story without flattening its magic.
This is also where a culture can start to hold. A good library card should survive a screenshot, a spoken caption, a screen-reading agent, and a prompt copied into a recent image generator without losing the scene's actual point.
Route Atlas
These are the routes that make the campaign legible. Read them as a small publishing system: event log first, references next, then surrounding tools and topic context.
-
@ sessions
Dated event log, ordered newest first, with each session at
/YYYY-MM-DD/. - ^ world Setting notes, currently a placeholder until sessions create enough stable lore to warrant it.
- ~ cast Character sheets, recurring portraits, and stable references once a person, creature, or quinary presence has enough weight to deserve memory.
- ?[arcs] Story threads, currently a placeholder because arcs should emerge from sessions instead of being forced in advance.