Ruling — Julius Caesar: Caesar, Pompey, and the Roman Civil War

← Julius Caesar: Caesar, Pompey, and the Roman Civil War

You asked

How do I play?

Answered counted as answered

Asked with: Julius Caesar: Caesar, Pompey, and the Roman Civil Warbg-37836-en-1e

The game is played for five Years, each consisting of five game turns.[1] Each game turn follows a specific sequence of three phases:[1]

1. Card Phase

* At the beginning of each Year, the 27 cards are shuffled and six cards are dealt to each player.[1]

* Each player examines their cards and discards one card without revealing it.[1][2]

* Each player starts a game turn by playing one card face-down, which are then revealed.[1]

* The player with the higher Move value on their card is Player 1 for that turn; if the cards are tied, Caesar is Player 1.[1]

* Event cards have special actions that can break normal rules.[3] If both players play Event cards, both events are cancelled and the turn ends.[1]

2. Command Phase

* Player 1 moves and levies (or executes an Event), then Player 2 moves and levies.[3]

* Move: Using Move Points (MP) from the active card, a player may move any/all blocks in one location to adjacent cities or seas.[3][4] Each MP allows one or two cities/seas of movement (Navis can move one or two seas).[3] Blocks that move two cities/seas cannot attack or reinforce.[3] Blocks entering a city or sea containing enemy blocks must stop.[3] Blocks that move cannot move again this turn, except to Retreat or Regroup.[4]

* Levy: After all movement is complete, players choose levies.[3] For each Levy, one step can be added to an existing block, or one new block can be chosen from a player's Levy Pool and deployed on the map at strength I.[3]

3. Battle Phase

* Battles occur between opposing blocks in the same city or sea.[3]

* Player 1 determines the sequence of battles.[3][5]

* In a battle, each firing block rolls dice equal to its current strength; a hit is scored for each roll equal to or lower than the block's firepower.[5]

* Hits are applied immediately and reduce the strongest enemy block at that instant.[5][6]

* If a player attacks via multiple roads/borders, they must declare a Main Attack; other blocks are Reserves and do not fire or take hits in Round 1.[5]

Winter Turn and Victory

* A Year ends after five cards have been played.[2]

* A Winter Turn follows, where players check for victory.[1][2]

* To win, a player must have 10 or more Victory Points (VP).[1] VPs are scored by totaling the value of Friendly cities plus 1 VP for each enemy leader killed.[1]

* If no one has 10 VPs by the end of Year 5, the player with the higher VPs wins; if still tied, the player holding Rome wins; otherwise, it is a draw.[1]

[1] RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook · p.1 · 1.0 INTRODUCTION · 1.1 Players · 1.2 VICTORY · 1.3 CONTENTS · 2.0 Game Turns · 2.1 Card Phase

[2] RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook · p.8 · 8.0 WINTER TURN · 8.1 CLEOPATRA GOES HOME · 8.2 Victory · 8.3 NAVIS to port · 8.4 WINTER SUPPLY · 8.5 Disbanding · …

[3] RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook · p.1 · 2.2 Command Phase · 2.3 Battle Phase · The Roman Calendar · Victory · Event Cards · Game Turn Example

[4] RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook · p.5 · 6.0 COMMAND Phase · 6.1 GROUP Moves · 6.11 Road Limits · 6.12 Attacking · 6.13 Pinning · 6.14 Response Movement · …

[5] RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook · p.6 · 7.3 Battle Reserves · 7.31 Disruption · 7.4 Battle HITS · 7.41 Elephant · 7.42 Ballista · Battle Sequence

[6] RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook · p.6 · Battle Turns · Attacker/Defender · Battle Hits · Pursuit · Treachery

That's the page. Back to the table.

🔧 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 88 ms · ask 5236 ms · total 46693 ms
single-flight (PR-5): queued 41367 ms · generation 5326 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 1, "score": 0.047643, "snippet": "Julius Caesar brings the drama of the most famous and significant Roman Civil War (49-45 BC) to life. Players take control of the legions of Caesar or Pompey and fight to determine the future of Rome republic or empire. The game is intended for two players. One player represents Julius Caesar, the o", "headingPath": "1.0 INTRODUCTION · 1.1 Players · 1.2 VICTORY · 1.3 CONTENTS · 2.0 Game Turns · 2.1 Card Phase", "sharpsignalDocId": 1204}, {"page": 1, "score": 0.045695, "snippet": "Player 1 moves and levies (or executes an Event), then Player 2 moves and levies. Move: Each move allows one Group (any/all blocks in one location) to move one or two cities; Navis can move one or two seas. Blocks cannot attack or reinforce if they move two cities/seas. Blocks entering a city or sea", "headingPath": "2.2 Command Phase · 2.3 Battle Phase · The Roman Calendar · Victory · Event Cards · Game Turn Example", "sharpsignalDocId": 1204}, {"page": 8, "score": 0.045541, "snippet": "A Year ends when all five (5) cards have been played. A Winter Turn now occurs during which players determine if either has won. Play the winter events in the exact order given. Move Cleopatra to Alexandria. If enemy-occupied, she joins that side immediately at her current strength. Determine if one", "headingPath": "8.0 WINTER TURN · 8.1 CLEOPATRA GOES HOME · 8.2 Victory · 8.3 NAVIS to port · 8.4 WINTER SUPPLY · 8.5 Disbanding · …", "sharpsignalDocId": 1204}, {"page": 6, "score": 0.032787, "snippet": "Caesar (A3) and Equitatus (B2) attack Pompey (B3) and Navis (D2). Battle Turn sequence: Caesar : attacking A3 Pompey : defending B3 Caesar Equitatus: attacking B2 Pompey Navis: defending D2 Because both players move before combat, a player can be the Defender in some battles, and the Attacker in oth", "headingPath": "Battle Turns · Attacker/Defender · Battle Hits · Pursuit · Treachery", "sharpsignalDocId": 1204}, {"page": 5, "score": 0.032258, "snippet": "Player 1 Moves and then Levies with the values from his active card, then Player 2 does the same. Command cards have Move Points (MP) of 1 to 4. Each MP allows any/ all block(s) in one location (city or sea) to move to adjacent cities/seas. If not attacking, blocks may continue to the next adjacent ", "headingPath": "6.0 COMMAND Phase · 6.1 GROUP Moves · 6.11 Road Limits · 6.12 Attacking · 6.13 Pinning · 6.14 Response Movement · …", "sharpsignalDocId": 1204}, {"page": 6, "score": 0.031746, "snippet": "Command cards have 1, 2, or 3 Levy Points (LP). Each LP allows: One (1) step to be added to one (1) existing block. Multiple steps can be added to the same block, each for LP1. One (1) new block can be chosen from a player's Levy Pool and deployed in a city at minimum strength. Steps can be added to", "headingPath": "6.4 LEVIES · 7.1 Battle SEQUENCE · 7.2 Battle TURNS", "sharpsignalDocId": 1204}, {"page": 6, "score": 0.030303, "snippet": "When attacking via two or more roads or sea borders, one road/border (Attacker choice) must be declared the Main Attack. Blocks using other roads/borders are Reserves . Blocks moved by Player 2 to reinforce a battle started by Player 1 are also Reserves . Reserve blocks may not fire, retreat, or tak", "headingPath": "7.3 Battle Reserves · 7.31 Disruption · 7.4 Battle HITS · 7.41 Elephant · 7.42 Ballista · Battle Sequence", "sharpsignalDocId": 1204}, {"page": 3, "score": 0.029851, "snippet": "The mapboard depicts the Mediterranean Sea and surrounding territory. The Caesar player sits at the north edge of the map, Pompey player at the south edge. Blocks on the map must be located on cities or seas. Navis must be located on seas or in port cities. Cities govern the movement and location of", "headingPath": "4.0 MAPBOARD · 4.1 Locations · 4.2 CITIES · 4.21 City Control · 4.3 Roads · 4.31 Road Classes · …", "sharpsignalDocId": 1204}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 1, "quote": null, "headingPath": "1.0 INTRODUCTION · 1.1 Players · 1.2 VICTORY · 1.3 CONTENTS · 2.0 Game Turns · 2.1 Card Phase", "sharpsignalDocId": 1204}, {"page": 8, "quote": null, "headingPath": "8.0 WINTER TURN · 8.1 CLEOPATRA GOES HOME · 8.2 Victory · 8.3 NAVIS to port · 8.4 WINTER SUPPLY · 8.5 Disbanding · …", "sharpsignalDocId": 1204}, {"page": 1, "quote": null, "headingPath": "2.2 Command Phase · 2.3 Battle Phase · The Roman Calendar · Victory · Event Cards · Game Turn Example", "sharpsignalDocId": 1204}, {"page": 5, "quote": null, "headingPath": "6.0 COMMAND Phase · 6.1 GROUP Moves · 6.11 Road Limits · 6.12 Attacking · 6.13 Pinning · 6.14 Response Movement · …", "sharpsignalDocId": 1204}, {"page": 6, "quote": null, "headingPath": "7.3 Battle Reserves · 7.31 Disruption · 7.4 Battle HITS · 7.41 Elephant · 7.42 Ballista · Battle Sequence", "sharpsignalDocId": 1204}, {"page": 6, "quote": null, "headingPath": "Battle Turns · Attacker/Defender · Battle Hits · Pursuit · Treachery", "sharpsignalDocId": 1204}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1204 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1204 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.89232 of 2043 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 7, 2026 03:08 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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	1.0 INTRODUCTION · 1.1 Players · 1.2 VICTORY · 1.3 CONTENTS · 2.0 Game Turns · 2.1 Card Phase	p.1	0.047643 (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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	2.2 Command Phase · 2.3 Battle Phase · The Roman Calendar · Victory · Event Cards · Game Turn Example	p.1	0.045695 (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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	8.0 WINTER TURN · 8.1 CLEOPATRA GOES HOME · 8.2 Victory · 8.3 NAVIS to port · 8.4 WINTER SUPPLY · 8.5 Disbanding · …	p.8	0.045541 (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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	Battle Turns · Attacker/Defender · Battle Hits · Pursuit · Treachery	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
#5	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	6.0 COMMAND Phase · 6.1 GROUP Moves · 6.11 Road Limits · 6.12 Attacking · 6.13 Pinning · 6.14 Response Movement · …	p.5	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
#6	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	6.4 LEVIES · 7.1 Battle SEQUENCE · 7.2 Battle TURNS	p.6	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
#7	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	7.3 Battle Reserves · 7.31 Disruption · 7.4 Battle HITS · 7.41 Elephant · 7.42 Ballista · Battle Sequence	p.6	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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	4.0 MAPBOARD · 4.1 Locations · 4.2 CITIES · 4.21 City Control · 4.3 Roads · 4.31 Road Classes · …	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

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 21 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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	2.2 Command Phase · 2.3 Battle Phase · The Roman Calendar · Victory · Event Cards · Game Turn Example	p.1	#2	0.045695 (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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	1.0 INTRODUCTION · 1.1 Players · 1.2 VICTORY · 1.3 CONTENTS · 2.0 Game Turns · 2.1 Card Phase	p.1	#1	0.047643 (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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	Event Cards	p.3	#12	0.028446 (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
#4	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	5.1 Historical DEPLOYMENT · 5.2 Levy Pool · 5.3 FREE DEPLOYMENT · CAESAR, 705 (49 BC) · LEVY POOL · POMPEY, 705 (49 BC)	p.4	#11	0.028718 (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
#5	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	7.3 Battle Reserves · 7.31 Disruption · 7.4 Battle HITS · 7.41 Elephant · 7.42 Ballista · Battle Sequence	p.6	#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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	Battle Turns · Attacker/Defender · Battle Hits · Pursuit · Treachery	p.6	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	6.0 COMMAND Phase · 6.1 GROUP Moves · 6.11 Road Limits · 6.12 Attacking · 6.13 Pinning · 6.14 Response Movement · …	p.5	#5	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))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	8.0 WINTER TURN · 8.1 CLEOPATRA GOES HOME · 8.2 Victory · 8.3 NAVIS to port · 8.4 WINTER SUPPLY · 8.5 Disbanding · …	p.8	#3	0.045541 (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 Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	1.0 INTRODUCTION · 1.1 Players · 1.2 VICTORY · 1.3 CONTENTS · 2.0 Game Turns · 2.1 Card Phase	p.1	no quote on the wire
[2]	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	8.0 WINTER TURN · 8.1 CLEOPATRA GOES HOME · 8.2 Victory · 8.3 NAVIS to port · 8.4 WINTER SUPPLY · 8.5 Disbanding · …	p.8	no quote on the wire
[3]	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	2.2 Command Phase · 2.3 Battle Phase · The Roman Calendar · Victory · Event Cards · Game Turn Example	p.1	no quote on the wire
[4]	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	6.0 COMMAND Phase · 6.1 GROUP Moves · 6.11 Road Limits · 6.12 Attacking · 6.13 Pinning · 6.14 Response Movement · …	p.5	no quote on the wire
[5]	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	7.3 Battle Reserves · 7.31 Disruption · 7.4 Battle HITS · 7.41 Elephant · 7.42 Ballista · Battle Sequence	p.6	no quote on the wire
[6]	RULEBOOK Julius Caesar: Caesar, Pompey, and the Roman Civil War — Rulebook (corpus doc 1204)	Battle Turns · Attacker/Defender · Battle Hits · Pursuit · Treachery	p.6	no quote on the wire

generation — timing and the path taken

timing split: retrieval 88 ms · first delta n/a · total 46693 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 41367 ms · retrieval 88 ms · ask 5236 ms · gateway work 5326 ms · total 46693 ms
tokens in (the prompt the answerer read): 4072
tokens out (what the answerer generated): 655
tok/sec: 199.8 tok/sec — 655 output tokens in 3.279 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 59s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 8s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
stream path: requested, but the gateway emitted no delta — the whole answer arrived at once (the child's stream flag off, or a non-streaming backend)
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 1134), 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.