Ruling — Cascadia

You asked

How do I take my turn?

Answered counted as answered

Asked with: Cascadiabg-295947-en-1e

1. Check to see if any wildlife are overpopulated: if all 4 available Wildlife Tokens are the same, wipe them by taking them aside and drawing 4 new tokens from the Cloth Bag to pair with Habitat Tiles;[1] if 3 of the available Wildlife Tokens are the same, you may choose to wipe them and replace them one-at-a-time with 3 new tokens from the Cloth Bag (this can only be done once per turn).[1]

2. After resolving overpopulations, place any wiped tokens back into the Cloth Bag.[1]

3. Optionally, before selecting a combination, you may spend a Nature Token to either take ANY one of the four Habitat Tiles and ANY one of the four Wildlife Tokens, or wipe ANY number of Wildlife Tokens and replace them.[1][2]

4. Select one Habitat Tile + Wildlife Token combination (typically an existing combination).[1]

5. Place the selected Habitat Tile and Wildlife Token into your environment in any order.[3]

6. Place the Habitat Tile adjacent to any Habitat Tile already in your environment, touching at least one side of another previously placed tile or the Starter Habitat Tile; you may not place it on top of another Habitat Tile nor move existing tiles.[3]

7. Place the Wildlife Token onto a single Habitat Tile that does not already have a token and shows the matching wildlife; you may place it on the tile you just selected or any other available Habitat Tile.[3]

8. If you cannot legally place the Wildlife Token or choose not to, return the token to the Cloth Bag.[3]

9. Replace the selected Habitat Tile with one from the top of a face-down stack and replace the selected Wildlife Token with one from the Cloth Bag.[4][3]

10. Your turn is complete, and play passes clockwise to the next player.[4][3]

[1] RULEBOOK Cascadia — Rulebook · p.6 · GAMEPLAY OVERVIEW

[2] RULEBOOK Cascadia — Rulebook · p.8 · 3, Habitat Tile Corridor Majorities.

[3] RULEBOOK Cascadia — Rulebook · p.7 · Place the Tile and Token into Your Environment

[4] RULEBOOK Cascadia — Rulebook · p.5 · GAMEPLAY OVERVIEW

🔧 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 248 ms · ask 9544 ms · total 9801 ms
single-flight (PR-5): queued 0 ms · generation 9801 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 10, "score": 0.04866, "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": 5, "score": 0.048652, "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": 8, "score": 0.045688, "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": 10, "score": 0.031746, "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": 10, "score": 0.03125, "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": 8, "score": 0.030769, "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": 6, "score": 0.030622, "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": 9, "score": 0.029851, "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) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 6, "quote": null, "headingPath": "GAMEPLAY OVERVIEW", "sharpsignalDocId": 109}, {"page": 8, "quote": null, "headingPath": "3, Habitat Tile Corridor Majorities.", "sharpsignalDocId": 109}, {"page": 7, "quote": null, "headingPath": "Place the Tile and Token into Your Environment", "sharpsignalDocId": 109}, {"page": 5, "quote": null, "headingPath": "GAMEPLAY OVERVIEW", "sharpsignalDocId": 109}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 109 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 109 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 9, 2026 09:24

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.

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 Cascadia — Rulebook (corpus doc 109)	Turn Example:	p.10	0.04866 (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 Cascadia — Rulebook (corpus doc 109)	GAMEPLAY OVERVIEW	p.5	0.048652 (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 Cascadia — Rulebook (corpus doc 109)	3, Habitat Tile Corridor Majorities.	p.8	0.045688 (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 Cascadia — Rulebook (corpus doc 109)	SOLO MODE	p.10	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 Cascadia — Rulebook (corpus doc 109)	FAMILY VARIANT.	p.10	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 Cascadia — Rulebook (corpus doc 109)	END GAME & SCORING	p.8	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 Cascadia — Rulebook (corpus doc 109)	GAMEPLAY OVERVIEW	p.6	0.030622 (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 Cascadia — Rulebook (corpus doc 109)	4. Nature Tokens	p.9	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))	232

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Cascadia — Rulebook (corpus doc 109)	GAMEPLAY OVERVIEW	p.6	no quote on the wire
[2]	RULEBOOK Cascadia — Rulebook (corpus doc 109)	3, Habitat Tile Corridor Majorities.	p.8	no quote on the wire
[3]	RULEBOOK Cascadia — Rulebook (corpus doc 109)	Place the Tile and Token into Your Environment	p.7	no quote on the wire
[4]	RULEBOOK Cascadia — Rulebook (corpus doc 109)	GAMEPLAY OVERVIEW	p.5	no quote on the wire

generation — timing and the path taken

timing split: retrieval 248 ms · first delta 6919 ms · total 9801 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 248 ms · ask 9544 ms · gateway work 9801 ms · total 9801 ms
tokens in (the prompt the answerer read): 2069
tokens out (what the answerer generated): 390
tok/sec: 137.3 tok/sec — 390 output tokens in 2.840 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 8s 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 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.