Ruling — Scythe

You asked

What happens when I roll a 7?

Refused — the rulebook doesn't cover this counted as refused

The rulebook doesn't appear to cover this cleanly — but here are the closest passages retrieved, in case they help you rule.

RULEBOOK Scythe — Rulebook · p.28 · GAME END AND SCORING

The game immediately ends when a player places their 6th star token, even if they have other things they could do that turn or other things would happen afterwards.

RULEBOOK Scythe — Rulebook · p.28 · EDGE CASES

If the 6th star comes from taking a bottom-row action, gain the primary benefit, the coins, and the Recruit Ongoing Benefit before placing the star. If you have units (character, mechs, or workers) remaining on a territory with an opponent's units (from a Move action), you must undo that portion of

RULEBOOK Scythe — Rulebook · p.14 · BOTTOM-ROW ACTIONS

The bottom-row actions are in the same order on all Player Mats, but the costs and benefits vary. The Player Mat visuals and the default costs and benefits explained in this section are based on the starting position of each Player Mat. OVERLAPPING TURNS: Usually when a player starts to take the bot

RULEBOOK Scythe — Rulebook · p.31 · HIGHLIGHTED RULES

All resources, units, or structures gained from an encounter card go on the territory where the encounter occurred. Benefits gained from encounters do not trigger Recruit Ongoing Bonuses. FACTORY: Only characters may claim Factory cards (1 per player). Actions taken on Factory cards do not trigger R

RULEBOOK Scythe — Rulebook · p.29 · DECLARING THE WINNER

Announce your coin total, and the player with the most coins wins! If multiple players have the same total, use the following as tiebreakers (in order): Number of workers, mechs, and structures Power Popularity Number of resource tokens controlled Number of territories controlled Number of star toke

🔧 debug — where this ruling came from

outcome: REFUSED_NO_RETRIEVAL — Refused — the rulebook doesn't cover this
corpus profile: live
answerer pin (deploy-frozen, attribution only): qwen3:4b-instruct-2507-q4_K_M@0edcdef34593
timings: search 85 ms · ask 2823 ms · total 2908 ms
single-flight (PR-5): queued 0 ms · generation 2908 ms
retrieval refs (raw): [{"page": 28, "score": 0.016393, "snippet": "The game immediately ends when a player places their 6th star token, even if they have other things they could do that turn or other things would happen afterwards.", "headingPath": "GAME END AND SCORING", "sharpsignalDocId": 44}, {"page": 28, "score": 0.016129, "snippet": "If the 6th star comes from taking a bottom-row action, gain the primary benefit, the coins, and the Recruit Ongoing Benefit before placing the star. If you have units (character, mechs, or workers) remaining on a territory with an opponent's units (from a Move action), you must undo that portion of ", "headingPath": "EDGE CASES", "sharpsignalDocId": 44}, {"page": 14, "score": 0.015873, "snippet": "The bottom-row actions are in the same order on all Player Mats, but the costs and benefits vary. The Player Mat visuals and the default costs and benefits explained in this section are based on the starting position of each Player Mat. OVERLAPPING TURNS: Usually when a player starts to take the bot", "headingPath": "BOTTOM-ROW ACTIONS", "sharpsignalDocId": 44}, {"page": 31, "score": 0.015625, "snippet": "All resources, units, or structures gained from an encounter card go on the territory where the encounter occurred. Benefits gained from encounters do not trigger Recruit Ongoing Bonuses. FACTORY: Only characters may claim Factory cards (1 per player). Actions taken on Factory cards do not trigger R", "headingPath": "HIGHLIGHTED RULES", "sharpsignalDocId": 44}, {"page": 29, "score": 0.015385, "snippet": "Announce your coin total, and the player with the most coins wins! If multiple players have the same total, use the following as tiebreakers (in order): Number of workers, mechs, and structures Power Popularity Number of resource tokens controlled Number of territories controlled Number of star toke", "headingPath": "DECLARING THE WINNER", "sharpsignalDocId": 44}, {"page": 7, "score": 0.015152, "snippet": "POWER TOKEN: Place your power token ( ) on the indicated level of the Power Track (on the game board). Power is the commodity you will spend in combat. COMBAT CARDS: Draw the indicated number of combat cards. The number of combat cards you have is public information, but the content of those cards i", "headingPath": "PLAYER MAT", "sharpsignalDocId": 44}, {"page": 26, "score": 0.014925, "snippet": "Each player starts the game with 2 objective cards that are kept secret from the other players. You may reveal a completed objective card during your own turn before or after you complete a top- or bottom-row action. If you do, place 1 star token on the objective space of the Triumph Track and disca", "headingPath": "O B J E C T I V E S", "sharpsignalDocId": 44}, {"page": 10, "score": 0.014706, "snippet": "Scythe uses an ongoing action-selection mechanism (no rounds or phases). Players take turns one after another until a player places their 6th star on the board, immediately ending the game. On your turn, do the following in sequential order: Place your action token on a different section of your Pla", "headingPath": "GAMEPLAY", "sharpsignalDocId": 44}]
citations (raw): []
boost provenance — errata + base rulebook (E2/E3): gate not evaluated for this ruling (boost, supersedence, and wrench all off at ask time), and the base-rulebook arm went unrecorded for the same reason — the wrench that would have stored it was off; rulesage.errata.boost-enabled=false, rulesage.errata.supersedence-enabled=false
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: Oct 7, 2026 02:29

retrieval — what the search arm returned

score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 Scythe — Rulebook (corpus doc 44)	GAME END AND SCORING	p.28	0.016393 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	164
#2	RULEBOOK Scythe — Rulebook (corpus doc 44)	EDGE CASES	p.28	0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#3	RULEBOOK Scythe — Rulebook (corpus doc 44)	BOTTOM-ROW ACTIONS	p.14	0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#4	RULEBOOK Scythe — Rulebook (corpus doc 44)	HIGHLIGHTED RULES	p.31	0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#5	RULEBOOK Scythe — Rulebook (corpus doc 44)	DECLARING THE WINNER	p.29	0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#6	RULEBOOK Scythe — Rulebook (corpus doc 44)	PLAYER MAT	p.7	0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#7	RULEBOOK Scythe — Rulebook (corpus doc 44)	O B J E C T I V E S	p.26	0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#8	RULEBOOK Scythe — Rulebook (corpus doc 44)	GAMEPLAY	p.10	0.014706 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars

generation — timing and the path taken

timing split: retrieval 85 ms · first delta n/a · total 2908 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 85 ms · ask 2823 ms · gateway work 2908 ms · total 2908 ms
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 33s ago)
stream path: not recorded — this ruling predates the stream-path column (V41)
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: REFUSED_NO_RETRIEVAL — Refused — the rulebook doesn't cover this
abstain rationale: the answerer offered no rationale text with this refusal (or the ruling predates the abstain_rationale column, V41)

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 2), 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.