You asked
How do I take my turn?
Answered counted as answeredAsked with: Power Gridbg-2651-en-1e
Depending on the phase of the game, taking a turn involves different actions: **During the Auction Power Plants phase:** 1. If a player wants to offer a power plant for auction, they do so [1]. 2. If a player wins an auction and buys a power plant, the next player in turn order takes their turn if they have not already purchased a power plant this round [1]. 3. If a player does not want to offer a power plant for auction, they must opt out of this phase; doing so means they cannot bid in later auctions during this phase and will not get a new power plant this round [2]. 4. To show they have opted out, the player moves their house on the player order track to the same numbered space on the bottom row [2]. **During the Buy Resources phase:** 1. Players may buy matching resources for their power plants from the resource market as long as there is still storage space [2]. 2. Players may not buy resources that their current power plants cannot use [2]. 3. The player purchases resource tokens from the spaces of the resource market, paying the price shown on the upper right of each resource space to the bank for each token [2][3]. 4. After purchasing, the player moves their house on the player order track to the same numbered space on the bottom row and the next player takes their turn [2][3]. **During the phase involving connecting cities:** 1. A player may connect any number of new cities during their turn in this phase, provided they pay all building and connecting costs [4]. 2. All subsequent cities added to a network must connect to at least one city already in that player's network (with one of their houses) [4][3]. 3. When connecting to a new city, the player chooses the cheapest connection(s) between a city in their network and the new city and pays the total of connecting costs and the cheapest available building cost to the bank [4]. 4. After connecting all desired cities, the player moves their house on the player and order track to the same numbered space on the bottom row and the next player follows with their turn [4].
🔧 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 212 ms · ask 9323 ms · total 9543 ms
- single-flight (PR-5)
- queued 0 ms · generation 9543 ms
- retrieval refs (raw)
- [{"page": 5, "score": 0.047643, "snippet": "If the player does not want to offer a power plant for auction, they must opt out of this phase. When they do so, they cannot bid in later auctions during this phase and, thus, will not get a new power plant this round. To show this, they move their house on the player order track to the same number", "headingPath": "b. Pass the auction", "sharpsignalDocId": 94}, {"page": 4, "score": 0.032787, "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": 8, "score": 0.032258, "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": 7, "score": 0.031746, "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": 12, "score": 0.030769, "snippet": "This phase is played in reverse player order beginning with the last player. > Each player may choose their starting city anywhere in the contiguous playing zone! > The player connects to any desired number of new cities during their turn, as long as they can pay for them. > Costs: building costs in", "headingPath": "Phase 4: Building Houses", "sharpsignalDocId": 94}, {"page": 12, "score": 0.030303, "snippet": "Rearrange the order of the houses in the top row of the player order. > First player: the player with the most cities in their network. > In case of a tie: the player with the bigger power plant.", "headingPath": "Phase 1: Determine Player Order", "sharpsignalDocId": 94}, {"page": 12, "score": 0.029851, "snippet": "> If a player opts out of this phase, they cannot bid on any auction and do not get any power plant in this round. > During the first round each player must buy a power plant and may not opt out of this phase! After the first round auction as a once off determine player order again. This phase is pl", "headingPath": "b) Pass the auction", "sharpsignalDocId": 94}, {"page": 5, "score": 0.029762, "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": 4, "quote": null, "headingPath": "Important rules to follow:", "sharpsignalDocId": 94}, {"page": 5, "quote": null, "headingPath": "b. Pass the auction", "sharpsignalDocId": 94}, {"page": 5, "quote": null, "headingPath": "b. Pass the auction", "sharpsignalDocId": 94}, {"page": 5, "quote": null, "headingPath": "b. Pass the auction", "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 3, 2026 05:50
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) | b. Pass the auction | p.5 | 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 |
| #2 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | Playing the game | p.4 | 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) | The 3 Steps of the Game | p.8 | 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)) | 119 |
| #4 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | The 3 Steps of the Game | p.7 | 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) | Phase 4: Building Houses | p.12 | 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 Power Grid — Rulebook (corpus doc 94) | Phase 1: Determine Player Order | p.12 | 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)) | 195 |
| #7 | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b) Pass the auction | p.12 | 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 Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | 0.029762 (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) | Important rules to follow: | p.4 | no quote on the wire |
| [2] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | no quote on the wire |
| [3] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | no quote on the wire |
| [4] | RULEBOOK Power Grid — Rulebook (corpus doc 94) | b. Pass the auction | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 212 ms · first delta 6074 ms · total 9543 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 212 ms · ask 9323 ms · gateway work 9543 ms · total 9543 ms
- tokens in (the prompt the answerer read)
- 3988
- tokens out (what the answerer generated)
- 464
- tok/sec
- 136.0 tok/sec — 464 output tokens in 3.411 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 30s 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
- 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.