You asked
How do I play?
Abstained — no grounded answer; closest passages below counted as honest abstainAsked with: Twilight Strugglebg-12333-en-1e
I looked through Twilight Struggle's rulebook and couldn't find a solid answer to that one — and I'd rather tell you so than guess at your table. Try asking it another way, or ask me about setup, turns, or how the game ends: those I know cold.
The closest rulebook passages are below — check them before ruling.
5.1 Cards may be played in one of two ways: as Events or Operations. Ordinarily, players will hold one card in their hand at the end of the turn. All other cards will be used for events or operations. Players may not forgo their turn by declining to play a card, or by discarding a card from their ha
Headline Phase: Each player secretly selects a card from their hand. Once both players have made their choice, they reveal their cards to each other simultaneously. These cards are called 'Headline cards' and their Events take place in this phase (and if the event title has an asterisk, are removed
The object of the game is to score Victory Points (VPs). Regional Victory Points are scored through geographic Influence over the six Regions. VPs can also be received through the play of certain Events. Each region has its own 'scoring card'. Playing a scoring card causes Victory Points to be score
Once all regions have been scored, victory goes to the player who has accrued most VPs. If the VP marker is on a positive number, the US wins; if the VP marker is on a negative number, the USSR wins. If the VP marker is on zero, the game ends in a draw. These rules are optional, and are not required
What follows is an example of play taken from the finals of the Boardgame Players' Association online tournament. This final features two of the finest Twilight Struggle players in the country- Chris Withers and Stefan Mecay. Until 2009, Stefan had won every Twilight Struggle tournament held at the
🔧 debug — where this ruling came from
- outcome
- ABSTAINED — Abstained — no grounded answer; closest passages below
- warm abstain
-
- this ruling — W1 — generic warm abstain · receipt: none (generic)
- corpus profile
- live,vps
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 86 ms · ask 4602 ms · total 38602 ms
- single-flight (PR-5)
- queued 33913 ms · generation 4689 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 5, "score": 0.04918, "snippet": "5.1 Cards may be played in one of two ways: as Events or Operations. Ordinarily, players will hold one card in their hand at the end of the turn. All other cards will be used for events or operations. Players may not forgo their turn by declining to play a card, or by discarding a card from their ha", "headingPath": "5.0 CARD PLAY", "sharpsignalDocId": 245}, {"page": 4, "score": 0.04741, "snippet": "Headline Phase: Each player secretly selects a card from their hand. Once both players have made their choice, they reveal their cards to each other simultaneously. These cards are called 'Headline cards' and their Events take place in this phase (and if the event title has an asterisk, are removed ", "headingPath": "4.0 GAME SEQUENCE", "sharpsignalDocId": 245}, {"page": 10, "score": 0.045335, "snippet": "The object of the game is to score Victory Points (VPs). Regional Victory Points are scored through geographic Influence over the six Regions. VPs can also be received through the play of certain Events. Each region has its own 'scoring card'. Playing a scoring card causes Victory Points to be score", "headingPath": "10.0 SCORING AND VICTORY", "sharpsignalDocId": 245}, {"page": 11, "score": 0.045262, "snippet": "Once all regions have been scored, victory goes to the player who has accrued most VPs. If the VP marker is on a positive number, the US wins; if the VP marker is on a negative number, the USSR wins. If the VP marker is on zero, the game ends in a draw. These rules are optional, and are not required", "headingPath": "10.3 VICTORY · 11.0 TOURNAMENT PLAY", "sharpsignalDocId": 245}, {"page": 13, "score": 0.043697, "snippet": "What follows is an example of play taken from the finals of the Boardgame Players' Association online tournament. This final features two of the finest Twilight Struggle players in the country- Chris Withers and Stefan Mecay. Until 2009, Stefan had won every Twilight Struggle tournament held at the ", "headingPath": "Extended Example of Play Extended Example of Play", "sharpsignalDocId": 245}, {"page": 5, "score": 0.043374, "snippet": "If a player has insufficient cards to take the requisite number of actions for the turn, that player must sit out of the remaining Action Rounds while the opposing player completes the turn. E. Check Military Operations Phase: Each player determines if they are penalized Victory Points for failing t", "headingPath": "4.0 GAME SEQUENCE", "sharpsignalDocId": 245}, {"page": 10, "score": 0.042208, "snippet": "10.2.1 The Victory Point Track shows a range of scoring possibilities from US-20 (US automatic victory) to USSR-20 (USSR automatic victory). At the start of the game, place the VP marker in the center of the chart, on the box marked At Start. This box represents zero points, or total equilibrium of ", "headingPath": "10.2 The Victory Point Track · 10.3 VICTORY", "sharpsignalDocId": 245}, {"page": 4, "score": 0.029851, "snippet": "3.1 Shuffle the Early War cards and deal each player 8 cards. In addition, place 'The China Card' face up in front of the USSR player. The players are allowed to examine their cards prior to deploying their initial Influence markers. 3.2 The USSR player sets up first. The USSR places a total of 15 I", "headingPath": "3.0 GAME SETUP", "sharpsignalDocId": 245}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- []
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 245 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 245 boosted
- answered-before recall
-
no past answered ruling for this game matched closely enough
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- debug row retained until
- Nov 13, 2026 13:19
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 Twilight Struggle — Rulebook (corpus doc 245) | 5.0 CARD PLAY | p.5 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | 300 |
| #2 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 4.0 GAME SEQUENCE | p.4 | 0.04741 (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 Twilight Struggle — Rulebook (corpus doc 245) | 10.0 SCORING AND VICTORY | p.10 | 0.045335 (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 Twilight Struggle — Rulebook (corpus doc 245) | 10.3 VICTORY · 11.0 TOURNAMENT PLAY | p.11 | 0.045262 (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 Twilight Struggle — Rulebook (corpus doc 245) | Extended Example of Play Extended Example of Play | p.13 | 0.043697 (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 Twilight Struggle — Rulebook (corpus doc 245) | 4.0 GAME SEQUENCE | p.5 | 0.043374 (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 Twilight Struggle — Rulebook (corpus doc 245) | 10.2 The Victory Point Track · 10.3 VICTORY | p.10 | 0.042208 (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 Twilight Struggle — Rulebook (corpus doc 245) | 3.0 GAME SETUP | p.4 | 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 |
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 Twilight Struggle — Rulebook (corpus doc 245) | 5.0 CARD PLAY | p.5 | #1 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | vector + full-text + the doc-priority boost arm | the re-ranker chose it |
| #2 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 6.4 THE SPACE RACE | p.7 | #15 | 0.026686 (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 |
| #3 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 2.2 CARDS · 2.3 MARKERS | p.3 | #10 | 0.028439 (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 Twilight Struggle — Rulebook (corpus doc 245) | 7.0 EVENTS | p.8 | #12 | 0.027778 (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 |
| #5 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 9.0 CHINA | p.9 | #13 | 0.027013 (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 |
| #6 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 10.0 SCORING AND VICTORY | p.10 | #3 | 0.045335 (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 |
| #7 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 3.0 GAME SETUP | p.4 | #8 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #8 | RULEBOOK Twilight Struggle — Rulebook (corpus doc 245) | 5.0 CARD PLAY | p.5 | #9 | 0.028958 (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 |
chosen chunks — what the answer actually cited
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.
| # | document | heading | page | quote chars |
|---|
generation — timing and the path taken
- timing split
- retrieval 86 ms · first delta 4581 ms · total 38602 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 33913 ms · retrieval 86 ms · ask 4602 ms · gateway work 4689 ms · total 38602 ms
- tokens in (the prompt the answerer read)
- 2951
- tokens out (what the answerer generated)
- 9
- tok/sec
- 145.2 tok/sec — 9 output tokens in 0.062 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 18s ago)
- 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
- ABSTAINED — Abstained — no grounded answer; closest passages below
- abstain rationale
-
I don't have enough information.
the answerer's own words, verbatim — hostile corpus/LLM text, rendered escaped
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 171), 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.