Ruling — Expeditions

← Expeditions

You asked

How do I play?

Answered counted as answered

Asked with: Expeditionsbg-379078-en-1e

Expeditions is played in consecutive clockwise turns.[1]

A Turn in Expeditions

1. Begin a turn by shifting your action token at the upper right of your mech mat.[1]

2. Choose to either take actions or Refresh.[1]

3. If taking actions, you must perform all exposed actions that you are able to (up to a maximum of 5), which can be a combination of Move, Play, or Gather.[1]

* Move: Move your mech to another unoccupied location within range of 1-3 locations.[1]

* Play: Play 1 card from your hand to your active row (the right of your mech mat).[2][1] You gain the card's core value (power and/or guile).[2] You may also place a specific worker on the card to activate its ability.[2][1] If you already have active cards, the new card is placed to their right.[2]

* Gather: Gain the exposed benefits at your mech's location.[1]

4. If choosing a Refresh turn, shift your action token from Move, Play, or Gather to cover the Refresh spot.[1][3] This can only be done if your action token was covering Move, Play, or Gather at the beginning of your turn.[1][3]

* During a Refresh turn, return all workers placed on active cards to your mech mat and return all active cards to your hand.[1][3][4]

* If you start a turn with your action token on the Refresh spot (which occurs on your first turn and after Refresh turns), shift your action token to the blank spot and take all three actions—Move, Play, and Gather—in any order.[1][3]

* On the turn following a turn where you took all three actions, you must shift your action token to cover Move, Gather, or Play.[1][3]

End of the Game

1. The end of the game is triggered when a player places their 4th glory token with the Boast ability.[1]

2. After this trigger, all players take one final turn.[4]

[1] RULEBOOK Expeditions — Rulebook · p.4 · SHARED COMPONENTS · GAMEPLAY OVERVIEW

[2] RULEBOOK Expeditions — Rulebook · p.6 · ACTIONS · ACTIONS continued

[3] RULEBOOK Expeditions — Rulebook · p.12 · REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued

[4] RULEBOOK Expeditions — Rulebook · p.1

Now you know — make it count.

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 149 ms · ask 23907 ms · total 64410 ms
single-flight (PR-5): queued 40347 ms · generation 24063 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.048172, "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": 1, "score": 0.046898, "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}, {"page": 1, "score": 0.046875, "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": 4, "score": 0.046244, "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": 6, "score": 0.045009, "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": 6, "score": 0.044916, "snippet": "Cards you control are always face up and may exist in one of two places: in your hand to the left of your mech mat or in your active row to the right of your mat. Whenever a card is placed in the active row (when played, gained, or discarded), it is always placed to the right of any existing active ", "headingPath": "CARDS YOU CONTROL ( )", "sharpsignalDocId": 455}, {"page": 5, "score": 0.031746, "snippet": "When you take a Move action or use a Move ability, move your mech to another unoccupied location (a location without another mech) within range. BASECAMP: Basecamp (where your mech begins the game) is adjacent to 3 locations. After moving off Basecamp, your mech will always be on a location-you may ", "headingPath": "MOVE", "sharpsignalDocId": 455}, {"page": 12, "score": 0.029958, "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}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 4, "quote": null, "headingPath": "SHARED COMPONENTS · GAMEPLAY OVERVIEW", "sharpsignalDocId": 455}, {"page": 6, "quote": null, "headingPath": "ACTIONS · ACTIONS continued", "sharpsignalDocId": 455}, {"page": 12, "quote": null, "headingPath": "REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued", "sharpsignalDocId": 455}, {"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 455}]
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: 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)
answer fence: passed — letter density 0.88058 of 1457 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 28, 2026 09:58 UTC

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

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 Expeditions — Rulebook (corpus doc 455)	SETUP	p.2	0.048172 (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)		p.1	0.046898 (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)		p.1	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 Expeditions — Rulebook (corpus doc 455)	SHARED COMPONENTS · GAMEPLAY OVERVIEW	p.4	0.046244 (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.045009 (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)	CARDS YOU CONTROL ( )	p.6	0.044916 (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)	MOVE	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
#8	RULEBOOK Expeditions — Rulebook (corpus doc 455)	REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued	p.12	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

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

candidate pool: the answering read scored 36 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Expeditions — Rulebook (corpus doc 455)	ACTIONS · ACTIONS continued	p.6	#5	0.045009 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Expeditions — Rulebook (corpus doc 455)	SHARED COMPONENTS · GAMEPLAY OVERVIEW	p.4	#4	0.046244 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Expeditions — Rulebook (corpus doc 455)	SETUP	p.2	#1	0.048172 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Expeditions — Rulebook (corpus doc 455)	SHARED COMPONENTS	p.3	#9	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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Expeditions — Rulebook (corpus doc 455)		p.1	#2	0.046898 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Expeditions — Rulebook (corpus doc 455)	CARDS YOU CONTROL ( )	p.6	#6	0.044916 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Expeditions — Rulebook (corpus doc 455)	REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued	p.12	#8	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))	vector + full-text	the re-ranker chose it
#8	RULEBOOK Expeditions — Rulebook (corpus doc 455)		p.1	#3	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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Expeditions — Rulebook (corpus doc 455)	SHARED COMPONENTS · GAMEPLAY OVERVIEW	p.4	no quote on the wire
[2]	RULEBOOK Expeditions — Rulebook (corpus doc 455)	ACTIONS · ACTIONS continued	p.6	no quote on the wire
[3]	RULEBOOK Expeditions — Rulebook (corpus doc 455)	REFRESH · END OF TURN · MECH ABILITIES · ACTIONS continued	p.12	no quote on the wire
[4]	RULEBOOK Expeditions — Rulebook (corpus doc 455)		p.1	no quote on the wire

generation — timing and the path taken

timing split: retrieval 149 ms · first delta 21604 ms · total 64410 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 40347 ms · retrieval 149 ms · ask 23907 ms · gateway work 24063 ms · total 64410 ms
tokens in (the prompt the answerer read): 3608
tokens out (what the answerer generated): 472
tok/sec: 200.9 tok/sec — 472 output tokens in 2.350 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 49s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 9s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
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 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.