Ruling — Nemesis: Lockdown

You asked

How do I play?

Answered counted as answered

Asked with: Nemesis: Lockdownbg-310100-en-1e

The game is played over a series of consecutive rounds, which end when any end game conditions are met.[1] Each round is split into two consecutive phases:

I: Player Phase

1. At the start of each Player Phase, all players draw cards from their Action deck until they have a hand size of 5 cards (if a deck is empty, shuffle the discard pile to form a new deck).[1]

2. The player with the First Player token passes it to the player on their left (except in the first round).[1]

3. Starting with the player with the First Player token and proceeding clockwise, each player performs a turn of 2 Actions.[1]

4. If a player cannot or chooses not to take any Actions, they must pass; if they perform only 1 Action, their second Action is to Pass.[1]

5. Once a player passes, they cannot perform any further actions for the remainder of the Phase; they may discard any number of cards from their hand and must flip their Help card to the Pass side.[1]

6. The phase continues until all players have passed.[1]

II: Event Phase

1. If there is a CSS token under the Time token, reveal it and check which CSS Pods are launched this round.[1]

2. Move the Time token on the Time track one slot to the $\text{right}$.[1]

3. Resolve the following:

* Check if the Autodestruction sequence and Alert Procedure must be resolved.[1]

* Check if Power must be reduced based on Power Thresholds.[1]

[1] RULEBOOK Nemesis: Lockdown — Rulebook · p.13 · FLoW oF THE GAME · round orDEr · i: pLAYEr pHASE · 1: DrAW ACTioN CArDS · 2: FirST pLAYEr ToKEN · 3: player turns · …

Answer in hand — your move.

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 82 ms · ask 5136 ms · total 5219 ms
single-flight (PR-5): queued 0 ms · generation 5219 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 13, "score": 0.04866, "snippet": "The game is played over a series of consecutive rounds , and ends when any of the end game conditions are met. More on Player Goals and End of the Game - see page 10. Each round is split into two consecutive Phases: I: Player Phase II: Event Phase Resolve the following steps: At the start of each Pl", "headingPath": "FLoW oF THE GAME · round orDEr · i: pLAYEr pHASE · 1: DrAW ACTioN CArDS · 2: FirST pLAYEr ToKEN · 3: player turns · …", "sharpsignalDocId": 356}, {"page": 8, "score": 0.047643, "snippet": "15] Take as many Help, Contingency and Night Stalker Reference cards as there are players and deal one to each player at random. Help cards determine the order of choosing Characters (Step 19). If there are 3 players, take the cards with number 1-3, if there are 4 players, take cards 1-4, etc. The n", "headingPath": "GAME SETup: steps 15-21, CrEW SETup", "sharpsignalDocId": 356}, {"page": 8, "score": 0.031746, "snippet": "More on Contingency - see page 11. 19] Shuffle all Character Draft cards . The players choose their Characters in the following order: Player 1 takes 2 random Character Draft cards, reveals them, chooses 1 and shuffles the other back into the Character Draft deck. Next, Player 2 chooses their Charac", "headingPath": "GAME SETup: steps 15-21, CrEW SETup", "sharpsignalDocId": 356}, {"page": 4, "score": 0.03125, "snippet": "4 4 D6 dice (2 Combat dice and 2 Advantage dice) GAME elements 1 Scanner 1 To perform any Room Action, a Character must be in the corresponding Room (unless they possess a special ability clearly saying otherwise). You cannot perform a Room Action when you are in Combat. You cannot perform a Room Ac", "headingPath": "", "sharpsignalDocId": 356}, {"page": 30, "score": 0.030769, "snippet": "While Nemesis shines as a semi-cooperative game, you can also try to survive alone. This mode has its own special Objectives deck - Solo / Coop Objectives. At the start of the game, draw two cards from this deck, instead of the regular Objective cards. After placing the Active Contingency, draw two ", "headingPath": "Solo Mode · Fully Cooperative Mode · revive", "sharpsignalDocId": 356}, {"page": 14, "score": 0.030303, "snippet": "Careful Movement - Works exactly like Movement, but instead of performing a Noise roll after moving, place a Noise marker in a chosen Corridor connected to the Room you are entering. If there is a Noise marker in all the Corridors connected to the Room you want to move to, you cannot perform a Caref", "headingPath": "out of combat · in combat", "sharpsignalDocId": 356}, {"page": 27, "score": 0.029851, "snippet": "To perform any Room Action, a Character must be in the corresponding Room (unless they possess a special ability clearly saying otherwise). You cannot perform a Room Action when you are in Combat. You cannot perform a Room Action in a Room with a Malfunction marker. Some Rooms have a Computer symbol", "headingPath": "rooM SHEET · rooms with a computer · BASiC rooMS \"i\" · EXAMINE THE ARCHivES: · Move through Technical Corridors: · initiate Autodestruction Sequence: · …", "sharpsignalDocId": 356}, {"page": 15, "score": 0.029412, "snippet": "Some Item cards allow a Character to perform specific Actions. Their description is provided on the Item cards. More on Items - see page 25. Most of the Rooms allow a Character to perform a specific Action. The description of each Room Action is provided on the Room sheet - see pages 27-29. The Comp", "headingPath": "ACTioNS FroM iTEM CArDS · ACTioNS FroM rooM TILES · Computer ActionS", "sharpsignalDocId": 356}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 13, "quote": null, "headingPath": "FLoW oF THE GAME · round orDEr · i: pLAYEr pHASE · 1: DrAW ACTioN CArDS · 2: FirST pLAYEr ToKEN · 3: player turns · …", "sharpsignalDocId": 356}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 356 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 356 boosted
answered-before recall: this ruling was answered, so past rulings were not offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
answer fence: passed — letter density 0.91358 of 1134 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 28, 2026 08:15 UTC

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. This ruling ran the THREE-ARM fuse (full-text + vector + the doc-priority boost arm, which carried the base rulebook and/or the errata corrections this query matched), whose arithmetic ceiling is 0.04918 — all three arms ranking the same chunk #1 (ceiling = arms/(k+1) at k=60). The measured healthy band 0.016–0.033 was measured on TWO-arm asks and does not bound this one: its high end is the two-arm ceiling, and a third arm has room above it. A chunk only one arm ranked highly lands near 0.016 (that one arm's #1 vote), so 0.03 here is an excellent hit, not a 3% match.

per-arm ranks (the rank each search arm gave a chunk): NOT DISCLOSED by the gateway. Fusion happens gateway-side and only the FUSED score crosses the wire, so rulesage cannot show them without a gateway change. The rank column below is the FUSED rank (position in the returned list), which is real.

token count per chunk: NOT DISCLOSED — chunk token counts are not reported on the ask path. The character counts below are of the bounded snippet/quote rulesage actually received — a real measurement of what we hold, never an estimate of the chunk.

fused rank	document	heading	page	fused RRF score	snippet chars
#1	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	FLoW oF THE GAME · round orDEr · i: pLAYEr pHASE · 1: DrAW ACTioN CArDS · 2: FirST pLAYEr ToKEN · 3: player turns · …	p.13	0.04866 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#2	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	GAME SETup: steps 15-21, CrEW SETup	p.8	0.047643 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#3	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	GAME SETup: steps 15-21, CrEW SETup	p.8	0.031746 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#4	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)		p.4	0.03125 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#5	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	Solo Mode · Fully Cooperative Mode · revive	p.30	0.030769 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#6	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	out of combat · in combat	p.14	0.030303 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#7	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	rooM SHEET · rooms with a computer · BASiC rooMS "i" · EXAMINE THE ARCHivES: · Move through Technical Corridors: · initiate Autodestruction Sequence: · …	p.27	0.029851 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300
#8	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	ACTioNS FroM iTEM CArDS · ACTioNS FroM rooM TILES · Computer ActionS	p.15	0.029412 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	300

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

candidate pool: the answering read scored 80 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	FLoW oF THE GAME · round orDEr · i: pLAYEr pHASE · 1: DrAW ACTioN CArDS · 2: FirST pLAYEr ToKEN · 3: player turns · …	p.13	#1	0.04866 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	2) Contamination check: · 3) objective check: · Ending the game before the other players	p.12	#18	0.014286 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#3	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	playing with intruders · Setup · Discovering intruder Weakness	p.32	#10	0.02623 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + full-text	the re-ranker chose it
#4	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	GAME SETup: steps 1-14, board setup	p.6	#17	0.014493 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#5	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)		p.4	#30	0.012048 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#6	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	CHArACTEr WouNDS AND DEATH · Light Wounds · DrESSiNG AND HEALiNG WouND	p.23	#34	0.011494 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#7	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	GAME SETup: steps 15-21, CrEW SETup	p.8	#3	0.031746 (healthy, below this ruling's 3-arm ceiling 0.04918 (the measured band 0.016–0.033 was taken on two-arm asks and does not bound a 3-arm one))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	vent out:	p.28	#32	0.011765 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Nemesis: Lockdown — Rulebook (corpus doc 356)	FLoW oF THE GAME · round orDEr · i: pLAYEr pHASE · 1: DrAW ACTioN CArDS · 2: FirST pLAYEr ToKEN · 3: player turns · …	p.13	no quote on the wire

generation — timing and the path taken

timing split: retrieval 82 ms · first delta 3452 ms · total 5219 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 0 ms · retrieval 82 ms · ask 5136 ms · gateway work 5219 ms · total 5219 ms
tokens in (the prompt the answerer read): 4172
tokens out (what the answerer generated): 342
tok/sec: 200.2 tok/sec — 342 output tokens in 1.708 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 8s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 8s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
stream path: streamed — the gateway pushed at least one accumulated draft
watchdog: first-token watchdog: 30s per arming window (rulesage.table.first-token-watchdog-seconds), re-armed once by the passages frame — so the worst case before a reader falls back to polling is 60s. Whether it actually fired is a BROWSER-side decision that never reaches the server, so it is not recorded here. The stream path above is the server's half of that story: whether a delta was emitted at all.
num_ctx · think posture: both are the CHILD's settings, not rulesage's, and no ask reply carries them — an answer never states which context window or think posture produced it. The live-seat line above reads them from the running child instead, where the gateway can answer for itself; it describes the child NOW, not this ask.

disposition

outcome: ANSWERED — Answered
abstain rationale (n/a — this ruling answered): answered — no abstain rationale applies

setup-shape — why the checklist band did or didn't render

decision: NOT_SETUP_SHAPED — no setup-shape pattern matched this question

errata registry — what the gate above had to match against

this game registers NO errata cards (edition 285), so "no registered errata card matched" above could never have matched one

Errata scope: the gate above matched this ruling's own edition only. When an ask also reads an expansion, that expansion's own registered errata cards stay outside the match — a stated phase-1 limitation, not a failed lookup.