RuleSage cited table rulings
← Expeditions

You asked

How should we prepare everything before the first turn?

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

Asked with: Expeditionsbg-379078-en-1e

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

RULEBOOK Expeditions — Rulebook · p.4 · SHARED COMPONENTS · GAMEPLAY OVERVIEW
4 A turn in Expeditions begins with shifting your action token at the upper right of your mech mat. Then you must either (a) take actions or (b) Refresh. If you take actions, you must perform all exposed actions that you are able to (some combination of Move, Play, Gather). (max 5) Most turns in Exp
RULEBOOK Expeditions — Rulebook · p.2 · SETUP
PLAYER COMPONENTS: Each player gains the following. Return any unused components from each step to the box. MECH MAT & MINIATURE: At random, gain a mech mat and the corresponding mech miniature. Choose a base snap to select your player color and attach the base snap to your mech. STARTING CARDS (CHA
RULEBOOK Expeditions — Rulebook · p.12 · REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued
When you take a Refresh turn or gain a Refresh benefit, return all workers placed on active cards to your mech mat, then return all active cards to your hand. (max 5) REFRESH TURN: Shift your action token from Move, Play, or Gather to cover the Refresh spot. You may take a Refresh turn only if your
RULEBOOK Expeditions — Rulebook · p.3 · SHARED COMPONENTS
BASECAMP BOARD: Place the Basecamp board on the table, then place each player's mech next to it. LOCATION TILES: Separate the location tiles into three groups by their region (South, Central, and North). Shuffle the 6 South location tiles. Referring to the layout diagram at the top right of the Base
RULEBOOK Expeditions — Rulebook · p.6 · ACTIONS · ACTIONS continued
6 When you take a Play action, choose 1 card in your hand (the left of your mech mat) and play it to your active row (the right of your mech mat). If you already have active cards, place the new card to their right. In any order, (a) you may gain the card's core value (in the upper left) and (b) you
🔧 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 229 ms · ask 6643 ms · total 29818 ms
single-flight (PR-5)
queued 22938 ms · generation 6880 ms
retrieval refs (raw)
[{"page": 4, "score": 0.032787, "snippet": "4 A turn in Expeditions begins with shifting your action token at the upper right of your mech mat. Then you must either (a) take actions or (b) Refresh. If you take actions, you must perform all exposed actions that you are able to (some combination of Move, Play, Gather). (max 5) Most turns in Exp", "headingPath": "SHARED COMPONENTS · GAMEPLAY OVERVIEW", "sharpsignalDocId": 455}, {"page": 2, "score": 0.032258, "snippet": "PLAYER COMPONENTS: Each player gains the following. Return any unused components from each step to the box. MECH MAT & MINIATURE: At random, gain a mech mat and the corresponding mech miniature. Choose a base snap to select your player color and attach the base snap to your mech. STARTING CARDS (CHA", "headingPath": "SETUP", "sharpsignalDocId": 455}, {"page": 12, "score": 0.031746, "snippet": "When you take a Refresh turn or gain a Refresh benefit, return all workers placed on active cards to your mech mat, then return all active cards to your hand. (max 5) REFRESH TURN: Shift your action token from Move, Play, or Gather to cover the Refresh spot. You may take a Refresh turn only if your ", "headingPath": "REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued", "sharpsignalDocId": 455}, {"page": 3, "score": 0.03125, "snippet": "BASECAMP BOARD: Place the Basecamp board on the table, then place each player's mech next to it. LOCATION TILES: Separate the location tiles into three groups by their region (South, Central, and North). Shuffle the 6 South location tiles. Referring to the layout diagram at the top right of the Base", "headingPath": "SHARED COMPONENTS", "sharpsignalDocId": 455}, {"page": 6, "score": 0.030769, "snippet": "6 When you take a Play action, choose 1 card in your hand (the left of your mech mat) and play it to your active row (the right of your mech mat). If you already have active cards, place the new card to their right. In any order, (a) you may gain the card's core value (in the upper left) and (b) you", "headingPath": "ACTIONS · ACTIONS continued", "sharpsignalDocId": 455}, {"page": 9, "score": 0.030303, "snippet": "When you take a Gather action, gain the exposed benefits at your mech's location. The benefits are shown at the bottom of the location-each icon is a separate benefit. If there is a / symbol ('or'), choose only the benefits on one side of that symbol. GAINING A FACE-UP CARD ( ) : Any benefit or abil", "headingPath": "GATHER", "sharpsignalDocId": 455}, {"page": 1, "score": 0.029851, "snippet": "PLAY: Play 1 card from your hand to your active row, gaining its core value and optionally placing a worker on it to activate its ability. REFRESH: Return all active cards to your hand and return all placed workers to your mech mat. The game ends after a player places their 4th glory token. All play", "headingPath": "", "sharpsignalDocId": 455}, {"page": 1, "score": 0.029412, "snippet": "Play cards to gain power, guile, and unique worker abilities; move your mech to mysterious locations; use workers, items, meteorites, and quests to enhance your mech; and use power and guile to vanquish corruption from the land. Collect glory and riches to complete the most lucrative expedition in t", "headingPath": "", "sharpsignalDocId": 455}]
citations (raw)
[]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 455 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 455 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 7, 2026 05:09

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Expeditions — Rulebook (corpus doc 455) SHARED COMPONENTS · GAMEPLAY OVERVIEW p.4 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 Expeditions — Rulebook (corpus doc 455) SETUP p.2 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 Expeditions — Rulebook (corpus doc 455) REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued p.12 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 Expeditions — Rulebook (corpus doc 455) SHARED COMPONENTS 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 Expeditions — Rulebook (corpus doc 455) ACTIONS · ACTIONS continued p.6 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 Expeditions — Rulebook (corpus doc 455) GATHER p.9 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 Expeditions — Rulebook (corpus doc 455) 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
#8 RULEBOOK Expeditions — Rulebook (corpus doc 455) p.1 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

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.

#documentheadingpagequote chars
timing split
retrieval 229 ms · first delta 6721 ms · total 29818 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 22938 ms · retrieval 229 ms · ask 6643 ms · gateway work 6880 ms · total 29818 ms
tokens in (the prompt the answerer read)
4496
tokens out (what the answerer generated)
9
tok/sec
84.1 tok/sec — 9 output tokens in 0.107 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 10s 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.
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
decision
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

this game registers NO errata cards (edition 385), 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.