You asked
When does the game end?
Answered counted as answeredThe game ends in the following ways: 1. The game ends immediately after Phase 4 (Build Houses) when at least one player has connected a specific number of cities (or more) in their network, depending on the number of players [1]. 2. The required number of connected cities to end the game is: * 2 players: 18 cities [1] * 3-4 players: 17 cities [1] * 5 players: 15 cities [1] * 6 players: 14 cities [1] 3. The game usually ends in Step 3, though it may end in Step 2 in some cases [2].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 215 ms · ask 7271 ms · total 7495 ms
- single-flight (PR-5)
- queued 0 ms · generation 7495 ms
- retrieval refs (raw)
- [{"page": 8, "score": 0.032787, "snippet": "The game ends immediately after Phase 4 (Build Houses) when at least one player has connected the indicated number of cities (or more) in their network, depending on the number of players. Players may use the oblong Game End barrier to place on the border in front of the matching space of the scorin", "headingPath": "End of the Game and Winning the Game", "sharpsignalDocId": 94}, {"page": 10, "score": 0.032258, "snippet": "The game ends immediately after phase 4 (Build Houses) when at least one player has connected 18 or more cities in their network. The Trust cannot win - it only offers many possibilities to place obstacles in the way of the players. Rio Grande Games PO Box 1033 Placitas, NM 87043, USA RioGames@aol.c", "headingPath": "End of the Game", "sharpsignalDocId": 94}, {"page": 7, "score": 0.031498, "snippet": "The game runs through three Steps and begins with Step 1. Step 2 begins when the first player has connected a certain number of cities in their network. Step 3 begins after the Step 3 card is drawn from the power plant stack. The game usually ends in Step 3, but in some cases may end in Step 2. This", "headingPath": "The 3 Steps of the Game", "sharpsignalDocId": 94}, {"page": 2, "score": 0.028778, "snippet": "P ower gri D uses new rules for 2 players. While challenging the opponent, you must incorporate the schemes of a competing Trust in your plans and use these schemes against your opponent. Below we describe all rules, including all rules for the two maps. At the end of the rules booklet you will find", "headingPath": "P ower gri D for 2 players: 'Against the Trust'", "sharpsignalDocId": 94}, {"page": 7, "score": 0.028259, "snippet": "Germany map: German Nuclear Power Phase-Out - After a player buys the nuclear power plant '39' in Phase 2 (Auction Power Plants), there is no further resupply of uranium until the end of the game. If the nuclear power plant '39' is not bought by a player or has been removed from the game during prep", "headingPath": "Important rules to follow:", "sharpsignalDocId": 94}, {"page": 7, "score": 0.027885, "snippet": "USA map: If players supply electricity by using coal, they place these coal markers on the storage space next to the resource market. When resupplying the resource market the players take the coal markers from this storage space. Resupply the resource market: Based on the number of players and the c", "headingPath": "Important rules to follow:", "sharpsignalDocId": 94}, {"page": 5, "score": 0.027864, "snippet": "The player purchases the resource tokens from the spaces of the resource market. The printed number on the upper right of each resource space shows the price for one resource token. The player pays this amount to the bank for each token. They move their house on the player order track to the same nu", "headingPath": "b. Pass the auction", "sharpsignalDocId": 94}, {"page": 4, "score": 0.026916, "snippet": "> During the first round of the game each player must buy 1 power plant. > As long as the discount token is on the lowest power plant, the minimum bid for that power plant is 1. If a player buys that power plant, they place the discount token next to the market. > As long as the discount token is on", "headingPath": "Important rules to follow:", "sharpsignalDocId": 94}]
- citations (raw)
- [{"page": 8, "quote": null, "headingPath": "End of the Game and Winning the Game", "sharpsignalDocId": 94}, {"page": 7, "quote": null, "headingPath": "The 3 Steps of the Game", "sharpsignalDocId": 94}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
- 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)
- debug row retained until
- Oct 30, 2026 03:05
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 Power Grid — Rulebook (corpus doc 94) | End of the Game and Winning the Game | p.8 | 0.032787 (at the 2-arm ceiling (0.03279) — the top of a 2-arm fuse; whether more arms ran here was never recorded) | 300 |
| #2 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | End of the Game | p.10 | 0.032258 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #3 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | The 3 Steps of the Game | p.7 | 0.031498 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #4 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | P ower gri D for 2 players: 'Against the Trust' | p.2 | 0.028778 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #5 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Important rules to follow: | p.7 | 0.028259 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #6 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Important rules to follow: | p.7 | 0.027885 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #7 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | 0.027864 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #8 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Important rules to follow: | p.4 | 0.026916 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
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 |
|---|---|---|---|---|
| [1] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | End of the Game and Winning the Game | p.8 | no quote on the wire |
| [2] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | The 3 Steps of the Game | p.7 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 215 ms · first delta n/a · total 7495 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 215 ms · ask 7271 ms · gateway work 7495 ms · total 7495 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 26s ago)
- stream path
- not recorded — this ruling predates the stream-path column (V41)
- 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 25), 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.