You asked
How do I setup the game?
Answered counted as answeredTo set up the game, follow these steps: 1. Place the remaining resource tokens as a supply near the resource market [1]. 2. Place the money separated by value next to the game board [1]. 3. If using the USA map, leave the coal storage space next to the resource market empty; all coal tokens must be placed on the resource market spaces [1]. 4. Place the appropriate resource refill summary card next to the resource market [1]. 5. Take power plant cards with a plug on the back (numbered '03' to '15') and shuffle them [1]. 6. Draw the top 8 cards from this shuffled pile and place them face up on the power plant market, sorted in ascending order by number: the four smallest go in the top row (current market) and the remaining four go in the bottom row (future market) [1]. 7. Take one more power plant card with a plug on the back from the shuffled pile and set it aside face down [1]. 8. Set the 'Step 3' card face down under the supply stack [1]. 9. Take the power plant that was set aside in step 7 and place it face-down on top of the supply stack [1]. 10. Remove a specific number of power plant cards with plugs and sockets from the shuffled pile based on the number of players (as shown in the table in source [1]) and place them face down in a box without looking at them [1]. 11. Shuffle all remaining power plant cards together and place them as a stack face down next to the power plant market [1]. 12. Place the auction hammer and discount token next to the power plant market [1]. 13. Determine the player order randomly at the beginning of the game [2].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:12b think:false 4eb23ef187e2
- timings
- search 220 ms · ask 10858 ms · total 11088 ms
- single-flight (PR-5)
- queued 0 ms · generation 11088 ms
- retrieval refs (raw)
- [{"page": 7, "score": 0.016393, "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.016129, "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.015873, "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": 5, "score": 0.015625, "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": 12, "score": 0.015385, "snippet": "Earning cash Each player earns cash from the bank based on the number of cities they power as shown on the payment summary card. Resupply the resource market Based on the number of players and the current Step of the game, resupply the resource market with resource tokens from the supply, using the ", "headingPath": "Phase 5: Bureaucracy", "sharpsignalDocId": 94}, {"page": 4, "score": 0.015152, "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": 3, "score": 0.014925, "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": 10, "score": 0.014706, "snippet": "During Step 1 of the game, players cannot connect to the six cities, where the players placed the Trust's houses on the spaces numbered 10 during the preparation. These cities are only available when Step 2 of the game starts. As long as the Trust has houses in its supply, each time a player connect", "headingPath": "Phase 4: Building Houses", "sharpsignalDocId": 94}]
- citations (raw)
- [{"page": 3, "quote": null, "headingPath": "Preparation", "sharpsignalDocId": 94}, {"page": 4, "quote": null, "headingPath": "Phase 1: Determine Player Order", "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 22, 2026 01:11
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) | The 3 Steps of the Game | p.7 | 0.016393 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #2 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Preparation | p.9 | 0.016129 (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) | Preparation | p.2 | 0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #4 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | 0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #5 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Phase 5: Bureaucracy | p.12 | 0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #6 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Phase 1: Determine Player Order | p.4 | 0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #7 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Preparation | p.3 | 0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #8 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Phase 4: Building Houses | p.10 | 0.014706 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and 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) | Preparation | p.3 | no quote on the wire |
| [2] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Phase 1: Determine Player Order | p.4 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 220 ms · first delta n/a · total 11088 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 220 ms · ask 10858 ms · gateway work 11088 ms · total 11088 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 40s 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
- 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)
-
setup
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.