Sessions
A session page should be short enough to write after play, but structured enough to feed the rest of the campaign record.
This is the dated source of truth for RPG Wednesday. The campaign has been developing for more than a year, and the log should stay terse enough to write after play and explicit enough to reuse later. Each session belongs at /play/rpg-wednesday/sessions/YYYY-MM-DD/, newest first, so arcs, world notes, and cast references can grow from actual play, including whatever the table learns about Mr. BoonWAP, Slibbon Bap, Mr. BaneWAP, WAPboy, Honk Bazongas, Gravy Davis, and the quinary five.
Tomorrow's table date is May 27, 2026: one day after the B-cycle release close on May 26 and one day after the TikTok group chat reached a 200-day streak. Treat the note as a cycle reflection first, then as a production spark: what did the cycle close, what did the streak prove, and what artifact should survive the night?
chronology matters before lore hardens into canon.
a scene, joke, artifact, or rule needs a durable dated source.
recap seeds, cast updates, world candidates, arc candidates, and later episode pages.
Local Gameplay Kit
Enable JavaScript to use private localStorage tools for scene state, initiative, clocks, scratch notes, character beats, canon candidates, and session recap seeds. The static campaign routes remain available either way.
Scratch during play. Keep timing, rulings, images, and table jokes rough while the scene is still moving.
Promote the return path. Recap seeds should name the beat someone needs in order to re-enter the next session quickly.
Then route outward. Cast, world, and arc pages should receive only the session memory that stays useful after the recap.
Log
The log starts with a release-day seed and grows forward from there. On the 13th and 26th, add a folder at sessions/YYYY-MM-DD/index.html and link it here. The A cycle closes on the 13th; the B cycle closes on the 26th. Wednesday sessions can then reflect on what the cycle closed and convert one streak, image, card, or prompt into playable material. The route shape is documented more deeply in spw-workbench.
Session Format
A session page should be short enough to write after play, but structured enough to feed the rest of the campaign record. It should also be easy to quote, screenshot, and promote into related surfaces later.
- @date The session date as the frame sigil: stable, sortable identity.
- ^"recap" What happened: 2-5 sentences in plain prose.
- ~cast Which characters appeared, with links to cast pages when those exist.
- ~character_beat What changed in a person: a fear sharpened, a bond shifted, a vow hardened, a mask cracked, or a subtle ritual became more legible through timing, refusal, or repair.
- ^canon_candidates Names, places, items, or rules that may deserve promotion into cast or world memory after another pass.
- *"name_drift" Log acronym pressure, boon/bane/bone/bonk/honk recombinations, and other moments when the wording itself changed the scene. If boof or wabopie logic makes someone briefly think they are WAPboy, that belongs in the record.
- ~touchy_questions If BoonWAP's existence or reality becomes a pressure point, log how the room handled it instead of trying to settle it too cleanly. WAP here means Wonder About Pi(e), and the uncertainty is part of the fabric.
- =spoken_hook Give each logged session a one-line spoken summary that can be read aloud, screenshotted, or handed to a screen-reading agent without losing the main tension.
- ?[turning_point] The moment the session pivoted, added after the fact.
- ~arc Which arc this session belongs to, if one has been named.
- >next_pressure What should be loaded into the next session: unresolved danger, emotional fallout, or the question still hanging in the room.