📐 Infrastructure

One-Sheet — TODO

The primary page · duplicate into a module folder as sN-sheet.html and mark it 🌊 Fluid

How to use this

This is the page you land on, and the page you hold at the top of the night. Seven slots, in this order, and it should read as roughly one page. The discipline that keeps it one page is the foldouts — a roster entry costs a line until you open it. Everything long-form — reasoning, Developments, behind-the-screen truth, the numbered read-alouds in clock order — lives on the prep read. Full rationale in Module Design. Delete this box when you're done.

Tonight

TODO — the first thing that happens. A plain sentence: who does what, where.
TODO — the next one. Where they go, who they talk to, what they walk into.
TODO — the fight, if there is one, and who is in it.
TODO — what they find out that they did not know at the top of the night.
TODO — how the night ends.

Opening monologue

The opening monologue read to start the night

TODO — second person, present tense, no mechanics, the same register as the prep read's numbered read-alouds but pitched at the whole night rather than one beat. Three short paragraphs is the shape: where they are and what they think is true · the thing that has changed · the image that puts them in the first scene. It is effectively read-aloud 0; the prep read's boxes continue from it.

Then straight into TODO — name the first scene and its first read-aloud. Don't pause for questions in between.

Scenes — every scene that could fire tonight

TODO — one line on the shape. This is the possibility space, not a schedule; the clock lives on the prep read's Pacing block. List every scene that could fire, including ones the party may never reach.

Scene	What it is	It ends when
TODO · name ~N min · dice or no dice	TODO — two or three sentences. Bold the thing you must not forget to do.	TODO — the condition that hands off to the next scene.
TODO · name ~N min	TODO	TODO
TODO · name ~N min	TODO	TODO

Running long? TODO. Running short? TODO. Running wrong? TODO.

NPCs — one line each

TODO name — one line: who they are, and the single thing that makes them play differently from anyone else in the room. No wants/needs/has here — that is the NPC page's job.
TODO name — TODO.
TODO name — TODO.

Full entries — wants, needs, has, standing, grievance — on the prep read, beside the beat you actually talk to them in.

Monsters — open a block to run it

TODO creature ×N · reskinned TODO · CR N · AC N · HP N · the one rule that makes it different

TODO creature

Reskin of the TODO (MM) · size type, alignment · house tweaks labelled below

Armor ClassTODO Hit PointsTODO SpeedTODO CRTODO

StrTODO

DexTODO

ConTODO

IntTODO

WisTODO

ChaTODO

Resistances / Immunities / Senses TODO.

House tweak — TODO. Every deviation from the MM block is labelled as one. Two at most.

Actions

TODO. Melee attack: +N to hit, reach 5 ft, one target. Hit: TODO.

Objective: TODO — what it is trying to do, which is often not "kill the party". Morale: TODO — every roster gets a flee / surrender / stop condition, no exceptions. Tell: TODO — how it reads at the table.

Budget. TODO adjusted XP — band it against 2014 DMG thresholds for the party size. Give the scale-down in the same line: fewer creatures, and what band that lands in.

No combat this session? Say so here in a .lore box and say why — "nothing to fight" is a design decision and the sheet should show it was made on purpose.

Numbers

Check / value	When
TODO DC	TODO — only write a DC down when failure has a consequence you'd otherwise invent under pressure.
TODO value	TODO — counts, prices, initiative blocks, anything you'd otherwise hunt for mid-scene.

Rewards

TODO — a number or a named thing. Never "a modest sum".
TODO — what is available but not obvious, and what it costs to get.
TODO — the intangible ones. An NPC's regard, a confidence given up, a standing that moved. These are rewards; list them like rewards.
XP — state it, even when the answer is "none, they stay at level N".