You asked
How do I setup the game?
Answered counted as answeredFor a standard multi-player game, the setup is as follows: 1. Place Wildlife Tokens in the Cloth Bag and shuffle/shake them well [1]. 2. Determine how many Habitat Tiles are needed based on the number of players using the provided chart [1]. 3. Randomly select the required Habitat Tiles without looking at them [1]. 4. Shuffle these tiles and stack them face down (any number of stacks) within easy reach of all players [1]. 5. Place any excluded Habitat Tiles back into the box [1]. 6. Randomly select one Wildlife Scoring Card for each of the five wildlife, then place those five cards in the center of the play area within easy view of all players [1]. 7. Put the other Wildlife Scoring Cards back in the box [1]. 8. Randomly distribute one Starter Habitat Tile to each player, placing it face-up in front of them [1]. 9. Place any remaining Starter Habitat Tiles back into the box [1]. 10. Reveal 4 Habitat Tiles from the face-down stacks and place them face-up in the center of the play area within easy reach of all players [1]. 11. Draw 22 Wildlife Tokens from the Cloth Bag and pair them, in order, with each of the 4 Habitat Tiles to form 4 combinations of 1 tile and token [1]. 12. Place the Nature Tokens within easy reach of all players [1]. 13. The first player is the person who most recently saw one of the wildlife in the game, or you may select the first player randomly [1]. For a 2-player game, follow the setup for a 2-player game with these exceptions: only give yourself a Starter Habitat Tile and place the stacks of Habitat Tiles to the left side of the play area [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 282 ms · ask 9553 ms · total 9845 ms
- single-flight (PR-5)
- queued 0 ms · generation 9845 ms
- retrieval refs (raw)
- [{"page": 10, "score": 0.032522, "snippet": "Setup: Follow the setup for a 2-player game with the following exceptions: only give yourself a Starter Habitat Tile and place the stacks of Habitat Tiles to the left side of the play area. Turn Summary: Follow a turn as usual, but before you replace the Habitat Tile and Wildlife Token in the displa", "headingPath": "SOLO MODE", "sharpsignalDocId": 109}, {"page": 4, "score": 0.031754, "snippet": "By Pace ait witatife Tokens in the Cloth Bag and shuffie/shake them well. By Using the chart below, determine how many Habitat Tiles you need, based on the number of players. Randomly select these tiles. Do not look at the tiles you include or exclude. For solo mode setup, please see page 10. BR: 43", "headingPath": "About the Team", "sharpsignalDocId": 109}, {"page": 14, "score": 0.031099, "snippet": "Set up and play a multi-player game of Cascadia using the normal rules, The winner of the game will fill in a maximum. of one Achievement shape in their column if an Achievement was earned. Whenever you fill ina shape, fill in the next shape on your trail on the Achievement hiking map (page 12). Set", "headingPath": "INTERMEDIATE VARIANT", "sharpsignalDocId": 109}, {"page": 10, "score": 0.031025, "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": 5, "score": 0.015873, "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": 7, "score": 0.015625, "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": 6, "score": 0.015385, "snippet": "At the beginning of each turn there will be four Habitat Tiles and four Wildlife Tokens in the center of the play area. The Habitat Tiles and Wildlife Tokens will be arranged in four distinct combinations, each with one Habitat Tile and one Wildlife Token-providing four choices. Before you make a se", "headingPath": "GAMEPLAY OVERVIEW", "sharpsignalDocId": 109}, {"page": 10, "score": 0.014925, "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}]
- citations (raw)
- [{"page": 4, "quote": null, "headingPath": "About the Team", "sharpsignalDocId": 109}, {"page": 10, "quote": null, "headingPath": "SOLO MODE", "sharpsignalDocId": 109}]
- 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 31, 2026 20:47
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 109) | SOLO MODE | p.10 | 0.032522 (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) | About the Team | p.4 | 0.031754 (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) | INTERMEDIATE VARIANT | p.14 | 0.031099 (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.031025 (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) | GAMEPLAY OVERVIEW | p.5 | 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 |
| #6 | RULEBOOK Cascadia — Rulebook (corpus doc 109) | Place the Tile and Token into Your Environment | p.7 | 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 |
| #7 | RULEBOOK Cascadia — Rulebook (corpus doc 109) | GAMEPLAY OVERVIEW | p.6 | 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 |
| #8 | RULEBOOK Cascadia — Rulebook (corpus doc 109) | Turn Example: | p.10 | 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 |
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) | About the Team | p.4 | no quote on the wire |
| [2] | RULEBOOK Cascadia — Rulebook (corpus doc 109) | SOLO MODE | p.10 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 282 ms · first delta 6970 ms · total 9845 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 282 ms · ask 9553 ms · gateway work 9845 ms · total 9845 ms
- tokens in (the prompt the answerer read)
- 2483
- tokens out (what the answerer generated)
- 389
- tok/sec
- 137.0 tok/sec — 389 output tokens in 2.839 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 44s 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)
-
setup
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.