You asked
Before anyone takes a turn, how is everything laid out on the table?
Answered counted as answeredAsked with: Runewarsbg-59294-en-1e
Before anyone takes a turn, the following steps are performed in order: 1. Shuffle the deck of Fate cards and deal one card to each player; the player with the highest numbered card is the first player [1]. 2. Starting with the first player and proceeding clockwise, each player chooses a faction and receives all components for that faction, including the faction sheet, plastic figures, home realm map tile, activation markers, and Order cards [1]. 3. Players create the game board using map tiles [1]. 4. Players place required neutral units into each area as indicated by an image in the area (if any) [1]. 5. Randomize city tokens and place one faceup on each city space of the game board [1]. 6. Remove Quest cards from the deck that refer to areas not part of the game board, add each player's Setup Quest cards to the Quest deck, and shuffle thoroughly [1]. 7. Each player sets resource dials on their faction sheet to the starting resources; each player then receives the amount of influence tokens and Tactics cards indicated on the bottom of their faction sheet [1]. 8. Starting with the first player and proceeding clockwise, each player places one stronghold token in any area of his home realm, recruits units using starting resources and places them in any areas of his home realm, and receives two dragon rune tokens and one false rune token to place one rune token in each area of his home realm (limited to one per area) [1]. 9. Each player receives two Quest cards and places them in his hand [1].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 265 ms · ask 13965 ms · total 14242 ms
- single-flight (PR-5)
- queued 0 ms · generation 14242 ms
- retrieval refs (raw)
- [{"page": 7, "score": 0.032787, "snippet": "The first player to control six areas containing dragon runes immediately wins the game. Each player begins the game with two dragon runes and can acquire more by conquering opponents' areas, obtaining Reward cards, fulfilling criteria on Objective cards, and as prompted by Season and Title cards. S", "headingPath": "Object of the Game · Pre-game Setup", "sharpsignalDocId": 508}, {"page": 8, "score": 0.032258, "snippet": "To do so, he simply chooses one home realm setup marker and replaces it with his home realm tile so that two areas of his home realm occupy the marker's previous space. A home realm may be placed in any orientation of its controller's choice. Home realm areas may never be adjacent to areas of anothe", "headingPath": "Map Setup", "sharpsignalDocId": 508}, {"page": 31, "score": 0.031746, "snippet": "If players run out of activation tokens, damage tokens, defeated hero markers, influence tokens, or training tokens, they should use a suitable replacement (such as a coin or bead). All other cards, tokens, and figures are limited to those provided in the game. If a deck of cards runs out, players s", "headingPath": "Component L imitations · Player Elimination · Play Order and Ties", "sharpsignalDocId": 508}, {"page": 15, "score": 0.03125, "snippet": "Home Realm: · Each faction's three starting areas. Players always control areas in their home realm (even if they do not have any units or strongholds present) unless enemy units are present. Areas of a home realm are never considered empty. Neutral Area: · Any area that contains neutral units and i", "headingPath": "Frequently Used Terms", "sharpsignalDocId": 508}, {"page": 8, "score": 0.030769, "snippet": "Before playing each game, players perform the following steps in order: Choose First Player: 1. Shuffle the deck of Fate cards and deal one card to each player. The player with the highest numbered card (listed on the bottom center) is selected as the first player . This player chooses his faction f", "headingPath": "Setup", "sharpsignalDocId": 508}, {"page": 22, "score": 0.030303, "snippet": "Each battle has up to five different combat rounds. The first round consists of all 'Initiative 1' units attacking, followed by the second round in which all 'Initiative 2' units attack, and so on. Each player chooses one of his unit types of the appropriate initiative to fight as follows: Attacker ", "headingPath": "Rounds of Combat", "sharpsignalDocId": 508}, {"page": 16, "score": 0.029851, "snippet": "The Human player is resolving a 'Strategize' Order 1. card during Spring. Using the card's primary ability, he moves two of his Footmen into an adjacent friendly area. He then moves one of his Knights from a different area into an adjacent area. Note that there is only one area that the Knight could", "headingPath": "Strategize Order Example", "sharpsignalDocId": 508}, {"page": 28, "score": 0.029412, "snippet": "After four rounds of a duel have been resolved, or a hero has been defeated, the duel is over. All damage dealt to a hero remains on its Hero card (unless the Hero was defeated). Each hero that was not defeated in the duel remains in the area (he is not forced to retreat). A hero that starts a duel ", "headingPath": "Duels", "sharpsignalDocId": 508}]
- citations (raw)
- [{"page": 8, "quote": null, "headingPath": "Setup", "sharpsignalDocId": 508}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 508 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 508 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)
- debug row retained until
- Nov 7, 2026 06:00
retrieval — what the search arm returned
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 Runewars — Rulebook (corpus doc 508) | Object of the Game · Pre-game Setup | p.7 | 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 |
| #2 | RULEBOOK Runewars — Rulebook (corpus doc 508) | Map Setup | p.8 | 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 |
| #3 | RULEBOOK Runewars — Rulebook (corpus doc 508) | Component L imitations · Player Elimination · Play Order and Ties | p.31 | 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 |
| #4 | RULEBOOK Runewars — Rulebook (corpus doc 508) | Frequently Used Terms | p.15 | 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 Runewars — Rulebook (corpus doc 508) | Setup | p.8 | 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 Runewars — Rulebook (corpus doc 508) | Rounds of Combat | p.22 | 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 Runewars — Rulebook (corpus doc 508) | Strategize Order Example | p.16 | 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 Runewars — Rulebook (corpus doc 508) | Duels | p.28 | 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 |
chosen chunks — what the answer actually cited
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.
| # | document | heading | page | quote chars |
|---|---|---|---|---|
| [1] | RULEBOOK Runewars — Rulebook (corpus doc 508) | Setup | p.8 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 265 ms · first delta 11752 ms · total 14242 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 265 ms · ask 13965 ms · gateway work 14242 ms · total 14242 ms
- tokens in (the prompt the answerer read)
- 4041
- tokens out (what the answerer generated)
- 328
- tok/sec
- 135.7 tok/sec — 328 output tokens in 2.417 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 19s 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
- 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 439), 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.