Chapter 6 — Where to Start

You have a character. You have an RPG. You have a source of fiction in front of you — a module, a dungeon, an oracle, a solo-system, a rulebook. You want to play. Where do you start?

This is the chapter for that.

It is not a teaching chapter. The book has already taught you what Lens is, how Ignition works, how a Pressure Clock fills, how the Commit Procedure runs, how perspective generalises. You have read those chapters. You have watched the engine work three times — Kael at the latch, Kael in the safe house, Lehmann reading the agent. You know how Lens runs. What you need now is the entry point, and the entry point depends on what kind of fiction you brought.

Here is the rule the rest of the chapter sits on. Lens does not tell you what is. You do — or your source does. Lens does not invent the world unilaterally; it cannot start from nothing. What it does, and what nothing else in your solo-RPG kit does, is complete the world your source provides by giving you perspective, pressure, and the firewall that keeps your character honest about what they have actually seen. Lens is built to pair. The richer the source, the lighter the work. The leaner the source, the more you bring — and the better you bring it, the more Lens has to read.

There is one refinement to that rule, and it matters most when your source is thin. A Lens roll can do more than read what is already on the page — it can surface a candidate: sign of occupation in an empty ruin, a presence behind a door, a detail that does not fit. That candidate is not yet true. It becomes true only when something confirms it — your source, an oracle, a Yes/No, or the Commit a full clock produces. Lens proposes; the world disposes. What Lens never does is propose and confirm in the same breath: the gut that flags a thing does not also get to rule it real.

Two guards keep this honest. First, you never ratify your own read — a confirmer is something outside your wish for the answer, and where you have nothing else, Lens’s own Yes/No Dice are the minimum confirmer, and they are enough. Set the likelihood from the fiction, not from the answer you want. Second, hold the result felt, not fixed until something confirms it — an impression that refuses to harden into fact is not a flaw in the read; it is the thing that stops you inventing. This is what lets Lens run on a setting alone, with no other oracle: the proposals are yours, the confirmations are the dice’s, and the firewall sits between them.

The flow itself does not change. Ignition gives you a starting position with a first Pressure Clock. The clock fills through Lens rolls. The Commit Procedure produces a world-state change with its Belief. You continue. Every source-type runs the same engine. What differs is what is already in front of you when you sit down.

Find your source. Read the spread. Start there.

> A note on Palettes. Before the spreads, one term you will meet in each spread’s Prep. A Palette is a Lens table translation layer — a set of result-text variants that re-render the canonical L-table results in a specific genre’s register, so the same roll reads as gritty-low-fantasy in one Palette and weird-fiction-investigation in another. The results are unchanged; the flavour fits — only the palette’s Dial touches the dice, setting how far the genre leans into the uncanny. You select a Palette at prep, once, and it sits behind your L-tables for the session. Six Palettes are drafted in the appendix; you can build your own using the structure there. Selecting a Palette is a one-line prep step in any source-type — that is why it appears in each spread.

Modules and Scenarios

A module is the richest source you can bring. It supplies the world — the place, the people, the situation, often the hook for the night. It usually supplies NPCs with names and motivations. It supplies the system register through whatever game it was written for. Most of what you need to play is on the page in front of you.

What you bring is a character with at least one detail of bite — not just stats and skills, but one fact about who they are that the situation could land against. Kael being a thief who reads small signs is the example. Frank Mealor’s jobs he can’t account for in daylight is another. The character needs something the world can touch.

What Lens supplies is what modules are weakest at: the felt perspective on what the module describes, the pressure that doesn’t exist in inert prose, and the Commit/Belief firewall that keeps you, the player who has read every page, from quietly handing the character your knowledge. The watch in the module is on the page. What it feels like to be the character listening for the watch is not — that is what Lens is for.

The flow is the same. What changes is the prep, and that Ignition is short because the module hands you most of it.

Prep. Read the module through. Not skimmed — actually read, the way the legacy module-play discipline names it. Know the rooms, the people, the traps, the consequences. You are not going to forget what you read — Lens does not require you to forget. The firewall keeps the character honest while you, the player, hold the module fully. Select a Palette that fits the module’s genre; the appendix has six drafted.

Ignition — short form. Start at Problem Setup. The module gave you the Hook: the call to action, the inciting incident, the faction making demands. “As much or as little as the situation doesn’t already hand you” — for modules, the situation hands you most of it. Read the Aim from what the scenario is pressing the character toward. Read the Friction from what the module says is in the way. Read the Stake from what the character personally loses if the scenario goes wrong. Set the Stage from what the module describes around the opening.

The first Pressure Clock — named in your voice. This is the only non-dialable step. Even when the module has given you everything else, you still name your character’s want as a question they would ask, and you size the clock against the scenario’s tightness. Can I reach the prisoners before the warlord wakes? 0/4. The module gave you the prisoners and the warlord; you gave the clock its question. Set your World Pressure at the same moment — the session-level timer that advances each time a local clock fills. The module’s scope tells you its size.

The first Lens roll. When the character meets the first concrete moment — a threshold, a watching presence, a hidden mechanism — the table that fits that moment fires. Roll it; read the result; mark the clock; play.

Into flow. Pressure Clock fills through Lens rolls. The Commit Procedure runs when it fills, deriving its Dominant Tag from the visible tag record on your Pressure Card. Your RPG handles what your RPG handles — when the fiction surfaces a discrete uncertain moment (a guard turns the corner, a trap clicks, a save is needed), the RPG resolves it. The Pressure Clock doesn’t track success or failure — your RPG handles that. The clock and the RPG roll are independent. They run in parallel. Lens sets the pressure. Your RPG resolves the action.

One thing modules ask of you specifically: when the module says something is there that the character has no way to perceive — the trap on the third step, the secret door behind the waterfall — let the RPG’s perception roll gate whether the character notices. Fail the perception, and the character walks into the trap. That is not a Lens problem; that is the firewall working honestly. You know the trap is there. The character earned no awareness of it. The bomb is under the table. The session is fifteen minutes of suspense, not fifteen seconds of surprise.

Solo Mode for Traditional RPGs

Many traditional RPGs publish solo supplements: reaction tables, encounter generators, scene structures, sometimes whole solo campaign frameworks. Some are slim — a few d20 tables and a sentence about how to use them. Some are substantial, with whole settings prepared for solo play. The supplement constrains by what the parent system permits.

What the supplement supplies depends on the supplement. Read what it gives you: setting, NPCs, reaction mechanics, journey systems, encounter tables. Whatever is there, treat as module material — it is your “what is.”

What you bring is the parent system’s character, your familiarity with the parent system’s mechanics, and the same one-detail-of-bite that any character needs.

What Lens supplies is what solo supplements rarely include in full: deep perspective work on what the supplement surfaces, sustained pressure across scenes via the Pressure Clock, and the Commit/Belief firewall. Reaction tables tell you what the NPC does; Lens tells you what your character makes of it. Encounter tables tell you what shows up; Lens reads how it lands.

Prep. Read the supplement’s relevant section the same way you would read a module. If the supplement comes with a scenario, treat it like a module and use the module flow. If it provides only generative tools — reaction tables, encounter tables, oracle questions — treat those as your “what is” generators and proceed. Select a Palette that fits the parent game’s genre register.

Ignition — variable form. Depends on what the supplement gave you. If a scenario, short-form — read the Stage from what the supplement describes around the opening. If only tools, fuller Ignition because more is unnamed, and the Stage is your read of what the supplement’s tools imply around the character.

The first Pressure Clock. The non-dialable step, whatever else the supplement supplied. Name it in your character’s voice. Size it against the situation the supplement set up. Set World Pressure alongside it, sized to the supplement’s arc.

The first Lens roll. Same as module mode — when the character meets the first concrete moment, Lens fires.

Into flow. Same engine. Same RPG boundary — the parent system’s resolution mechanics handle discrete uncertain moments; the Pressure Clock measures the pressure of being in the situation; Lens rolls fill the clock. When the clock fills, the Commit Procedure runs and the Commit’s shape derives from the visible tag record’s Dominant Tag.

If your supplement’s reaction or encounter table fires alongside Lens, treat the table’s result as a fact the world has produced — what shows up, what an NPC does — and then fire Lens against it. The supplement supplies the what; Lens reads the character’s perspective on it.

Solo-First Games

Solo-first games are built from the ground up for one player. The move-and-oracle systems, the journaling games, the prompt-and-die systems — they integrate the apparatus a traditional RPG leaves out. Most have built-in oracles, encounter generation, scene structures, and partial interiority via compels, reaction tables, or move-based prompts.

What the solo-first system supplies is integrated apparatus: a way to ask questions of the fiction, a way to generate NPCs and threats, a way to manage pacing. Some have partial interiority work — compels that ask whether a strong urge takes hold, reaction tables that surface what an NPC does. Most do not have what Lens provides.

What you bring is the system’s character, the system’s rules in working memory, and the awareness that Lens adds — it does not replace. The system’s oracle is still your oracle for objective truth. The system’s encounter generator is still your generator. Lens is not a substitute for any of that. Lens is what you reach for when the moment turns inward.

What Lens supplies is the Commit/Belief firewall — which most solo-first systems lack — and deeper perspective work on what the system surfaces. The system gives you a compel; Lens gives you the full reading of the compel’s pull. The system rolls an encounter; Lens reads the character’s gut on the encounter as it forms.

Prep. Have the solo-first system’s materials open and ready. Your oracle, your tables, your move list, your character sheet. Lens does not displace any of this. Select a Palette that fits the system’s tone; the genre and register the system was designed around will usually point you to one.

Ignition — short to medium form. Solo-first systems usually start cold: you decide what scenario you are running, what your character is doing. Hook from your character + the situation you have set; Aim from the situation’s pressure; Friction and Stake follow; Stage from what your set situation puts around the character. If the system has a premise mechanic — a quest structure, a journey framework, an objective track — it can supply the Hook. Use what the system offers.

The first Pressure Clock. Named in your voice. The system may have its own progress tracks; the Pressure Clock is not a progress track. The Pressure Clock measures pressure on the character; the system’s track measures progress toward objective. Run them in parallel. They are different objects. Set World Pressure too, sized to your scenario’s arc — a third track, separate from both.

The first Lens roll. When the system has surfaced something — an oracle answer, an encounter, a compel — and the character is reading it, Lens fires.

Into flow. Same engine. The solo-first system’s resolution mechanics handle action and outcome. Lens reads the pressure of being in the situation. Where the system has its own pressure mechanic (momentum, chaos, fortune, or similar), Lens’s Pressure Clock runs alongside it — measuring what the character is under, not what the scenario is under. They do not duplicate. They complement. When your Pressure Clock fills, the Commit Procedure runs from the visible tag record’s Dominant Tag.

Dungeon Crawls

A dungeon crawl is the test case for Lens. The dungeon brings the world richer than almost any other source — maps, rooms, encounters, mechanics, treasure, traps — and brings interiority lower than any other source. The goblin in room 3 is a stat block: hit points, armour class, attacks, loot. The corridor is a description of length and texture. The encounter is a fight resolved through dice.

Without Lens, that is the whole experience. With Lens, the goblin in room 3 is no longer CR-1. It is a perspective with a gut — fearful, confident, compelled, exhausted, hungry, watching the door. The corridor is no longer a length of stone. It is what your character reads in the silence before the door at the end. The encounter is no longer the fight; it is the moments before, during, and after, charged with pressure that the dungeon book did not write.

A glimpse of what that looks like, from the goblin’s side, before the door opens. Sam jumps to the goblin’s perspective for one roll — L4: Disposition — and gets 8, DESPERATE NEED. Urgency sharp. Options gone. They need something badly enough to show it. Impulse: I’ll address the need. The goblin in room 3 is now a creature with a problem the dungeon book never named — hungry, cornered in this room three days, the patrol overdue, this is the door something has to come through whether it is rescue or end. Sam, playing the PC at the door, doesn’t know any of this. But when the PC opens that door, the encounter is no longer a tactical roll against CR-1. It is two perspectives meeting, one of which has been waiting.

What the dungeon supplies is everything except interiority. World, structure, encounters, mechanics, loot — all there. The author of the dungeon may have written rich NPC motivations for the major figures, but the dungeon’s small inhabitants — the goblin, the kobold, the guard — get stat blocks, not interior lives.

What you bring is a character with one detail of bite, awareness of what level of the dungeon you are running, and the recognition that you are supplying what the dungeon does not. The dungeon will not give you the goblin’s fear. You will — through Lens.

What Lens supplies is the full transformation: perspective on the goblin’s room, on the corridor, on the encounter; pressure as the dungeon closes around the party; the Commit/Belief firewall that lets a player who has read the dungeon book run a character who has not.

Prep. Know the level you are running. Have the dungeon’s materials in working reach. Know which rooms hold what; you will not forget, and Lens does not require you to. Select a Palette that fits the dungeon’s register — gritty-low-fantasy, weird-tale, high-myth — whichever matches the prose of the book in front of you.

Ignition — short form. The dungeon supplies the Hook through its premise: the dungeon exists to be explored, cleared, looted, escaped. Start at Problem Setup. Aim from your character’s immediate purpose: get past this level, reach the prisoners, find the artifact, kill the boss. Friction from the dungeon’s threats. Stake from what the character personally loses if the run fails — not “the party dies” but something specific to the character. Stage from the dungeon’s described surroundings — the room, the corridor, the door, the watching dark.

The first Pressure Clock. Can I reach the boss before the patrol cycles back? 0/4. Can I get the artifact out of the vault before the wards trigger? 0/3. Named in your character’s voice. Sized against the immediate near-term — the next room, the next floor, the next encounter. World Pressure runs alongside, sized to the whole dungeon’s arc — the larger crisis the dungeon is the site of.

The first Lens roll. The first door, the first corridor, the first sense of the place. Lens fires on the threshold the way Sam fired L2 with Kael — what the dungeon feels like from inside the character, not from the page above the table.

Into flow. Lens rolls on what the character meets. The Pressure Clock fills. When it fills, the Commit Procedure produces world-state change derived from the visible tag record’s Dominant Tag — the patrol returns earlier than expected, the wards register intrusion, the boss is alerted, the artifact’s keeper stirs. Your RPG handles combat, resolution, harm, loot. The clock measures the pressure of being in the situation. The RPG resolves the action. The two run in parallel.

One discipline specific to dungeons: when a Lens roll surfaces something the dungeon book described — the goblin’s posture, the trap’s mechanism, the room’s wrongness — the fact of the thing is the dungeon’s; the character’s reading is Lens’s. The goblin is in room 3 because the book says so. What the goblin’s gut is doing in room 3 is what you just rolled.

The Room Speaks — an optional mode

Here is a mode you can switch on for a crawl that is all mechanism and no breath — the kind where you build a character with a past and then never once touch it. In The Room Speaks, a scene-room holds you until it has spoken: you may not narrate leaving until the room’s clock fills and Commits. The clock is small — one segment, two for a room with weight, three at the most — and the threshold read usually fills it on its own. It is the GM leaning in at the door: one more thing, before you go.

This never asks you to invent. A room with nothing to say comes back as exactly that — nothing surfaces, the space reads as built, move through — and that result satisfies the gate as honestly as any other. The requirement is that you looked, not that you found. Run it on rooms that are scenes: the chamber, the vault, the cell, the shrine. Do not run it on corridors and connecting stone — a passage you are only crossing is not a room that speaks. And keep the framing soft: one more thing, never locked in.

One discipline holds the mode together. Each room Commit feeds the dungeon clock the way any local Commit feeds the level above it — but World Pressure moves only when a room actually shifts the session’s arc, not once per door. Feed the macro clock at every threshold and a long crawl will detonate it by footstep, with no story behind the bang. Spend the room beats locally; let the arc rise only when a room earns it. Played this way, every room hands back something the dungeon book never wrote — a fear, a wrongness, a cost — and the crawl gets the interiority it was missing without ever feeling like a toll.

Hex Crawls

A hex crawl is a dungeon turned inside out — the structure is procedural geography, the encounters are tables, the rhythm is travel rather than corridor. What the dungeon does for confined space, the hex crawl does for landscape. Same Lens treatment, same gap to fill.

What the hex crawl supplies is the geography (hex by hex), the encounter tables (what fires per region), the journey mechanics, sometimes set-piece locations. Each hex is mostly empty until the table fires; the table fires; the encounter happens; the journey continues.

What you bring is a character, a journey, and awareness that you supply how the miles feel. The hex crawl will not tell you what the empty mile feels like to a character who has walked seven of them. You will.

What Lens supplies is the traveller’s perspective on the geography, gut on the village that comes into view too quiet, pressure as the journey extends past the character’s reserves. Lens reads the texture between encounters — the mile that is just a mile, but in this character’s exhausted state, the mile that doubles.

Prep. Know the hex crawl’s structure, your starting hex, your character’s resources for the journey. Select a Palette that fits the geography’s register — viking-age saga, dark-caribbean, weird-frontier — whichever matches the world the hex crawl builds.

Ignition — short form. The hex crawl supplies the situation: you are travelling, here is where you started, here is where you are going. Hook from your character + the journey’s stakes; Aim from the destination or the survival; Friction from the geography and the encounter tables; Stake from what the character personally loses if the journey fails; Stage from the starting hex’s described terrain.

The first Pressure Clock. Can I reach the village before the storm closes the pass? 0/5. Can I cross the moor without the thing in it finding me? 0/4. Sized against the journey’s length. World Pressure runs alongside, sized to the whole journey’s arc.

The first Lens roll. The first hex’s read — the texture of the morning, the feel of the path, what the character makes of the silence or the noise or the absence of either.

Into flow. Lens rolls on what the character meets, hex by hex, encounter by encounter. The Pressure Clock fills with the journey’s weight. When it fills, the Commit Procedure runs from the visible tag record’s Dominant Tag. Encounters from the hex crawl’s tables fire as the system specifies; Lens reads the character’s gut on what shows up. Your RPG handles the encounter’s resolution if it turns to action.

Mythic-Class Oracle Play

Mythic, and the family of systems built around its model — oracle-driven generative play, where the player asks questions of the fiction and the answers compound into a session. The oracle does what your party-game GM does: it surfaces facts, decides what happens off-screen, answers the questions that move the story forward. Most of these systems also include some form of chaos management — Mythic’s chaos factor, others’ variants — which calibrates how much pressure the world is under.

What the oracle supplies is what is. Not pre-written, but generated in response to questions you ask. You start with a one-line premise; the oracle expands it; you ask questions; the oracle answers; the session forms.

What you bring is a character, a starting premise, and the understanding that the oracle and Lens complement each other rather than overlap. The oracle generates world-facts. Lens reads the character’s perspective on the world-facts. These are different jobs.

What Lens supplies is what Mythic-class systems leave out: the Commit/Belief firewall, perspective work on what the oracle surfaces, sustained character-side pressure via the Pressure Clock. The oracle tells you the door is locked; Lens tells you what the character makes of the locked door, what their gut says about it, what pressure builds while they stand at it. The oracle tells you the NPC’s general disposition; Lens tells you what the character reads in the NPC’s face.

Of all the source-types, this one most closely matches what Lens was built to complete. The oracle generates; Lens reads. Both parts of solo play are visible, both parts have their machinery, and neither asks the other to do its job.

Prep. Have the oracle ready. Have its chaos-factor mechanic ready, if it has one. Know your character. Have a one-line premise: who, where, what is pressing. Select a Palette that fits the genre your premise implies — the oracle does not flavour the L-tables; the Palette does.

Ignition — full but compressed. The oracle does not generate from absolute zero; you supply the opening premise. From that premise: Hook from your character + the implied world-fact; Aim from the situation’s pressure; Friction and Stake from where the premise is leaning; Stage from the premise’s implied setting around the character. Use Yes/No Dice — they are the oracle in its simplest form, and they integrate cleanly — for any binary the Ignition surfaces but cannot answer from premise alone.

The first Pressure Clock. Named in your character’s voice. Sized against what the premise suggests. The chaos factor or its equivalent measures the scenario’s pressure; the Pressure Clock measures your character’s pressure. Lens’s own World Pressure runs alongside both — a third track for the session-arc, sized to where you expect the story to land. They are three different objects, they run in parallel, they do not substitute for each other.

In practice, do not run all three hot at once. They are distinct, but three live countdowns is a lot to carry, and they can end up pulling one scene in three directions. Let the situation choose which one drives: when the scenario itself is volatile, let the chaos factor lead and keep your Pressure Clock small; when the beat is about your character’s nerve, let the Pressure Clock lead and let the chaos factor idle. World Pressure only needs to move when a Commit actually shifts the session’s arc. One meter carries the beat; the others wait.

The first Lens roll. After the oracle has surfaced the first concrete thing — a fact about the world, an NPC’s appearance, a place’s description — Lens fires against it. The character is reading what the oracle just produced.

Into flow. Oracle generates; Lens reads. The Pressure Clock fills through Lens rolls. When it fills, the Commit Procedure runs from the visible tag record’s Dominant Tag. The chaos factor adjusts per the oracle system’s rules; the Pressure Clock fills per Lens’s rules; the two pressures stack against each other but never inside each other. Your RPG, if you are using one alongside, handles discrete action; if you are playing without one, the oracle handles those too via expanded questions.

System and RPG Only

You have your rulebook. That is what you have. No scenario, no module, no solo supplement, no oracle, no dungeon book.

Stop.

Open the rulebook. Look for the included scenario. Almost every rulebook ships with one — a starter adventure, an introductory situation, a sample location with sample NPCs. It exists because the rulebook’s authors knew that system alone is not enough fiction to play against. Run that scenario. Treat it as a module per the module flow earlier in this chapter. That is by far the lowest-effort way to satisfy what Lens needs from you.

If you have read your rulebook cover to cover and you are certain there is no scenario: build the minimum yourself before opening Lens. Write three sentences. Where is the character? What is pressing on them? What do they want? That is enough — three sentences is a Hook waiting to be sharpened. Ignition runs against it.

What you supply is the entire minimum-viable triad: a character with detail, a setting with at least one fact, a system register that tells you what kind of fiction this is. Lens cannot supply any of these for you. Lens does not tell you what is. If you bring nothing, the engine will produce dice rolls you have to author meaning into — and that is not Lens running, that is you ghost-writing with dice scaffolding. The book learned this from playtest.

The flow is the same once you have brought enough. Three sentences is enough.

Prep. Open the rulebook to the scenario. If no scenario: write the three sentences. Build no further until they exist. Select a Palette that fits your character + setting + system register; if none of the six drafted fit, the appendix’s structure shows how to build one.

Ignition — full form. You are sourcing everything. Hook from character + setting; Aim from situation; Friction from what is in the way; Stake from what is personally lost; Stage from what is around the character; Opening Beat from where they stand in the first moment. This is the case Sam runs in Chapter 2 — full Ignition, every part sourced, no module to read off.

The first Pressure Clock. Named in your voice. Sized against what your three sentences (or starter scenario) suggest. Set World Pressure too, sized to where you expect the situation to break.

The first Lens roll. The first concrete moment your character meets in the situation you set up.

Into flow. Same engine. Same RPG boundary — your rulebook’s resolution mechanics handle discrete action; the Pressure Clock measures situational pressure; Lens rolls fill the clock. When it fills, the Commit Procedure runs from the visible tag record’s Dominant Tag.

The hardest version of solo play is this one, by a wide margin. Lens does not make it easier in the prep phase — what it makes easier is everything after the prep, once your three sentences become a session that is reading itself back to you.

What This Chapter Showed You

Seven entry points. The flow that followed each was the same. What changed was what your source brought to the table, and what Lens completed in turn.

The module gave you a world; Lens gave you the perspective and the firewall. The solo supplement gave you tools; Lens gave you the depth those tools did not include. The solo-first game gave you integrated apparatus; Lens gave you the firewall it lacked. The dungeon gave you structure and zero interiority; Lens gave you the goblin in room 3 as a perspective with a gut. The hex crawl gave you geography; Lens gave you the texture of the mile. The Mythic-class oracle gave you generated world-facts; Lens gave you the character’s reading of them. The rulebook alone gave you almost nothing; you brought three sentences, and Lens ran honestly against that.

The richer your source, the lighter your work. The leaner your source, the more of the minimum-viable triad falls to you. The right pairing — and this is what the chapter has been telling you by structure rather than argument — is Lens plus a source that brings what Lens does not. Almost any source qualifies. Almost no source is wrong. Some sources make the work harder; reach for the scenario the rulebook ships with, or the supplement that came with the game, or the dungeon that came in the box. Lens is not picky about its partner. It is picky about its diet. Bring it something to read.

When you ask, in the middle of a session, which table fits this moment? — turn to the next chapter. The tables themselves are organised by what they read.

Now play.