Ruling — Root — RuleSage

You asked

How do I setup the game?

Answered counted as answered

Asked with: Rootbg-237182-en-1e

If any players are new to the game, use the Standard Setup.[1]

**Standard Setup**

1. Assign one faction to each player in any way, determine the starting player and seating order randomly, and each player takes their chosen faction board and the pieces listed on its back.[2]

2. Each player places their score marker on '0' on the score track.[2]

3. If playing with two players, remove all four dominance cards from the deck, shuffle the deck, and each player draws three cards.[2]

4. Place a ruin in each slot on the map marked with an 'R' (four in total).[2]

5. Place these items on the corresponding spaces of the item supply near the top of the map: 2 M, 2 B, 1 C, 1 H, 2 S, 2 T, 2 X.[2]

6. Hand out the 16 faction overview cards as desired, and place the two battle dice near the map.[2]

7. In setup order (A, B, C, etc.), each player follows their faction's setup instructions, listed in their rules section and on the back of their faction board.[2]

[1] RULEBOOK Root — Law of Root · p.4 · 5. Setup

[2] RULEBOOK Root — Law of Root · p.5 · 5.1 Standard Setup

Strategy guides → — community tips, kept separate from rulings

🔧 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 124 ms · ask 5637 ms · total 5765 ms
single-flight (PR-5): queued 0 ms · generation 5765 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 3, "score": 0.048652, "snippet": "Follow the modified setup rules on the first two pages of the Walking /Through Root booklet. Once you have set up the game, give the players an overview of Root's theme and the victory conditions for each faction. Now you're ready to play.", "headingPath": "Setup", "sharpsignalDocId": 75}, {"page": 23, "score": 0.046927, "snippet": "Before playing on the winter map, take out the 12 suit markers, flip them face down, and shuffle them. /Then, place one suit marker near each clearing on the map. A/fter a suit marker has been added to each clearing, flip them all over, and set up the game as normal. Note the different placement of ", "headingPath": "Setup", "sharpsignalDocId": 75}, {"page": 4, "score": 0.032787, "snippet": "If any players are new to the game, use the Standard Setup (5.1) If everyone has played and you want more variety, use the Advanced Setup (Appendix A). If you want to play with five or more factions that would start in corner clearings, you must use the Advanced Setup.", "headingPath": "5. Setup", "sharpsignalDocId": 56}, {"page": 4, "score": 0.030159, "snippet": "If playing with three players, remove the Vagabond. If playing with two, also remove the Alliance. For more faction mixes, see page 22. Choose Factions. Each player chooses a faction board and takes all of their faction's pieces. 1 st /The back of each faction board lists all of its pieces and gives", "headingPath": "Setup", "sharpsignalDocId": 75}, {"page": 23, "score": 0.028624, "snippet": "As a group, you may choose and set up factions as described in the Standard Setup (5.1) or you may use the faction setup cards included in the Marauder and Homeland Expansions, as described below. A.8.1 Step 1: Create Dra/ft Pool. Agree whether you will omit any factions from the game. You can- not ", "headingPath": "A.8 Step 8: Set Up Factions", "sharpsignalDocId": 56}, {"page": 19, "score": 0.02758, "snippet": "16.3.1 Step 1: Gather Pieces. Form a supply of 20 warriors and 12 enclaves. 16.3.2 Step 2: Place Warriors and Enclave. In a clearing on the river, place 5 warriors and 1 enclave on its Peaceful side. /This is your starting clearing. 16.3.3 Step 3: Remove Dominance. In a two-player game, remove the F", "headingPath": "16.3 Faction Setup", "sharpsignalDocId": 56}, {"page": 3, "score": 0.027253, "snippet": "Give the booklet to the Marquise player and ask them to read the text aloud as they take the actions described. When their turn is over, pass the booklet to the Eyrie player so they can do the same. Continue this until you reach the end. /The booklet also answers some common questions and gives stra", "headingPath": "Play", "sharpsignalDocId": 75}, {"page": 21, "score": 0.026496, "snippet": "During your Daylight, if you have at least 10 victory points, you may play a dominance card into your play area to activate it. Remove your score marker from the score track. For the rest of the game, you can only win by meeting the victory condition listed on your activated dominance card. Gently U", "headingPath": "Changing Your Victory Condition", "sharpsignalDocId": 75}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 4, "quote": null, "headingPath": "5. Setup", "sharpsignalDocId": 56}, {"page": 5, "quote": null, "headingPath": "5.1 Standard Setup", "sharpsignalDocId": 56}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 75 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 75 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.88560 of 778 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 22:16

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 Root — Learning to Play (corpus doc 75)	Setup	p.3	0.048652 (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))	239
#2	RULEBOOK Root — Learning to Play (corpus doc 75)	Setup	p.23	0.046927 (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 Root — Law of Root (corpus doc 56)	5. Setup	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))	269
#4	RULEBOOK Root — Learning to Play (corpus doc 75)	Setup	p.4	0.030159 (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 Root — Law of Root (corpus doc 56)	A.8 Step 8: Set Up Factions	p.23	0.028624 (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 Root — Law of Root (corpus doc 56)	16.3 Faction Setup	p.19	0.02758 (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 Root — Learning to Play (corpus doc 75)	Play	p.3	0.027253 (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 Root — Learning to Play (corpus doc 75)	Changing Your Victory Condition	p.21	0.026496 (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 80 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 Root — Law of Root (corpus doc 56)	5. Setup	p.4	#3	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 + full-text	the re-ranker chose it
#2	RULEBOOK Root — Learning to Play (corpus doc 75)	Setup	p.23	#2	0.046927 (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 Root — Law of Root (corpus doc 56)	5.1 Standard Setup	p.5	#13	0.015873 (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 Root — Law of Root (corpus doc 56)	17.3 Faction Setup	p.20	#16	0.015385 (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 Root — Law of Root (corpus doc 56)	16.3 Faction Setup	p.19	#6	0.02758 (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
#6	RULEBOOK Root — Law of Root (corpus doc 56)	A.8 Step 8: Set Up Factions	p.23	#5	0.028624 (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
#7	RULEBOOK Root — Law of Root (corpus doc 56)	Setup (5.1)	p.32	#15	0.015625 (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
#8	RULEBOOK Root — Learning to Play (corpus doc 75)	Setup	p.3	#1	0.048652 (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 Root — Law of Root (corpus doc 56)	5. Setup	p.4	no quote on the wire
[2]	RULEBOOK Root — Law of Root (corpus doc 56)	5.1 Standard Setup	p.5	no quote on the wire

generation — timing and the path taken

timing split: retrieval 124 ms · first delta 4478 ms · total 5765 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 124 ms · ask 5637 ms · gateway work 5765 ms · total 5765 ms
tokens in (the prompt the answerer read): 2110
tokens out (what the answerer generated): 258
tok/sec: 205.1 tok/sec — 258 output tokens in 1.258 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 3s 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.

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: NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
pattern that matched: SETUP — "setup" / "set up"
matched words (in the normalized question): setup

errata registry — what the gate above had to match against

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