Ruling — Let's Go! To Japan

You asked

Before anyone takes a turn, how is everything laid out on the table?

Answered counted as answered

Asked with: Let's Go! To Japanbg-368173-en-1e

1. One player randomly places each of their 6 Favorable Condition tokens in the circular spot corresponding to one of the 6 days (Monday to Saturday) at the bottom of their player board [1]. 2. All other players place their own Favorable Condition tokens on their player boards matching the exact order of that player's tokens [1]. 3. Shuffle the 80 Activity cards marked 'Tokyo' on the back and place them face-down in a Tokyo deck in the central play area, within reach of all players [1]. 4. Shuffle the 80 Activity cards marked 'Kyoto' on the back and place them face-down near the Tokyo deck [1]. 5. Leave space for a face-up discard pile [1]. 6. Place the Round Tracker Board in the central play area [1]. 7. Place the Round Tracker token on the first (leftmost) circular space, so as not to cover the icon [1]. 8. Each player takes a Starting Train token [1]. 9. Place the Train, Wild, Research, Walk, and '+12' tokens in separate piles within reach of all players to form the supply [1].

[1] RULEBOOK Let's Go! To Japan — Rulebook · p.3 · setup

🔧 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 309 ms · ask 7767 ms · total 8088 ms
single-flight (PR-5): queued 0 ms · generation 8088 ms
retrieval refs (raw): [{"page": 6, "score": 0.032787, "snippet": "Throughout the game, players will add Activity cards to their itinerary by placing them in a column below one of the days, Monday to Saturday, on their player board. Each day can have a maximum of 3 cards in its column. (Extra Walk cards, which are explained on page 8, are the exception.) The cards ", "headingPath": "card placement", "sharpsignalDocId": 489}, {"page": 9, "score": 0.032258, "snippet": "At this point, players activate the cards in their itinerary in order from Monday to Saturday, starting with the card at the top of the column for Monday and going downward in that column so that the upper section of each card is activated. This is followed by the activation of the visible 'Highligh", "headingPath": "final round: going on a trip! · example", "sharpsignalDocId": 489}, {"page": 5, "score": 0.031746, "snippet": "Each round, players will play either 1 or 2 Activity cards simultaneously to their itinerary, as indicated by the text on the Round Tracker Board. The upper section of each card shows which of the player's 5 Experience tokens will move forward on the Experience Track on their player board, and/or wh", "headingPath": "2. play cards", "sharpsignalDocId": 489}, {"page": 5, "score": 0.03125, "snippet": "Draw Cards | 2. Play Cards 2a. Day Bonuses | 3. End of Round At the beginning of each round, players will draw Activity cards simultaneously to their hand as indicated by where the Round Tracker token is on the Round Tracker Board. This icon means players should draw 1 card from the Tokyo deck and 1", "headingPath": "round order · 1. draw cards · research tokens", "sharpsignalDocId": 489}, {"page": 7, "score": 0.030769, "snippet": "When playing cards, players should consider maximizing points by: y Placing cards in the day in which the Favorable Condition token on their player board matches the most icons in the upper section of the card, since that will earn them bonuses. (See next column.) y Placing Tokyo cards adjacent to o", "headingPath": "2. play cards (continued) · going for a walk", "sharpsignalDocId": 489}, {"page": 14, "score": 0.030303, "snippet": "At the end of their trip (after they finish scoring Saturday), players earn points for where each of their 5 Experience tokens is on their Experience Track. At the end of her trip, Machiko's Experience Track looks like this. y She scores no points for her Shopping/Goods token as it did not reach at ", "headingPath": "experience track · example: experience track · final score", "sharpsignalDocId": 489}, {"page": 3, "score": 0.029851, "snippet": "One player randomly places each of their 6 Favorable Condition tokens in the circular spot corresponding to one of the 6 days (Monday to Saturday) at the bottom of their player board. All other players place their own Favorable Condition tokens on their player boards matching the exact order of that", "headingPath": "setup", "sharpsignalDocId": 489}, {"page": 8, "score": 0.029412, "snippet": "Kinkakuji Temple Arashiyama Bamboo Grove Ponto-cho Kiyomizudera Temple Higashiyama District Kyoto Tower Fushimi Inari Shrine A player who has matched 2 icons can choose to take the lesser bonus for matching only 1 icon. A player who has matched 3 icons can choose to take any 1 of the lesser bonuses ", "headingPath": "kyoto highlights · 2a. day bonuses (continued) · wild tokens · extra walk · 3. end of round", "sharpsignalDocId": 489}]
citations (raw): [{"page": 3, "quote": null, "headingPath": "setup", "sharpsignalDocId": 489}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 489 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 489 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 7, 2026 05:55

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 Let's Go! To Japan — Rulebook (corpus doc 489)	card placement	p.6	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 Let's Go! To Japan — Rulebook (corpus doc 489)	final round: going on a trip! · example	p.9	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 Let's Go! To Japan — Rulebook (corpus doc 489)	2. play cards	p.5	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 Let's Go! To Japan — Rulebook (corpus doc 489)	round order · 1. draw cards · research tokens	p.5	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 Let's Go! To Japan — Rulebook (corpus doc 489)	2. play cards (continued) · going for a walk	p.7	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 Let's Go! To Japan — Rulebook (corpus doc 489)	experience track · example: experience track · final score	p.14	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 Let's Go! To Japan — Rulebook (corpus doc 489)	setup	p.3	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
#8	RULEBOOK Let's Go! To Japan — Rulebook (corpus doc 489)	kyoto highlights · 2a. day bonuses (continued) · wild tokens · extra walk · 3. end of round	p.8	0.029412 (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 Let's Go! To Japan — Rulebook (corpus doc 489)	setup	p.3	no quote on the wire

generation — timing and the path taken

timing split: retrieval 309 ms · first delta 6207 ms · total 8088 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 309 ms · ask 7767 ms · gateway work 8088 ms · total 8088 ms
tokens in (the prompt the answerer read): 3550
tokens out (what the answerer generated): 251
tok/sec: 136.3 tok/sec — 251 output tokens in 1.841 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 58s 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 420), 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.