You asked
What does each player take, and what goes in the middle, before we begin?
Answered counted as answeredAsked with: Ticket to Ride: Nordic Countriesbg-31627-en-1e
1. Place the board map in the center of the table [1]. 2. Place the Globetrotter Bonus card face up next to the board [1]. 3. Each player takes a set of 40 Colored Train Cars along with its matching Scoring Marker [1]. 4. Each player places his Scoring Marker on the starting location next to the 100 number on the Scoring Track running along the map's border [1]. 5. Shuffle the Train Car cards and deal a starting hand of 4 cards to each player [1]. 6. Place the remaining deck of Train Car cards near the board and turn the top five cards from the deck face-up [1]. 7. Shuffle the Destination Ticket cards and deal 5 cards to each player [1]. 8. The Destination Ticket deck is then placed next to the board [1].
🔧 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 328 ms · ask 4065 ms · total 4402 ms
- single-flight (PR-5)
- queued 0 ms · generation 4402 ms
- retrieval refs (raw)
- [{"page": 2, "score": 0.032787, "snippet": "The player who is the most experienced traveler goes first. Play then proceeds clockwise around the table, each player taking one turn at a time until the game ends. On his turn, a player must perform one (and only one) of the following three actions: Draw Train Car cards The player may draw 2 Train", "headingPath": "The Game Turn", "sharpsignalDocId": 344}, {"page": 4, "score": 0.032258, "snippet": "When attempting to claim a Tunnel route, a player first lays down the number of cards required. Then the 3 top cards from the Train Car card draw pile are turned face-up. For each card revealed whose color matches the color used to claim the Tunnel (including locomotives), an additional card of the ", "headingPath": "Tunnels · Route Scoring Table · Drawing Destination Ticket Cards", "sharpsignalDocId": 344}, {"page": 4, "score": 0.031746, "snippet": "When one player's stock of colored trains gets down to only two trains or less at the end of his turn, each player, including that player, gets one final turn. The game then ends and players calculate their final scores. Players should have already accounted for the points earned as they completed d", "headingPath": "Game End · Calculating Scores · Register your boardgame", "sharpsignalDocId": 344}, {"page": 3, "score": 0.03125, "snippet": "To claim a route, a player must play a set of cards equal to the number of spaces in the route. A set of cards must be of the same color. Most routes require a specific type of set. For example a Blue route must be claimed using blue-colored Train Car cards. Some routes - those that are Gray colored", "headingPath": "Claiming Routes · Ferries · Tunnels", "sharpsignalDocId": 344}, {"page": 2, "score": 0.030769, "snippet": "◆ 1 Board map of Scandinavian train routes ◆ 120 Colored Train cars (40 each in 3 different colors, plus a few spare) ◆ 157 Illustrated cards: 1 Globetrotter Bonus card for the most completed tickets ❶ ◆ 3 Wooden Scoring Markers (1 for each player matching the train colors) ◆ 1 Rules booklet Place t", "headingPath": "Components · Setting up the Game · Object of the Game", "sharpsignalDocId": 344}, {"page": 3, "score": 0.030303, "snippet": "Draw Destination Tickets The player may draw 3 Destination Tickets from the top of the deck. He must keep at least one of them, but he may keep two or all three if he chooses. Any returned cards are removed from the game and put back in the box, not to return to the game. There are 8 types of regula", "headingPath": "The Game Turn · Train Car Cards", "sharpsignalDocId": 344}, {"page": 1, "score": 0.029851, "snippet": "T icket to Ride Nordic Countries takes you on a Nordic adventure through Denmark, Finland, Norway and Sweden as you travel to the great northern cities of Copenhagen, Oslo, Helsinki and Stockholm. Visit Norway's beautiful fjords and the magnificent mountain scenery on the Rauma Railway. Breathe in t", "headingPath": "", "sharpsignalDocId": 344}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "Components · Setting up the Game · Object of the Game", "sharpsignalDocId": 344}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 344 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 344 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 6, 2026 18:18
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 Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | The Game Turn | p.2 | 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 |
| #2 | RULEBOOK Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | Tunnels · Route Scoring Table · Drawing Destination Ticket Cards | p.4 | 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)) | 300 |
| #3 | RULEBOOK Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | Game End · Calculating Scores · Register your boardgame | p.4 | 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 |
| #4 | RULEBOOK Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | Claiming Routes · Ferries · Tunnels | p.3 | 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 |
| #5 | RULEBOOK Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | Components · Setting up the Game · Object of the Game | p.2 | 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 Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | The Game Turn · Train Car Cards | p.3 | 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)) | 300 |
| #7 | RULEBOOK Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | p.1 | 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 |
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 Ticket to Ride: Nordic Countries — Rulebook (corpus doc 344) | Components · Setting up the Game · Object of the Game | p.2 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 328 ms · first delta 3024 ms · total 4402 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 328 ms · ask 4065 ms · gateway work 4402 ms · total 4402 ms
- tokens in (the prompt the answerer read)
- 2793
- tokens out (what the answerer generated)
- 182
- tok/sec
- 138.2 tok/sec — 182 output tokens in 1.317 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 29s 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
- BEGIN — "begin" / "beginning"
- matched words (in the normalized question)
-
begin
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 272), 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.