You asked
When does the game end?
Answered counted as answered1. The game ends immediately at the end of any player's turn if there are no face-down Habitat Tiles left in the stacks to replace the one taken [1]. 2. Alternatively, the game ends when there are no more Habitat Tiles available to replace one selected by a player [2][3].
🔧 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 190 ms · ask 6858 ms · total 24569 ms
- single-flight (PR-5)
- queued 17505 ms · generation 7064 ms
- retrieval refs (raw)
- [{"page": 5, "score": 0.032266, "snippet": "Beginning with the starting player and proceeding clockwise around the table, players will take turns drafting Habitat Tiles and Wildlife Tokens and adding them into their expanding environment, until the end of the game. On each turn, a player will select a Habitat Tile and Wildlife Token combinati", "headingPath": "GAMEPLAYOVERVIEW", "sharpsignalDocId": 108}, {"page": 8, "score": 0.032266, "snippet": "If, at the end of any player's turn, there are no face-down Habitat Tiles left in the stacks to replace the one taken, the game ends immediately and scores are tallied, (Note: each player will play exactly 20 turns) Record scores on the Scorepad for the following: Wildlife Scoring Cards Habitat Tile", "headingPath": "END GAME & SCORING", "sharpsignalDocId": 109}, {"page": 5, "score": 0.032258, "snippet": "Beginning with the starting player and proceeding clockwise around the table, players will take turns drafting Habitat Tiles and Wildlife Tokens and adding them into their expanding environment, until the end of the game. On each turn, a player will select a Habitat Tile and Wildlife Token combinati", "headingPath": "GAMEPLAY OVERVIEW", "sharpsignalDocId": 109}, {"page": 10, "score": 0.030331, "snippet": "Setup: The Family Variant setup is the same as the standard game except, for step 3, use ONLY the Family Variant Wildlife Scoring Card. Turn Summary: No changes (see Turn Summary on pages 6-7) End Game & Scoring: Follow scoring on pages 8-9 but you may choose to skip step 3 depending on if you want ", "headingPath": "FAMILY VARIANT.", "sharpsignalDocId": 109}, {"page": 10, "score": 0.030303, "snippet": "On your tun you spend a Nature Token so you can take the Keystone Tile and the matching Elk Wildlife Token. After you have placed the tile and token into your environment, discard the tile and token furthest from the draw stacks (The Mc Slide the remaining two Habitat Tiles and two Wildlife Tokens a", "headingPath": "Turn Example:", "sharpsignalDocId": 109}, {"page": 8, "score": 0.02901, "snippet": "According to player count, score bonus points for having the LARGEST contiguous habitat corridor for each of the 5 habitat types. (Use the numbers recorded on the Scorepad from step 2 to determine who gains bonus points. Record bonus points in the bottom right corner of the corresponding box for the", "headingPath": "3, Habitat Tile Corridor Majorities.", "sharpsignalDocId": 109}, {"page": 7, "score": 0.026137, "snippet": "'Once you have selected your Habitat Tile and Wildlife Token, you will place them into your environment in any order. 'The Habitat Tile must be placed into your environment according to the following placement tules: A. The Habitat Tile must be placed adjacent to any Habitat Tile already in your env", "headingPath": "Place the Tile and Token into Your Environment", "sharpsignalDocId": 109}, {"page": 9, "score": 0.015625, "snippet": "For each player, score 1 point for each unused Nature Token, Finally, tally all points and the player with the most In the case of a tie, the player with the most Nature Tokens wins. If still tied, they share the victory. points win", "headingPath": "4. Nature Tokens", "sharpsignalDocId": 109}]
- citations (raw)
- [{"page": 8, "quote": null, "headingPath": "END GAME & SCORING", "sharpsignalDocId": 109}, {"page": 5, "quote": null, "headingPath": "GAMEPLAY OVERVIEW", "sharpsignalDocId": 109}, {"page": 5, "quote": null, "headingPath": "GAMEPLAYOVERVIEW", "sharpsignalDocId": 108}]
- 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:58
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 Cascadia — Rulebook (corpus doc 108) | GAMEPLAYOVERVIEW | p.5 | 0.032266 (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 Cascadia — Rulebook (corpus doc 109) | END GAME & SCORING | p.8 | 0.032266 (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 Cascadia — Rulebook (corpus doc 109) | GAMEPLAY OVERVIEW | p.5 | 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 |
| #4 | RULEBOOK Cascadia — Rulebook (corpus doc 109) | FAMILY VARIANT. | p.10 | 0.030331 (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 Cascadia — Rulebook (corpus doc 109) | Turn Example: | p.10 | 0.030303 (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 Cascadia — Rulebook (corpus doc 109) | 3, Habitat Tile Corridor Majorities. | p.8 | 0.02901 (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 Cascadia — Rulebook (corpus doc 109) | Place the Tile and Token into Your Environment | p.7 | 0.026137 (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 Cascadia — Rulebook (corpus doc 109) | 4. Nature Tokens | p.9 | 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) | 232 |
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 Cascadia — Rulebook (corpus doc 109) | END GAME & SCORING | p.8 | no quote on the wire |
| [2] | RULEBOOK Cascadia — Rulebook (corpus doc 109) | GAMEPLAY OVERVIEW | p.5 | no quote on the wire |
| [3] | RULEBOOK Cascadia — Rulebook (corpus doc 108) | GAMEPLAYOVERVIEW | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 190 ms · first delta n/a · total 24569 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 17505 ms · retrieval 190 ms · ask 6858 ms · gateway work 7064 ms · total 24569 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 16s 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 23), 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.