You asked
How do I set up the game?
Answered counted as answeredAsked with: Power Gridbg-2651-en-1e
To set up the game, follow these steps: 1. Place the remaining resource tokens as a supply near the resource market [1]. 2. Place money separated by value next to the game board [1]. 3. For the USA map, ensure the coal storage space next to the resource market is empty, as all coal tokens are placed on the spaces of the resource market [1]. 4. Place the appropriate resource refill summary card next to the resource market based on the number of players [1]. 5. Shuffle the pile of power plant cards with a plug on the back (numbered '03' to '15') [1]. 6. Draw the top 8 cards from the plugged power plant pile and place them face up, sorting them in ascending order by their numbers [1]. 7. Place the four smallest cards in the top row of the market (the current market) in ascending order, left to right, and place the remaining four in the bottom row (the future market) in ascending order, left to right [1]. 8. Take one more power plant card with a plug on the back face down and set it aside [1]. 9. Set aside the 'Step 3' card, then shuffle the power plant cards with a socket on the back [1]. 10. Randomly remove some power plant cards with plugs and sockets on the back from the supply based on the number of players (2 players: 1 plug, 5 sockets; 3 players: 2 plugs, 6 sockets; 4 players: 1 plug, 3 sockets; 5-6 players: none) [1]. 11. Shuffle all remaining power plant cards together and place them as a face-down stack next to the power plant market [1]. 12. Place the 'Step 3' card face down under the supply stack [1]. 13. Take the previously set-aside plugged power plant card and place it face-down on top of the supply stack [1]. 14. Place the auction hammer and discount token next to the power plant market [1]. 15. The Trust needs its own space next to the game board for its 16 houses (plus one for player order) [2]. 16. Randomly determine the first player (between the two players) and place their house on space 1 of the player order track [2]. 17. Place the Trust's second player house on space 3 of the player order track, as the Trust is always second in player order [2]. 18. After choosing a contiguous playing zone of 3 adjacent areas, place 6 houses of the Trust on the number 10 spaces of 6 adjacent cities by following this sequence: the starting player places one Trust house on any city of their choice, then the other player places 2 houses (one at a time) adjacent to an already placed Trust house, then the starting player places the next 2, and finally the other player places the last house [2]. 19. Place the remaining 10 houses of the Trust as a supply next to the game board [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 229 ms · ask 11459 ms · total 1049685 ms
- single-flight (PR-5)
- queued 1037988 ms · generation 11697 ms
- retrieval refs (raw)
- [{"page": 3, "score": 0.045805, "snippet": "Place the remaining resource tokens as a supply near the resource market. Place the money separated by value next to the game board. USA map: There is a storage space for coal next to the resource market. At the beginning of the game, this storage space is empty, as all coal tokens are placed on the", "headingPath": "Preparation", "sharpsignalDocId": 94}, {"page": 7, "score": 0.032787, "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": 9, "score": 0.032258, "snippet": "The Trust needs its own space next to the game board, where it places its own power plants. The Trust gets 16 houses of its own color, plus one additional house for player order (The trust does not place a house on the scoring track for connected cities). The Trust does not get any money. Randomly d", "headingPath": "Preparation", "sharpsignalDocId": 94}, {"page": 2, "score": 0.031746, "snippet": "Place the board in the middle of the table. For the first game we suggest choosing Germany. The map is separated into 6 areas, each with 7 cities. In each game, players choose a contiguous playing zone of connected areas depending on the number of players. This is the whole playing zone for ALL play", "headingPath": "Preparation", "sharpsignalDocId": 94}, {"page": 4, "score": 0.03125, "snippet": "The game is played over several rounds. Each round of the game has five phases. In each phase, all players take their actions in the order specified for the phase before the game continues to the next phase. The five phases are: Determine Player Order Auction Power Plants Buy Resources Build Houses ", "headingPath": "Playing the game", "sharpsignalDocId": 94}, {"page": 4, "score": 0.030769, "snippet": "Players determine the player order for the round. The first player is the player with the most cities in their network (the house on the highest numbered space of the scoring track for connected cities). If two or more players are tied for the most cities, the first player is the player among them w", "headingPath": "Phase 1: Determine Player Order", "sharpsignalDocId": 94}, {"page": 8, "score": 0.030303, "snippet": "When you draw the Step 3 card from the power plant stack, Step 3 begins at the beginning of the next phase of the game!", "headingPath": "The 3 Steps of the Game", "sharpsignalDocId": 94}, {"page": 5, "score": 0.029851, "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}]
- citations (raw)
- [{"page": 3, "quote": null, "headingPath": "Preparation", "sharpsignalDocId": 94}, {"page": 9, "quote": null, "headingPath": "Preparation", "sharpsignalDocId": 94}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 94 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 94 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)
- debug row retained until
- Nov 6, 2026 14:26
retrieval — what the search arm returned
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 Power Grid — Rulebook (corpus doc 94) | Preparation | p.3 | 0.045805 (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 Power Grid — Rulebook (corpus doc 94) | The 3 Steps of the Game | p.7 | 0.032787 (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 Power Grid — Rulebook (corpus doc 94) | Preparation | p.9 | 0.032258 (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 Power Grid — Rulebook (corpus doc 94) | Preparation | p.2 | 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 |
| #5 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Playing the game | 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 |
| #6 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Phase 1: Determine Player Order | p.4 | 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 |
| #7 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | The 3 Steps of the Game | p.8 | 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)) | 119 |
| #8 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | 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 |
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) | Preparation | p.3 | no quote on the wire |
| [2] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Preparation | p.9 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 229 ms · first delta 6798 ms · total 1049685 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 1037988 ms · retrieval 229 ms · ask 11459 ms · gateway work 11697 ms · total 1049685 ms
- tokens in (the prompt the answerer read)
- 2975
- tokens out (what the answerer generated)
- 665
- tok/sec
- 137.8 tok/sec — 665 output tokens in 4.827 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 3s 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
- 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
- NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
- pattern that matched
- SETUP — "setup" / "set up"
- matched words (in the normalized question)
-
set up
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.