Ruling — Star Wars: Rebellion

You asked

How do I take my turn?

Answered counted as answered

Asked with: Star Wars: Rebellionbg-187645-en-1e

During the Command Phase, players take turns activating systems or revealing missions.[1] The Rebel player takes the first turn, followed by the Imperial player.[1] In a Team Game, players take turns following the initiative number shown in their leader pool, starting with #1, then #2, etc..[1]

During a player's turn in a Team Game, the player can:

1. Activate a system using one of his leaders.[1]

2. Reveal a mission that one of his leaders is assigned to.[1]

3. Pass.[1]

To activate a system, follow these steps:

1. Place Leader: The player takes a leader from his leader pool and places it in any system (a leader without tactic values cannot activate a system).[2]

2. Move Units: The player can move his units from adjacent systems to this system.[2]

3. Reveal Base: If Imperial ground units moved into a system, the Rebel player must declare whether the base is in the system; if so, the base is revealed.[2]

4. Combat: If there are Imperial and Rebel units in the same system and the same theater, they resolve combat.[2]

5. Subjugate: If there is an Imperial ground unit in the system and it does not have Imperial loyalty, place a subjugation marker there.[2]

A player may choose to pass at any time during the Command Phase.[1] When a player passes, they cannot use their leaders to reveal missions or activate systems for the rest of that Command Phase.[1]

[1] RULEBOOK Star Wars: Rebellion — Rulebook · p.6 · COMMAND PHASE · COMPONENT LIMITATIONS

[2] RULEBOOK Star Wars: Rebellion — Rulebook · p.2 · ACTIVATING SYSTEMS

The book has spoken.

🔧 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 96 ms · ask 4200 ms · total 4303 ms
single-flight (PR-5): queued 0 ms · generation 4303 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 6, "score": 0.047163, "snippet": "During the Command Phase, players take turns activating systems or revealing missions. b The Rebel player takes the first turn during the Command Phase, followed by the Imperial player. b When placing a leader in a system, it does not matter where the leader is placed within the system. The leader w", "headingPath": "COMMAND PHASE · COMPONENT LIMITATIONS", "sharpsignalDocId": 256}, {"page": 4, "score": 0.04598, "snippet": "When a player moves units to a system that contains his opponent's units, a combat is resolved. Combat is only resolved if both players have units in the same theater. 1 . Add Leader: If a player does not have a leader with tactic values in the system, he may take one leader from his leader pool and", "headingPath": "COMBAT", "sharpsignalDocId": 256}, {"page": 8, "score": 0.032787, "snippet": "To reveal a mission, perform the following steps: 1 . Flip Card Faceup: The player flips one of his mission cards faceup and reads the card aloud. Team Game: A player can only reveal a mission card that one of his leaders is assigned to. The player who reveals the card rolls dice and makes all decis", "headingPath": "REVEALING A MISSION", "sharpsignalDocId": 256}, {"page": 12, "score": 0.032258, "snippet": "During the Refresh Phase, players perform cleanup steps in preparation for the next game round: 1 . Retrieve Leaders: Players return all their leaders from the game board to their leader pools. If a leader is still on a mission card, it returns to the leader pool, and the card returns to its owner's", "headingPath": "REFRESH PHASE", "sharpsignalDocId": 256}, {"page": 4, "score": 0.031746, "snippet": "Although a player may try to bluff and mislead his opponent about his intentions and the location of the Rebel base, there are a few rules that must always be observed. b If an ability requires the Rebel player to resolve an effect in the Rebel base's system (not the 'Rebel Base' space), he must do ", "headingPath": "CHEATING", "sharpsignalDocId": 256}, {"page": 2, "score": 0.03125, "snippet": "Activating a system using a leader is how players move their units and initiate combat during the Command Phase. T o activate a system, follow these steps: 1 . Place Leader: The player takes a leader from his leader pool and places it in any system. A leader that does not have tactic values cannot a", "headingPath": "ACTIVATING SYSTEMS", "sharpsignalDocId": 256}, {"page": 15, "score": 0.030303, "snippet": "This section of the Rules Reference contains the complete rules for setting up a game of Star Wars: Rebellion . These rules include the advanced rules found in the back of the Learn to Play booklet. After players have played their first game, they should follow the setup rules on this page for all f", "headingPath": "APPENDIX: COMPLETE SETUP", "sharpsignalDocId": 256}, {"page": 11, "score": 0.029412, "snippet": "When the time marker advances to a space that contains a recruit icon, players recruit leaders. Recruit icon To recruit leaders, each player draws two action cards, chooses one leader on either of those cards, and places that leader in his leader pool. Each player keeps his chosen action card facedo", "headingPath": "RECRUITING", "sharpsignalDocId": 256}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 6, "quote": null, "headingPath": "COMMAND PHASE · COMPONENT LIMITATIONS", "sharpsignalDocId": 256}, {"page": 2, "quote": null, "headingPath": "ACTIVATING SYSTEMS", "sharpsignalDocId": 256}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 256 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 256 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.91439 of 1133 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 19, 2026 15:12 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 Star Wars: Rebellion — Rulebook (corpus doc 256)	COMMAND PHASE · COMPONENT LIMITATIONS	p.6	0.047163 (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 Star Wars: Rebellion — Rulebook (corpus doc 256)	COMBAT	p.4	0.04598 (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 Star Wars: Rebellion — Rulebook (corpus doc 256)	REVEALING A MISSION	p.8	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
#4	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	REFRESH PHASE	p.12	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
#5	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	CHEATING	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
#6	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	ACTIVATING SYSTEMS	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
#7	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	APPENDIX: COMPLETE SETUP	p.15	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 Star Wars: Rebellion — Rulebook (corpus doc 256)	RECRUITING	p.11	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

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 43 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 Star Wars: Rebellion — Rulebook (corpus doc 256)	COMMAND PHASE · COMPONENT LIMITATIONS	p.6	#1	0.047163 (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 Star Wars: Rebellion — Rulebook (corpus doc 256)	RETREATING	p.5	#9	0.014493 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#3	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	ENDING COMBAT · RESOLVING AN ATTACK	p.4	#17	0.012987 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#4	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	CURRENT PLAYER · DAMAGE · DEATH STAR · BUILDING A DEATH STAR · DESTROYING A DEATH STAR	p.6	#39	0.010101 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#5	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	APPENDIX: COMPLETE SETUP	p.15	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	APPENDIX: COMPLETE SETUP	p.15	#10	0.014286 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#7	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	ACTIVATING SYSTEMS	p.2	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	COMBAT	p.4	#2	0.04598 (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 Star Wars: Rebellion — Rulebook (corpus doc 256)	COMMAND PHASE · COMPONENT LIMITATIONS	p.6	no quote on the wire
[2]	RULEBOOK Star Wars: Rebellion — Rulebook (corpus doc 256)	ACTIVATING SYSTEMS	p.2	no quote on the wire

generation — timing and the path taken

timing split: retrieval 96 ms · first delta 2667 ms · total 4303 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 96 ms · ask 4200 ms · gateway work 4303 ms · total 4303 ms
tokens in (the prompt the answerer read): 3894
tokens out (what the answerer generated): 327
tok/sec: 205.1 tok/sec — 327 output tokens in 1.594 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 33s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 2s 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 181), 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.