Ruling — Ticket to Ride

You asked

How do I take my turn?

Answered counted as answered

Asked with: Ticket to Ridebg-9209-en-1e

On his turn, a player must perform one (and only one) of the following three actions [1]: 1. Draw Train Car Cards: The player may draw 2 Train Car cards [2]. He may take any one of the face-up cards or he may draw the top card from the deck [2]. If he draws a face up card, he immediately turns a replacement card face-up from the deck [2]. He then draws his second card, either from the face up cards or from the top of the deck [2]. (Note: If a Locomotive card is one of the five face-up cards, the player who draws it may only draw one card, instead of two [3]). 2. Claim a Route: The player may claim a route on the board by playing a set of Train Car cards that match the color and length of the route and then placing one of his colored trains on each space of this route [2]. To claim a route, a player must play a set of cards equal to the number of spaces in the route [4]. The set of cards must be of the same type [4]. When a route is claimed, the player places one of his plastic trains in each of the spaces of the route and all cards in the set used are discarded [4]. The player then records his score by moving his Scoring Marker the appropriate number of spaces along the Scoring Track on the board [2]. A player may only claim a maximum of one route on his turn [4]. 3. Draw Destination Tickets: The player draws 3 Destination Tickets from the top of the deck [2]. He must keep at least one, but may keep two or all three if he chooses [2]. Any returned cards are placed on the bottom of the deck [2].

[1] RULEBOOK Ticket to Ride — Rulebook · p.2 · The Game Turn

[2] RULEBOOK Ticket to Ride — Rulebook · p.3 · The Game Turn

[3] RULEBOOK Ticket to Ride — Rulebook · p.3 · Train Car Cards

[4] RULEBOOK Ticket to Ride — Rulebook · p.3 · Claiming Routes

🔧 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 218 ms · ask 4585 ms · total 4812 ms
single-flight (PR-5): queued 0 ms · generation 4812 ms
retrieval refs (raw): [{"page": 2, "score": 0.04918, "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: 30 Destination Ticket cards 1 Longest Continuous", "headingPath": "The Game Turn", "sharpsignalDocId": 85}, {"page": 3, "score": 0.048387, "snippet": "Draw Train Car Cards The player may draw 2 Train Car cards. He may take any one of the face-up cards or he may draw the top card from the deck (this is a blind draw). If he draws a face up card, he immediately turns a replacement card face-up from the deck. He then draws his second card, either from", "headingPath": "The Game Turn", "sharpsignalDocId": 85}, {"page": 2, "score": 0.046875, "snippet": "Place the board map in the center of the table. Each player takes a set of 45 Colored Train Cars along with its matching Scoring Marker. Each player places his Scoring Marker on Start ❶ on the Scoring Track running along the map's border. Throughout the game, each time a player scores points, he wil", "headingPath": "Setting up the Game", "sharpsignalDocId": 85}, {"page": 3, "score": 0.031746, "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 type. Most routes require a specific type of set. For example a Blue route must be claimed using blue-colored Passenger Car cards. Some routes - those that are Gray colo", "headingPath": "Claiming Routes", "sharpsignalDocId": 85}, {"page": 4, "score": 0.030769, "snippet": "A player can use his turn to draw more Destination Ticket cards. To do so, he draws 3 new cards from the top of the Destination Ticket Deck. He must keep at least one of the cards, but may also keep two or all three if he chooses. If there are less than 3 Destination Tickets left in the deck, the pl", "headingPath": "Drawing Destination Ticket Cards", "sharpsignalDocId": 85}, {"page": 4, "score": 0.030303, "snippet": "When a player claims a route, he records the points he receives by moving his Scoring Marker on the Scoring Track:", "headingPath": "Route Scoring Table", "sharpsignalDocId": 85}, {"page": 3, "score": 0.029958, "snippet": "There are 8 types of regular Train Car cards, plus Locomotive cars. The colors of each type of Train Car card match various routes between cities on the board - Purple, Blue, Orange, White, Green, Yellow, Black, and Red. Locomotives are Multi-colored and act as a wild card that can be part of any se", "headingPath": "Train Car Cards", "sharpsignalDocId": 85}, {"page": 4, "score": 0.029851, "snippet": "Players should have already accounted for the points earned as they completed different routes. To make sure no mistakes were made, you may want to re-count the points for each player's routes. Players should then reveal all their Destination Tickets and add (or subtract) the value of their Destinat", "headingPath": "Calculating Scores", "sharpsignalDocId": 85}]
citations (raw): [{"page": 2, "quote": null, "headingPath": "The Game Turn", "sharpsignalDocId": 85}, {"page": 3, "quote": null, "headingPath": "The Game Turn", "sharpsignalDocId": 85}, {"page": 3, "quote": null, "headingPath": "Train Car Cards", "sharpsignalDocId": 85}, {"page": 3, "quote": null, "headingPath": "Claiming Routes", "sharpsignalDocId": 85}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 85 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 85 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:35

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 — Rulebook (corpus doc 85)	The Game Turn	p.2	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	The Game Turn	p.3	0.048387 (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 — Rulebook (corpus doc 85)	Setting up the Game	p.2	0.046875 (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 — Rulebook (corpus doc 85)	Claiming Routes	p.3	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 Ticket to Ride — Rulebook (corpus doc 85)	Drawing Destination Ticket Cards	p.4	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 — Rulebook (corpus doc 85)	Route Scoring Table	p.4	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))	114
#7	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	Train Car Cards	p.3	0.029958 (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 Ticket to Ride — Rulebook (corpus doc 85)	Calculating Scores	p.4	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

#	document	heading	page	quote chars
[1]	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	The Game Turn	p.2	no quote on the wire
[2]	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	The Game Turn	p.3	no quote on the wire
[3]	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	Train Car Cards	p.3	no quote on the wire
[4]	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	Claiming Routes	p.3	no quote on the wire

generation — timing and the path taken

timing split: retrieval 218 ms · first delta 2301 ms · total 4812 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 218 ms · ask 4585 ms · gateway work 4812 ms · total 4812 ms
tokens in (the prompt the answerer read): 1922
tokens out (what the answerer generated): 368
tok/sec: 150.0 tok/sec — 368 output tokens in 2.453 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 27s 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 16), 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.