Archived first design (v1, August 2026) — the current Lens site is here.
LENSSolo Roleplaying Engine

Chapter 4 — Pressure

“I knew that sound well too. It was the beating of the old man’s heart. It increased my fury, as the beating of a drum stimulates the soldier into courage.”

— Edgar Allan Poe, The Tell-Tale Heart

You’ve been marking Beats on your Pressure Clock since the first roll. Now let’s find out what they’ve been building toward.

The Pressure Clock doesn’t track success or failure — your RPG handles that. When Can I cross the river? (0/3) fills, Lens doesn’t decide whether you cross. Your RPG does. Lens tracks the pressure that accumulated while you were trying. Every Lens roll adds to it. Conflict Tags stack. A pattern forms. And when the clock fills, that pattern becomes a fact the world can’t take back.

Pressure has three tools.

The Pressure Clock fills as you act. Each Lens roll adds Resistance — until the clock fills and the world Commits to an unavoidable change. This is where uncertainty and escalation come from.

The Pressure Card records every Commit — world state changes that are now true — and your character’s Beliefs about the situation. When confrontation arrives, the Card tells you exactly what position you’re in.

World Pressure advances every time a local clock fills. It’s your confrontation timer. When it fills, the crisis arrives — whether you’re ready or not. This is where timing comes from.

Together, they turn your starting situation into a game that pushes back.

The Pressure Clock

Pressure builds, peaks, and releases. Lens calls this the Pressure Cycle.

And then pressure builds again.

Lens measures building pressure as a clock — the Pressure Clock. It’s a label and a counter: a name for what’s at stake right now, and a row of empty boxes that fill as pressure builds. Each build is one Resistance Beat, hereafter: Beat. Three Beats fill a size-3 clock. When the clock fills, the world Commits — something changes, on screen or off, and the situation is different from that moment forward.

The clock you already have

You don’t create your first clock here. You created it in Chapter 2, at the end of Ignition, and it took its first mark on your first Lens roll in Chapter 3. It is already named, and it is already a question. Can I get the Sword out of Reims before sunrise? 0/4. This chapter is about what that clock does as it fills, and what happens when it does.

The clock name is a question, in the character’s voice — the form you set in Ignition. Not Get through the locked door but Can I get through the locked door? Not Find what’s hidden but What’s hidden in the chamber? Chapter 2 gave you the reason the name is a question and not a label, and that reason still holds. What matters here is what the question does once the clock starts filling: it stays open until the world answers it — and a Commit is the world answering it.

Sizing the clock

Size is how many Beats the clock holds before it fills and the world Commits. Local clocks run 2–8, default 4. Most scenes land at 3–6.

Social and investigative play sizes differently, because its pressure arrives in single Beats. Give it room: a single negotiation, audience, or confrontation runs well at 4–5; a social or political arc across scenes wants 6–8, or chain shorter clocks; a scene of investigation sits at 4–6, and leans on the rule that a filled clock never dead-ends.

Size Pacing Use for
0/2 — Volatile Explosive. Commits almost immediately. Ambushes, panic scenes, short tactical bursts.
0/3 — Tight Quick but earned. Two or three actions and the world commits. Dashes, short encounters, fast investigations, time-critical windows.
0/4 — Default Clear rhythm with room for consequence. The standard starting point. Most scenes. Start here unless you have a reason not to.
0/5 — Deep Slow burn. Dominant Tags have time to emerge clearly. Long investigations, richer social arcs, sustained infiltrations.
0/6 — Epic Heavy and deliberate. Commits feel major. Campaign-scale scenes, long arcs, major set-piece sequences.
0/7–0/8 Extended. Use sparingly. Rare. If you want 9+, chain clocks instead of inflating one clock.

Your Turn. Look at the clock you carried in from Ignition. Is it sized right for the scene in front of you — a quick window, a normal scene, a long sustained sequence? Resize it now if it isn’t: ________________________? 0/Size

Naming a clock well

When a clock fills, its Commit usually hands you the next one (we’ll get to chaining). When you name that next clock — or sharpen the one you have — the rule is the same one Ignition used: name it from what the character is driving at, not from the next action, and not from the room.

Can I pick this lock? is an action wearing a question mark. It resolves the instant the lock opens, and you need a new clock immediately. Can I get to the ledger before the watch does? is a threshold. It bends across scenes — the lock, the corridor, the guard who wasn’t supposed to be there, the choice of whether to run. The geography keeps changing; the want doesn’t. That clock carries further because it’s built from the character’s driving want, read off the whole Ignition statement — the Aim, tempered by what stands in the way and what it costs — not from the bare objective.

Canon Aim: steal the Silver Sword. Bare, that’s an action. Read against the Friction and the Stake, the want underneath it is get out of this city alive with the thing I came for — and the clock that carries the session is Can I get the Sword out of Reims before sunrise? Scope scales with the want. A tight want gives Can I get inside? A campaign-sized want gives Can I rescue my patron? Same rule at every scale: phrase the character’s want as a question, and let the world spend the whole clock answering it.

Calibrating for lighter games

The default Pressure system assumes stakes, consequence, and escalation. That suits most adventure play. If you’re running something cosy, comedic, or low-stakes, two dials adjust it without breaking it.

Size clocks bigger. A size-6 or size-8 clock gives the fiction room to breathe. Pressure accumulates more slowly; moments have space to be funny, warm, or strange before the world Commits. You’re not reducing pressure — you’re giving it a longer runway.

Let Commits be complications rather than crises. A Commit is a world-state change, not necessarily a disaster. The cake burned. The rival showed up at the festival. The rain started during the outdoor wedding. The letter arrived at the worst possible moment. The Commit makes the next scene harder, narrower, or more complicated — it doesn’t have to make it dangerous.

The system still works. Clocks still fill, World Pressure still advances, confrontation still arrives. The weight of what arrives ranges from catastrophe to inconvenience, depending on the game you’re playing.

The eight Conflict Tags are tone-neutral. Threat in a horror game means something hunts you. Threat in a pastoral game means the ward wandered too far from the path. The tag names don’t change. The fiction they generate does — shaped by your genre, your palette, and the Golden Question.

Filling a Pressure Clock

Clocks fill through Beats — units of resistance that accumulate as you push against the world. Each time you roll Lens you get a Conflict Tag and a Resistance value: +1, +2, sometimes more. That’s how many Beats you add.

Example. Your clock is Can I get through the locked door? 0/4. You roll Lens and get [Exposure +2]. Two Beats: 2/4. Next roll, [Pressure +1]: 3/4. One more Beat and the world Commits at 4/4.

What if you get +2 at 3/4 and reach 5/4? The clock simply fills. Excess Beats are ignored — a +2 on a clock at 3/4 fills it and does not carry a spare Beat to the next clock. The world Commits, you write the Pressure Card, and the next clock starts at zero.

And a quiet roll is not a wasted one. A low, flat read — nothing here, the room is what it seems — still adds its Beat. The pressure built while you looked; the turn was not spent for nothing. Calm results move the clock as surely as loud ones.

What Lens rolls do for the clock

Chapter 3 taught the Lens roll: the Impression (the world through the character’s eyes), the Impulse (the world having an opinion about what to do next), and the Conflict Tag (the mechanical acknowledgement that the world has teeth). For pressure purposes, what matters is this: every Lens roll adds Resistance to your clock, and over the course of a clock the Conflict Tags accumulate into a pattern that shapes the Commit.

Lens and your RPG

Lens is a pressure and perception system. It is not a dice-resolution system. The dice live in your RPG.

A Lens roll is complete in itself — Impression, Impulse, Conflict Tag. It doesn’t trigger an RPG roll. But the fiction a Lens roll creates may contain something that warrants resolution. If the Impression surfaces a guard turning a corner, a trap clicking, a searchlight sweeping, the fiction now holds a discrete, uncertain moment. Your RPG handles that — Stealth check, spot hidden, Reflex save. That roll answers a question the narrative asked, not a question Lens asked.

Many Lens rolls produce no RPG roll at all. The Impulse says move along the wall, stay low. You move. Pressure ticks. The story advances. Other rolls surface something concrete, and your RPG earns its roll because the fiction demands it.

The clock and the RPG roll are independent. Resistance accumulates on the clock regardless of whether an RPG roll happens, and regardless of whether it succeeds or fails. The clock measures the pressure of being in the situation. The RPG roll resolves a specific event inside it. They run in parallel, not in sequence.

Hard stops. If your RPG roll creates a hard stop — captured, alarm unquestionably raised, knocked out, environment collapses — treat that as the situation committing. Fill the current clock immediately and go to the Commit procedure.

Stop and check after every Lens roll. Add the Resistance. Read the total. Is it full? If yes, stop. Commit before the next action. The check happens before you narrate, not alongside it.

A common error: missing a filled clock because you’re tracking it in your head while reading the result, narrating the fiction, and choosing what to do next. The fix is mechanical. After every Lens roll: read the tag, mark the clock, check the total, then narrate. That sequence keeps the world honest. If you realise after the fact that a clock filled earlier and you missed the Commit — stop, and run it now. The Card is the world; if it should have changed, change it.

When a Clock Fills: Commit

When your Pressure Clock fills, the world Commits. Play stops building and something solidifies — one truth becomes unavoidable. You state it, and the fiction changes. A Commit is not a reward and not a punishment. It’s a consequence of pressure. The world has been pushed, and now it pushes back in a way that can’t be ignored.

A full clock isn’t success

This is the rule most likely to trip you up, so it’s worth being direct.

Can I get through the locked door? 4/4 doesn’t put you through the door — your lockpicking check did that two Beats ago. The clock filling tells you what the world does in response to the pressure that built while you were in the situation. Those are always separate. An RPG roll does not add Beats — only Lens rolls do. Whether your Stealth check succeeded or failed makes no difference to the clock. Lens sets the pressure. Your RPG resolves the action.

The Commit Procedure

Look at the Conflict Tags you rolled while filling the clock. The tag that accumulated the most Beats is the Dominant Tag — it tells you the shape of the world-state change. Mostly Exposure: the Commit looks like being noticed, spotted, cornered. Mostly Cost: something has been spent, closed, lost. Two tags of the same name add together — Exposure +2 and Exposure +1 count as Exposure (3). The Dominant Tag doesn’t decide for you; it points you in a direction.

You only ever have one Dominant Tag. If two tags tie at Commit, the dominant one is the most recent rolled. Read the Commit through that tag. The earlier tag is already on the Card from when it was rolled — it remains part of the situation, but it does not shape this Commit.

Determining the Dominant Tag.

Then ask: what just changed in the world? The change can be on screen — something the character sees, hears, experiences — or off screen — a patrol repositioning, reinforcements arriving, a door locked behind you, an NPC deciding something the character doesn’t know yet. State it as something concrete:

The test: does this Commit make the next clock harder, narrower, or more urgent? If yes, you’ve Committed.

When the clock asked a question and the answer is no. An interrogative clock makes this cleaner, not harder. Who killed Marian? 0/4 can fill without you knowing who killed Marian. When a clock fills and you still don’t have the answer it asked for — the search turned up nothing, the contact wouldn’t talk, the evidence didn’t add up — the Commit gives you a Lead and a Consequence. You learn something that points forward, and you pay a price for the time it took. Lens does not produce dead ends. The question form sharpens this: the Commit is the answer the world gives — usually “not yet, and here’s what it cost you.” A filled clock always moves the fiction, even when it doesn’t give you what you wanted.

Your Commit writes your next clock

The world-state change that just landed is the pressure your next clock builds against. One clock’s Commit becomes the next clock’s problem — that’s how clocks chain, and how a single problem can carry an entire session.

Set the next clock at the moment of Commit, not at the next Lens roll. When a clock fills, name and open the next one immediately, and name it the same way — as a question, from the character’s want. The character is still in a pressured situation; the next threshold is already forming, and the Commit usually tells you what it is. An active clock is the default during pressured play. Rest is a clock at rest, not the absence of one; you close a clock outright only when its thread is wholly done.

Sometimes the Commit doesn’t obviously point to a next clock. Three options. If a new threshold is pressing — a new obstacle, question, or danger created by the Commit — name it as a question and start a clock. If the situation has fundamentally changed and nothing from the original still applies, re-ignite: return to Chapter 2 and run Problem Setup and the Opening Beat from your new position. If no pressure presses right now — the character is safe, the immediate problem resolved cleanly — you do not force a roll; you narrate and play your RPG. But the clock does not go away. Lens is always on: the clock is the standing question above your play, and in calm it simply waits, barely stirring, until something is worth a read again. You never switch it off or decide whether to keep one — you always have a clock, and when it fills you name the next.

Ending mid-clock

Sessions can end mid-clock. Sometimes the fiction reaches a natural pause before a clock fills. Don’t force a Commit to tidy the state. The clock and the Card carry into the next session. A forced Commit at session end produces a world-state change the fiction hasn’t earned and a Belief that wasn’t formed by anything the character experienced. The Card holds the position; next session resumes from exactly where you left off, with the clock at whatever total it reached. Trust the clock to fill when it fills.

Turn Spark

When the clock fills you know something changes. The Dominant Tag tells you the pressure type. Turn Spark tells you the shape of the change. If the Commit is already obvious from the fiction, skip Turn Spark and state the world-state change directly.

Combine the Dominant Tag with the Turn Spark. Exposure + Revelation: someone saw you and a hidden truth surfaced. Threat + Commitment: the danger landed and your options collapsed to one. If the result feels abstract, roll the Sensory Hook prompt (Quick-Detail A) — Aspect / Verb / Descriptor — to make it concrete.

d6 Type Description
1–2 Commitment The situation narrows. Options close. What was uncertain is now fixed — you’re locked in.
3–4 Escalation Pressure intensifies. The Commit doesn’t just land — it raises the stakes for what comes next.
5–6 Revelation A hidden truth surfaces. Something you didn’t know becomes true in the world.

The Pressure Card

Everything that solidifies goes somewhere: the Pressure Card, or “the Card.” Any notepad works; index cards work well. Solo play can dissolve into vagueness. Did you already talk to the guard? Did the ward fire or not? Is the checkpoint there or isn’t it? The Card is concrete, permanent, inarguable.

What goes on the Card

Every time a Pressure Clock fills, you record two things — and they come from two different places. This distinction is the whole chapter; get it right.

The Commit — what changed in the world. This is system-derived. The Dominant Tag and Turn Spark shaped it; you state it, but the system pointed at it. It is always a fact. It happened. It’s real. On screen (the character experienced it) or off screen (the world shifted where the character can’t see) — either way, true.

The Belief — what your character thinks is true right now. This is player-written, and nothing in the system hands it to you. No table emits a Belief. No die generates one. You write it, from what the character experienced through the rolls — what they read, even wrongly, from what was in front of them. Sometimes the Belief matches the Commit: the character saw what happened and understood it. Sometimes it doesn’t: the Commit was off screen, or the character misread it, or has no idea anything changed. “Nothing has changed” is a valid Belief, and often the most dangerous one.

Examples. After Can I find the ledger? fills:

After Can I reach the ledger before they do? 0/3 fills:

After Can I get clear before the watch closes? 0/4:

Notice the gap in that last one. The Commit says the watch has sealed the exits and is sweeping inward with a list of names. The Belief says Kael thinks he can still slip out quietly if he’s fast. That gap is where the game lives. Kael makes his next decision from the Belief — speed, quiet, the gap in the cordon. The world responds from the Commit — sealed exits, a closing sweep, the network already on a page. The collision is the scene he doesn’t see coming.

The discipline: one question, asked first

Beliefs aren’t ratifications of the truth. They’re a record of how the character read the situation, given what they actually perceived. If the character read it wrong, write the wrong read. If the character read it right, write the right read. Either way, the read has to come from the fiction the rolls produced — not from your prep notes, not from the scenario, not from a detail invented after the fact to make the Belief sound clever.

So, before you write any Belief, ask one question: Could the character have known this from what they actually saw, heard, or rolled? If yes, write it. If no, you’re retconning. When in doubt, write the smaller Belief — a Belief that just matches the Commit and stays honest about the character’s read is always safe. Beliefs don’t have to be wrong to be interesting. They have to be true to what the character experienced, even when that experience is incomplete.

You’ve been holding this line since your first Lens roll. The Golden Question keeps the player’s knowledge out of what the character perceives; the Belief test keeps it out of what the character concludes. One firewall — character experience over player knowledge — at a later and louder moment. At the first roll it kept a single Impression honest. Here it keeps the whole Pressure Card honest, and the stakes are larger: a contaminated Belief doesn’t spoil one roll, it poisons every later scene that reads off the Card.

The example below is that one question, failed and then passed.

Example: Kael and the Failed Belief

Go back to Kael’s first clock — Can I find the ledger?. In Chapter 3 the Lens roll surfaced something tuned in the wood above the latch, a chill in the metal his hand wouldn’t shake, and a gut that said slow down — this is built for haste. Kael Resisted that pull. He told himself it was nothing — the old paranoia, teeth seen in a hinge again — and he drove his hand to the latch at exactly the speed the thing was built to punish. The clock entered Chapter 4 at 3/4 — [Threat +2] from the roll, +1 for the Resist — and the next Lens roll into the moment landed [Exposure +2]. Those two Beats took the clock from 3/4 to 4/4, the world Committing as the steel released. Now Kael’s player writes the Belief.

The Belief goes wrong

The player has read the module. He knows the latch is trapped — a spring-loaded blade, set by people who built this house expecting betrayal. The temptation is to write a Belief that gives Kael that knowledge. So he writes: Belief: There was a blade in that latch. I felt it go as I moved — it nearly had me. They trapped the door; the rest of the house will be worse.

Nothing Kael concluded told him there was a blade, or a spring, or a builder who expected betrayal. The Lens roll gave him a wrongness and a memory and a pull to slow — and he dismissed all of it. He went through telling himself it was nothing. The player put the trap into Kael’s certainty because the player read the module. Three things went wrong.

The fiction was retconned. A conclusion entered Kael’s read that he never reached. He didn’t register a blade going past — he registered nothing, because dismissing it was the whole point of the moment.

The Belief came from player knowledge, not character experience. The roll surfaced an unease; Kael overrode it. The module told the player what the unease was. It never told Kael — Kael decided it was nothing and acted on that.

The Hitchcock gap collapsed. A Belief that knows about the trap erases the gap the split exists to create. If Kael believes the door was trapped, there is nothing left for him to be wrong about, and nothing for the rest of the house to spring on a man who thinks he’s already paid.

What the Belief should have been

The Belief comes from what Kael experienced and concluded: a flicker of the old instinct, talked down; a hand driven fast through a doorway; a doorway that, as far as he let himself notice, held nothing. His honest read:

Belief: I did it again — teeth in a hinge, and there was nothing. I’m through. If I move fast I’m at the ledger before anyone reacts.

That’s wrong, in the way that makes the game work. The latch was real; the thing he talked himself past had a blade in it; and the speed he chose to prove he wasn’t afraid is exactly what the trap was built to catch. But Kael has no way of knowing that — he made the dismissal himself, and the Belief reflects the read he actually committed to. The gap between Commit (the trap fired; the door was exactly what his gut said) and Belief (it was nothing, I’m through, move fast) is now alive — and it’s the same Belief you’ll watch go on the Card in Kael Plays Pressure, because the discipline produces it.

That’s the test, in action. Kael didn’t conclude there was a blade — he concluded there was nothing and overrode the instinct that said otherwise — so the blade doesn’t go in the Belief, however much the player wants him forewarned. The player keeps the knowledge. Kael keeps the read he actually made.

The Card as Oracle

When you’re mid-session and wonder “Do they know who I am?” or “Is the exit still clear?”, check the Card.

Where you stand when the crisis arrives is determined by the Commits. How prepared you feel is determined by the Beliefs. The gap between them is the tension.

Your Turn. Get your Pressure Card ready — a notepad, an index card, anything you can write on. You’ll be recording Commits and Beliefs on it as you play.

World Pressure

Your Pressure Clock measures pressure on what you’re doing right now. World Pressure measures pressure on your game.

Without a mechanism that tightens the situation, the player can wait, retry, negotiate forever. World Pressure is the answer — a confrontation timer that advances regardless of whether you succeed or fail. It’s a track running in the background. Set a limit based on how long you want the scenario to run. Every time a local clock fills, World Pressure advances +1. When it hits its limit, confrontation arrives.

It is the same object, one level up. A local clock fills from Lens rolls; World Pressure fills from local clocks. Each time a local clock Commits it advances World Pressure by one — and that Beat carries the local clock’s Dominant Tag, so World Pressure builds a tag record of its own from the dominant pressures beneath it. When World Pressure fills, it Commits by the procedure you already know, and its Commit can feed a clock above it in turn. Everything in Lens is a Pressure Clock; World Pressure is simply the largest one you are running, and you may stack a further level above it — a campaign, a saga — whenever the game wants the reach.

One detail carries up cleanly. If a local clock Commits with no Dominant Tag left in its record, it still advances World Pressure — but as an untagged Beat: it moves the clock above without shaping it, exactly as a Resisted Beat fills a clock without entering the record.

Scenario length Size Pacing Notes
Quick one-shot 0/4–0/5 Urgent. Four to five clock fills to confrontation. Short evening sessions, convention games, diagnostic scenarios.
Standard session 0/6 The default. Six local clock fills to confrontation. One-shots, single-session modules, first sessions with Lens.
Full module 0/8–0/10 Extended arc. Room to explore before the crisis bites. Multi-session adventures, longer published modules, campaign chapters.
Campaign arc 0/10–0/12 Long haul. Many problems resolved before the world forces the issue. Full campaign arcs, mega-dungeons, sandbox play with a looming threat.

How World Pressure advances

Every time you fill a Pressure Clock, World Pressure advances +1. It doesn’t care whether your goal was a success or a failure. It measures how close you are to confrontation. Every clock you fill tightens the net. Choices narrow. Stakes rise.

Why sabotage still advances World Pressure. You might wonder: if I sabotage the opposition, shouldn’t that slow it? No. World Pressure doesn’t measure enemy progress. It measures how close you are to confrontation. By acting against them, you don’t buy time — you force a reaction. The world tightens because you pushed it, not because you failed.

When World Pressure fills: Confrontation

When World Pressure hits its limit, confrontation arrives. Not because you lost — because time’s up. The situation forces itself to a head.

Read your Pressure Card. The Commits tell you what’s true in the world. The Beliefs tell you what your character thinks is true. The gap between them is about to close — violently, quietly, or catastrophically, depending on what you’ve built.

If you’re playing a published module, you probably already know the shape of the confrontation. The module’s big threat — the villain, the ritual, the betrayal, the siege — is what arrives. The Card tells you what position you’re in when it does. If the module says the antagonist makes their move, World Pressure filling is that moment. The Commits determine whether you’re ready. If you’re not playing a module, the Commits point you toward the confrontation; they have a direction. The shape of the crisis is already on the Card — you’ve been building it, clock by clock.

One line holds above all of this: Lens never moves a timeline the fiction has already fixed. When a module pins its climax to a calendar — the vote on the third day, the duel at dawn, the tide that will not wait — that scheduled event is the confrontation, on its own schedule, whatever World Pressure reads when it comes. There, World Pressure is not the trigger but the gauge: it tells you how heavy your position has grown by the time the hour arrives, and you do well to size it to land near that hour. Where the fiction fixes no such hour, the Stake is your off-ramp — confrontation comes when the Stake falls due. Either way the clocks escalate toward the crisis; they never reschedule it.

Return to the stake you set at the start of the session. This is what’s at risk. Resolve the confrontation using your RPG. When it ends, don’t clear the Card. What’s on it is now the world. If the Stake is spent, a new one will have emerged from what just happened. Your next session starts here, from exactly the position you built.

Your Turn. Set your World Pressure. Check the sizing table. How long do you want this scenario to run? Write it: World Pressure 0/___

Kael Plays Pressure

You’ve seen every piece. Now watch them run together — on the scene Chapter 3 left open.

Kael’s player has read the module. He knows the safe house was built by people who expected betrayal, and that some of its doors were reinforced, repaired, and trapped. He knows the latch under Kael’s hand is one of them. He knows the ledger matters and that the watch are coming back before dawn. Kael knows almost none of this. He knows there is a door, a latch, a mark in the wood, and a corridor that has been too quiet. He knows himself — a thief who has stayed alive by reading small signs, and who has wasted as much of his life seeing danger in dirt and bad carpentry. Chapter 3 ended on the fork: the Lens roll surfaced something tuned in the wood, a wrongness in the cold metal, a gut that said slow down. Kael Resisted. He told himself it was nothing and put his hand to the latch.

Kael’s player knows the latch is trapped. Kael has just told himself it isn’t. That’s the bomb under the table.

He sets World Pressure for a tight one-shot infiltration.

World Pressure 0/4

Clock 1: Can I find the ledger? 3/4 — [Threat +2]; +1 Beat (Resist, untagged)

This is not a new clock and it does not arrive as a bare number. Kael carried it from Ignition; it took its marks in Chapter 3. The record is on the Card already: the Lens roll at the latch was L11: Hidden Mechanism — 7, SOMETHING TUNED, First Sign Temperature, Impulse I’ll slow down. The thing is built for haste. That roll put [Threat +2] on the clock — two Beats. Kael Resisted the Impulse, which adds one more Beat. That Resist Beat is not a tag; it fills the clock but it does not go in the tag record. So the clock stands at 3/4, and the only tag on it is [Threat +2]. One more Beat and the world Commits.

Hold that asymmetry, because it is the rule and the chapter will lean on it: tagged Beats feed the Dominant Tag; the Resist Beat fills the clock but never the tag record. Kael’s clock is at 3/4 from three Beats — but only Threat is written on the Card.

The next Lens roll. Kael’s hand is on the latch and his weight is going forward. The mechanism his gut flagged — and he dismissed — is still live; nothing has resolved it. That is a pressured moment, so Lens fires. The table is still L11: Hidden Mechanism — the hidden thing has not become known; it has become imminent. Sam does not re-use the Chapter 3 result; this is a new roll on a moment that has tightened.

L11: Hidden Mechanism — 8, WAKING SOMETHING. First Sign d6: not needed; the moment is concrete enough.

My probing has surfaced me to whatever’s here. The check itself is the trigger now.

Impulse: I’ll step back. I’ll stop feeding it.

[Exposure +2]

The tag is [Exposure +2] — Lens’s second tag on this clock, joining the [Threat +2] from Chapter 3. Two Beats on a clock at 3/4: it fills. Can I find the ledger? 3/4 becomes 4/4 — the world Commits.

Now the fiction holds a discrete, uncertain thing: Kael’s hand is committed to a latch that is about to do what it was built to do. That is an RPG question, and only an RPG question. Kael’s game resolves whether his body can arrest a motion already underway — a Reflex save, a Dexterity check, whatever that game uses. The save fails by a hair. A thin steel tongue snaps from the jamb. It does not fill the clock and it does not cause the Commit — the Lens roll already did that, the moment its [Exposure +2] took the clock to 4/4. The RPG roll only resolves what the firing does to Kael’s body: the blade scores the wood where his wrist was, and misses flesh by the width of the hesitation he didn’t take.

Kael’s First Commit. Read the visible record: tags on the clock are [Threat +2] (Chapter 3) and [Exposure +2] (the filling roll). Tied at 2. Most recently rolled is [Exposure +2] — Exposure Dominant, derived from the Card. State the world-state change through Exposure:

Look at the gap. The Commit says the trap was real and it fired — Kael’s wrist is intact only because the housing was a fraction slow — and the sound of it landed in a house designed to listen. The Belief says Kael got through nothing — that he talked down a ghost again, the way he always does, and now he should move fast. Nothing he let himself perceive contradicts that read; dismissing it was the whole of what he did. That Belief is the most dangerous sentence on the Card, and the discipline produced it: it is exactly the Belief from the Failed Belief example, because Kael made the same dismissal both times. World Pressure advances: 1/4.

Clock 2: Can I reach the ledger before they do? 0/3

The Commit writes the next clock. A trap fired — quietly, but it fired, and a sprung trap in a careful house is the kind of thing careful people notice. The threshold is no longer find the ledger; it is get to it before the house turns over. Kael doesn’t frame it that way — he thinks he’s clear and moving. The Card frames it. Sam sizes at 3 — tight, urgent.

Beat 1 — L2: Crossing a Threshold. Kael crosses out of the corridor and into the ledger room itself — a genuinely new space, entered for the first time. L2 fires on the arrival.

L2: Crossing a Threshold — 4. First Sign d6: 3 — Movement.

Something here was already underway before I crossed in.

Impulse: I’ll fall into step and learn the rhythm before I break it.

[Pressure +1]

Through Kael’s eyes: the room is not asleep. A lamp wick still curls smoke; a chair sits angled from the desk as if pushed back a moment ago. Movement — the First Sign — puts the wrongness in the timing: someone was here, working, and stopped. He does not know it was the sound of the latch that moved them; he reads recently active, not I was heard. The Impulse says don’t freeze, move with it. He follows, easing along the wall. No RPG roll; nothing discrete to resolve. One Beat. 1/3.

Beat 2 — L2 again? No — L8: Under Watch. Out in the house, the watching becomes a present pressure: a door opens somewhere behind and below, then another, in a rhythm. L8 fires.

L8: Under Watch — 6, FOLLOWED DELIBERATELY. First Sign d6: 2 — Movement.

Tail confirmed. No effort to hide it.

Impulse: I’ll keep walking. I won’t give them the reaction.

[Exposure +1]

Kael’s game has nothing discrete to resolve — no one is in the room with him; the pressure is the pattern, not a person. The Resistance goes on the clock. One Beat. 2/3.

Beat 3 — L2: Crossing a Threshold. Kael moves to the inner door of the ledger room, the way deeper. A new threshold.

L2: Crossing a Threshold — 7, NO WAY BACK. First Sign d6: 6 — Absence.

The way behind is already closing.

Impulse: I’ll move forward before it does.

[Control +2]

What hits Kael first is an absence — the corridor noise he came through has stopped, which means the search has reached it. He reads the way I came is no longer mine. Two Beats. 4/3 — the clock fills with overflow; excess ignored.

Kael’s Second Commit. Visible record on Clock 2: [Pressure +1], [Exposure +1], [Control +2]. Highest tag value is Control (2) — Dominant, derived from the Card. Turn Spark, because the precise turn isn’t obvious: d6 — 1, Commitment. Control + Commitment: the situation narrows; an option closes for good.

The Commit closes the entrance as an exit — a Control change, stated through the Dominant Tag. Kael’s Belief registers the closed route (he heard the corridor go quiet, that much he experienced) but reads it as a problem he can still outrun. World Pressure advances: 2/4.

Clock 3: Can I find the ledger before the sweep reaches me? 0/3

The Commit wrote it: the search is inward-bound and Kael’s exit is gone, so the want sharpens to get the thing and beat the sweep. Sam sizes at 3 — no room left.

Beat 1 — L8: Under Watch. The sweep’s rhythm is closer now, two rooms off.

L8: Under Watch — 4, STORY TESTED. First Sign d6: 4 — Question.

Story challenged. Details questioned. Looking for cracks.

Impulse: I’ll hold the story. I won’t elaborate.

[Pressure +1]

Off-stage, a voice in the next room is putting questions to someone — a servant, a guard, Kael can’t tell. He doesn’t know what they know; he reads they are not just walking, they are asking. The Impulse is to hold still and not improvise. One Beat. 1/3.

Beat 2 — L2: Crossing a Threshold. Kael reaches the inner cabinet where the ledger should be — arriving at the object, and at the realisation of what it means to be here.

L2: Crossing a Threshold — 5, WRONG FIT. First Sign d6: 2 — Placement.

Something here is out of place. I can’t name it yet.

Impulse: I’ll go to the thing my eye keeps snagging on and put my hand on it.

[Clue +1]

The ledger is here — but Placement makes the wrongness sit in where things are: a drawer not quite shut, a second ledger where there should be one, the dust disturbed by a hand that wasn’t his. Kael reads someone has been in this exact cabinet, recently, and not for the first time. The clue goes on the clock. One Beat. 2/3.

Beat 3 — L8: Under Watch. The sweep is at the ledger-room’s outer door. Kael lifts the cabinet’s contents; his RPG’s Stealth check fires as he moves a stack that shifts — fails. A bound spine slides and slaps the floor. That is the fiction; the RPG resolved it. Now Lens fires on the watching.

L8: Under Watch — 3, INTEREST SHARPENS. First Sign d6: 5 — Timing.

Attention focuses. Something caught their eye. Scrutiny deepens.

Impulse: I’ll give them something else to look at.

[Exposure +1]

The slap of the spine landed into a silence that was listening. Timing makes it land wrong — a half-second before the sweep would have moved past. The Impulse says misdirect. But Kael is moving fast, wound tight, a man who has decided speed is the answer. He doesn’t want to stop and divert. He Resists. The world pushes back: the [Exposure +1] tag, plus the Resist Beat — which fills the clock but, as established, does not join the tag record. 2/3 + 1 (Exposure) + 1 (Resist) = 4/3 — fills, overflow ignored.

Kael’s Third Commit. Visible tag record on Clock 3: [Pressure +1], [Clue +1], [Exposure +1]. The Resist Beat is not here — by the rule. Three tags, all +1 — tied at 1. The rule for a tie is most recently rolled — the last tag was [Exposure +1], so Exposure is Dominant, derived from the Card. Turn Spark: d6 — 5, Revelation. Exposure + Revelation: the watching resolves into a truth Kael can’t see.

The Commit crystallises the closing net and the named list — the Stake Kael set at Ignition, now mechanical on the Card. Kael’s Belief catches up by one notch (he knows the sound placed him — he heard it land) but still reads speed as the answer to a trap built to make speed worthless. World Pressure advances: 3/4.

Clock 4: Can I get out before they close on the room? 0/3

The Commit wrote it: exits sealed, the sweep converging here. The want is bare survival with the thing. Sam sizes at 3 — the last clock; one fill from confrontation.

Beat 1 — L8: Under Watch. Footsteps stop outside the ledger room’s door. The handle moves.

L8: Under Watch — 9, AUTHORITY ACTIVATED. First Sign d6: 1 — Eyes.

Power deployed. Orders issued. Resistance has cost.

Impulse: I’ll comply visibly. I’ll make the submission obvious enough that they don’t need to ask twice.

[Control +2]

Through Kael’s eyes — First Sign Eyes — it is in the way the first one through the door looks at him: not searching any more, deciding. The Impulse the table hands him is to submit, fast and visibly. Two Beats. 2/3.

Beat 2 — L2: Crossing a Threshold. Kael breaks for the only gap — a servants’ hatch behind the cabinet, half-blocked. Crossing into it is a new threshold under the worst possible terms.

L2: Crossing a Threshold — 9, HOSTILE GROUND. First Sign d6: 6 — Absence.

This place has been worked over. The damage is still in it.

Impulse: I’ll lower my profile. I’ll take a route I wouldn’t usually take.

[Threat +2]

The hatch passage is not a clean way out — Absence tells him what is missing is safety; this route has been used hard and recently, and not by friends. The Impulse is to go low and wrong-foot the expected path. Two Beats. 4/3 — fills, overflow ignored.

Kael’s Fourth Commit. Visible tag record on Clock 4: [Control +2], [Threat +2]. Tied at 2. Most recently rolled is [Threat +2] — Threat Dominant, derived from the Card. No Turn Spark; the fiction is unambiguous.

World Pressure advances: 4/4 — World Pressure fills. Confrontation arrives.

Confrontation

It arrives because the timer filled — not because a roll failed, not by authorial fiat, but because four clocks fed four advances and the fourth tipped World Pressure to its limit. That is the mechanic doing exactly what the chapter said it would. Read the Card — the full record of the position Kael built:

Every Belief sits behind its Commit, and behind it in the same direction — Kael reads less danger than the Card holds, every time, because the first dismissal set the pattern and the discipline kept it honest the whole way down. The confrontation is no surprise to the player: they watched the blade clear its housing, the corridor close, the spine hit the floor, the watch reach the door. It is a surprise to Kael, because his Beliefs told a quieter story at every step. That is Hitchcock’s bomb. The player has known it was under the table since Kael told himself the latch was nothing. Kael has not.

There is no fight here. Kael is one wounded thief in a wall passage; the watch is a sealed house and a closing pattern. The confrontation is whether he gets out — the foul route ahead, a bluff, a room they have swept and might not sweep twice — under the full pressure of a Card that says the exits are shut and his name is travelling. Lens does not resolve that. The Card set the terms; the watch is the threat the module always held; the way out, if there is one, is the kind of thing the module describes and Kael’s RPG resolves. When it ends, don’t clear the Card. What’s on it is the world. Your next session — Kael caught, Kael clear, Kael bargaining in the dark — starts from exactly the position these four clocks built.

Your Turn. Look at the clock and World Pressure you set earlier. You’ve watched Kael run four chained clocks to a confrontation that arrived because World Pressure filled — a resumed clock that filled on a Lens roll while an RPG save only resolved the wound, a Commit that wrote the next clock, tag records you could read the Dominant Tag from without being told, and a Card where the gap between what the world did and what Kael believes built a closing net he doesn’t see. Would you resize your clock? Change your World Pressure? You don’t have to — but if watching Kael showed you something about your own setup, sharpen it now.

Troubleshooting

Summary

Pressure Clock. You carried it in from Ignition, phrased as a question in the character’s voice — the threshold your actions are building toward, not the next action. Size it: 2–3 for quick moments, 4 for a standard scene, 5–6 for a longer one. For 7+, chain clocks instead.

Filling the clock. Each Lens roll produces a Conflict Tag and a Resistance value. Add the Resistance as Beats. RPG rolls do not add Beats — only Lens rolls do.

Lens and your RPG. Lens gives perception and pressure; your RPG resolves actions. Independent — Resistance accumulates regardless of whether an RPG roll happens or its result.

When the clock fills: Commit. The world commits to an unavoidable change. A full clock is not success or failure. Identify the Dominant Tag (most Beats; if tied, most recent). Roll Turn Spark (d6) if the Commit isn’t obvious — 1–2 Commitment, 3–4 Escalation, 5–6 Revelation. State the world-state change, on screen or off. When the clock asked a question and you don’t have the answer, the Commit is a Lead and a Consequence — never a dead end.

Pressure Card. Record the Commit (system-derived, always a fact) and the Belief (player-written, from character experience — accurate, incomplete, or wrong). The gap between them is where the tension lives. Test before writing a Belief: could the character have known this from what they actually saw, heard, or rolled?

World Pressure. Advances +1 every time a local clock fills, success or failure. Set the limit by how long you want the scenario to run. When it fills, confrontation arrives — read the Card; that’s the world you’re standing in. Resolve with your RPG.

At session end, read your Dominant Tags in sequence. They tell you the genre of the story you played. Clue then Threat: investigation turning dangerous. Exposure throughout: a surveillance thriller. Cost dominating: prices you didn’t budget for. You didn’t choose the genre. The dice did. The tags recorded it.

← 3 · The First Roll5 · Perspective →