Ruling — Ticket to Ride

You asked

Can I get more routes?

Abstained — no grounded answer; closest passages below counted as honest abstain

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

The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.

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

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

RULEBOOK Ticket to Ride — Rulebook · p.4 · Calculating Scores

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

RULEBOOK Ticket to Ride — Rulebook · p.4 · Drawing Destination Ticket Cards

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

RULEBOOK Ticket to Ride — Rulebook · p.2 · Object of the Game

The object of the game is to score the highest number of total points. Points can be scored by: ◆ Claiming a Route between two adjacent cities on the map; ◆ Successfully completing a Continuous Path of routes between two cities listed on your Destination Ticket(s); ◆ Completing the Longest Continuou

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

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

🔧 debug — where this ruling came from

outcome: ABSTAINED — Abstained — no grounded answer; closest passages below
corpus profile: live
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 465 ms · ask 2496 ms · total 2981 ms
single-flight (PR-5): queued 0 ms · generation 2981 ms
retrieval refs (raw): [{"page": 3, "score": 0.032787, "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.032258, "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}, {"page": 4, "score": 0.031746, "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": 2, "score": 0.03125, "snippet": "The object of the game is to score the highest number of total points. Points can be scored by: ◆ Claiming a Route between two adjacent cities on the map; ◆ Successfully completing a Continuous Path of routes between two cities listed on your Destination Ticket(s); ◆ Completing the Longest Continuou", "headingPath": "Object of the Game", "sharpsignalDocId": 85}, {"page": 3, "score": 0.030769, "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": 3, "score": 0.030478, "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": 1, "score": 0.030303, "snippet": "O n a blustery autumn evening five old friends met in the backroom of one of the city's oldest and most private clubs. Each had traveled a long distance - from all corners of the world - to meet on this very specific day… October 2, 1900 - 28 years to the day that the London eccentric, Phileas Fogg ", "headingPath": "", "sharpsignalDocId": 85}, {"page": 2, "score": 0.029851, "snippet": "◆ 1 Board map of North American train routes ◆ 240 Colored Train Cars (45 each in Blue, Red, Green, Yellow and Black, plus some extra replacement cars in each color) ◆ 144 Illustrated cards: 110 Train Car cards (12 each of Box, Passenger, Tanker, Reefer, Freight, Hopper, Coal, and Caboose cars, plus", "headingPath": "Components", "sharpsignalDocId": 85}]
citations (raw): []
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: no past answered ruling for this game matched closely enough
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:01

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)	Claiming Routes	p.3	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 — Rulebook (corpus doc 85)	Calculating Scores	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 — Rulebook (corpus doc 85)	Drawing Destination Ticket Cards	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 — Rulebook (corpus doc 85)	Object of the Game	p.2	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 — Rulebook (corpus doc 85)	The Game Turn	p.3	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)	Train Car Cards	p.3	0.030478 (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 — Rulebook (corpus doc 85)		p.1	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
#8	RULEBOOK Ticket to Ride — Rulebook (corpus doc 85)	Components	p.2	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

generation — timing and the path taken

timing split: retrieval 465 ms · first delta 2895 ms · total 2981 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 465 ms · ask 2496 ms · gateway work 2981 ms · total 2981 ms
tokens in (the prompt the answerer read): 1828
tokens out (what the answerer generated): 9
tok/sec: 147.5 tok/sec — 9 output tokens in 0.061 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 50s 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: ABSTAINED — Abstained — no grounded answer; closest passages below
abstain rationale: I don't have enough information.
the answerer's own words, verbatim — hostile corpus/LLM text, rendered escaped

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.