Ruling — Reavers of Midgard

You asked

How do I setup the game?

Answered counted as answered

Asked with: Reavers of Midgardbg-242684-en-1e

1. Set the Game Board in the middle of the playing area, and place the Round Tracker on the space labeled 1.[1]

2. Give the Start Player marker to whomever most recently won glory in battle, or select a start player at random.[1]

3. In a three-player game, give the first player the Honor Ship token.[1]

4. In clockwise order, the Start Player takes 4 Food tokens, the second player takes 5 Food, the third player takes 6 Food, and the fourth player takes 7 Food.[1]

5. Each player places their score tracker at the 0 marker on the Glory track.[1]

6. Separate the Sea Journey, Sea Battle, Village Spoils, Keep Spoils, Reaver, and Prophecy cards, shuffle each deck separately, and place them on their corresponding spaces on the Game Board.[1]

7. Each player takes 2 Reaver cards from the deck.[1]

8. Players roll the dice indicated on the top left of each of these Reaver cards and place them on their Player Board.[1]

9. Each player decides whether to Rally, Speculate, or Promote the Reavers according to the Recruit Reavers rules.[1]

10. At each Action Location, fill the spaces with cards according to the number of players.[1][2][3]

11. Specifically, place Sea Battle cards face up in each card space.[2][3]

12. Place Village Spoils cards face up in each card space.[2][3]

13. Place Keep Spoils cards face up in each card space.[2][3]

14. Place Reaver cards face up in each card space.[2][3]

15. For Trading with Villages, place a Prophecy card face up in each of the card spaces, then roll and place two of each color Crew dice in the designated dice spaces.[2][3]

16. Place the Ship Upgrade tokens at the Raid Villages Action Location on their corresponding spaces.[1]

17. Sort the Territory tiles by type, shuffle them, and place them on their corresponding spaces.[1]

18. Place the Dice, Food, Favor, Terror, Wall, Farm, and Tower tokens in a supply accessible to all players.[1]

[1] RULEBOOK Reavers of Midgard — Rulebook · p.4

[2] RULEBOOK Reavers of Midgard — Rulebook · p.6 · components

[3] RULEBOOK Reavers of Midgard — Rulebook · p.6

That settles it — whose turn was it?

🔧 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 243 ms · ask 4166 ms · total 4412 ms
single-flight (PR-5): queued 0 ms · generation 4412 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 4, "score": 0.048916, "snippet": "game setup 1 Player Board 1 Longship pawn and 1 score tracker (In a two-player game, give each player 2 Longship pawns) 1 Favor token 1 2 3 4 5 6 7 8 9 10 11 12 Set the Game Board in the middle of the playing area, and place the Round Tracker on the space labeled 1. (The displayed board is for 3-4 p", "headingPath": "", "sharpsignalDocId": 1108}, {"page": 6, "score": 0.048139, "snippet": "Game setup (cont.) Trading with Villages: Place a Prophecy card face up in each of the card spaces. Then, roll and place two of each color Crew dice in the designated dice spaces. During initial Game Setup, and during each cleanup phase, set up each of the Action Locations as described below: Sea Ba", "headingPath": "", "sharpsignalDocId": 1108}, {"page": 6, "score": 0.048131, "snippet": "During initial Game Setup, and during each cleanup phase, set up each of the Action Locations as described below: Sea Battle: Place Sea Battle cards face up in each of the card spaces according to the number of players. Trading with Villages: Place a Prophecy card face up in each of the card spaces.", "headingPath": "components", "sharpsignalDocId": 1108}, {"page": 13, "score": 0.03125, "snippet": "At the end of each round of the game, players complete the following steps to prepare for the next round: If you are on Round 6, proceed to final scoring. Otherwise, move the Round marker 1 space clockwise. In a 3-player game, the player with the Honor Ship token passes it clockwise to the next play", "headingPath": "", "sharpsignalDocId": 1108}, {"page": 7, "score": 0.030769, "snippet": "Note: Each Action Location may only be selected once per Round. There are two different kinds of Action Locations, indicated by the color of their banner. RED locations provide an effect and also an additional bonus depending on player order. BLUE locations provide an effect that may be repeated a c", "headingPath": "", "sharpsignalDocId": 1108}, {"page": 8, "score": 0.030303, "snippet": "All activating players gain 2 Reaver cards. Beginning with the active player and proceeding clockwise, each participant chooses a face-up stack of cards from the board or 2 random cards from the Reavers deck. The player who selects this locations gain 2 Favor. The other players receive no bonus. For", "headingPath": "This Action Location has no cost.", "sharpsignalDocId": 1108}, {"page": 8, "score": 0.029851, "snippet": "Note: The bonuses that players receive are based on their proximity to the active player, not on the order of activation. Meaning if the player 1 seat clockwise from the active player chooses to not to pay the cost and participate in the effect of the Action Location, the next player to pay the cost", "headingPath": "The effects of each Action Location are described in detail below. · IMPORTANT TERMS", "sharpsignalDocId": 1108}, {"page": 12, "score": 0.029412, "snippet": "Beginning with the active player and proceeding clockwise, each participant may attempt to Subdue territories a declining number of times. The active player may attempt to Subdue 3 territories. The second player may attempt to Subdue 2 territories. The third and fourth players may attempt to Subdue ", "headingPath": "This Action Location has a variable cost to activate.", "sharpsignalDocId": 1108}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 1108}, {"page": 6, "quote": null, "headingPath": "components", "sharpsignalDocId": 1108}, {"page": 6, "quote": null, "headingPath": "", "sharpsignalDocId": 1108}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1108 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1108 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.88875 of 1564 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 27, 2026 01:56 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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.4	0.048916 (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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.6	0.048139 (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 Reavers of Midgard — Rulebook (corpus doc 1108)	components	p.6	0.048131 (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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.13	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
#5	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)		p.7	0.030769 (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 Reavers of Midgard — Rulebook (corpus doc 1108)	This Action Location has no cost.	p.8	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
#7	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)	The effects of each Action Location are described in detail below. · IMPORTANT TERMS	p.8	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
#8	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)	This Action Location has a variable cost to activate.	p.12	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 31 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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.4	#1	0.048916 (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 Reavers of Midgard — Rulebook (corpus doc 1108)	components	p.6	#3	0.048131 (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 Reavers of Midgard — Rulebook (corpus doc 1108)	This Action Location has a variable cost to activate.	p.12	#8	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
#4	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)	This Action Location has no cost.	p.8	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)	The effects of each Action Location are described in detail below. · IMPORTANT TERMS	p.8	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)		p.2	#10	0.028485 (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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.13	#4	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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.6	#2	0.048139 (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 Reavers of Midgard — Rulebook (corpus doc 1108)		p.4	no quote on the wire
[2]	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)	components	p.6	no quote on the wire
[3]	RULEBOOK Reavers of Midgard — Rulebook (corpus doc 1108)		p.6	no quote on the wire

generation — timing and the path taken

timing split: retrieval 243 ms · first delta 1905 ms · total 4412 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 243 ms · ask 4166 ms · gateway work 4412 ms · total 4412 ms
tokens in (the prompt the answerer read): 2787
tokens out (what the answerer generated): 497
tok/sec: 202.6 tok/sec — 497 output tokens in 2.453 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 23s ago)
gateway schema (read from the running child): schema head 0042_definer_search_path (live revision not readable by this principal)
answerer host (measured by rulesage): reachable (for 60h, checked 1s 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: 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 1038), 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.