You asked
What is the correct arrangement of components at the very beginning of a game?
Answered counted as answeredAsked with: Pagan: Fate of Roanokebg-319910-en-1e
1. Decide who will play as the Witch and who will play as the Hunter [1]. 2. The Witch receives 3 Action pawns (2 ¨ and 1 ≈ ), the Witch player board as well as the green Influence disc [1]. 3. The Hunter takes 3 Action pawns ( ® ), the Hunter player board and the red Influence disc [1]. 4. Place the 3 part village board at the center of the table (1st, 2nd, 3rd ) and put the Enchantment board to one side of it [1]. 5. Place the 9 villagers on the village board corresponding to their symbol and coloring, and. [1] 6. Shuffle the 9 Suspects, matching the villagers on the village board, to form the Suspect deck [1]. 7. The Witch draws the top card of the Suspect deck, keeping it secret from the Hunter [1]. 8. Both players shuffle their 50 cards building their respective decks [1]. 9. Put the remaining tokens ( Clues, Evidence, Secrets and Favors ) in the general supply [1]. 10. Both players draw 3 hand cards from their respective decks and set their Influence disc to 2 [1]. 11. If playing for the first time, place 1 player aid card next to your board [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 272 ms · ask 10088 ms · total 10370 ms
- single-flight (PR-5)
- queued 0 ms · generation 10370 ms
- retrieval refs (raw)
- [{"page": 9, "score": 0.032787, "snippet": "During the Action phase, perform 3 Actions by placing your Action pawns , one at a time, on available action spots to carry out the corresponding action. Note: In the first turn of the game the Witch only has 2 regular Action pawns which they must use to visit villagers of the same faction . Startin", "headingPath": "Action phase · A. Villager action · B. Player board action", "sharpsignalDocId": 507}, {"page": 27, "score": 0.032258, "snippet": "Besides the 50-card deck, each player also selects one of the factions for the game. A faction consists of three like-colored villagers that share a common faction name and can be easily identified with the Villager Overview Cards . The Witch selects the Red Faction , the Witch Hunter selects the Bl", "headingPath": "Villager set / Factions & Scenario cards · Scenario cards", "sharpsignalDocId": 507}, {"page": 6, "score": 0.031746, "snippet": "♦ Decide who will play as the Witch and who will play as the Hunter. ♦ The Witch receives 3 Action pawns (2 ¨ and 1 ≈ ), the Witch player board as well as the green Influence disc. ♦ The Hunter takes 3 Action pawns ( ® ) , the Hunter player board and the red Influence disc. ♦ Place the 3 part villag", "headingPath": "Game Setup", "sharpsignalDocId": 507}, {"page": 28, "score": 0.03125, "snippet": "The decks included in the base game are constructed to interact well with each other, and to provide a balanced game for beginners and experienced players alike. Pagan: Fate of Roanoke has been designed as an expandable game with new cards and other content added through expansions. Each of these ex", "headingPath": "Deckbuilding · Rules", "sharpsignalDocId": 507}, {"page": 29, "score": 0.030769, "snippet": "These starter decks are used for Scenario 1 - Welcome to Roanoke. It provides a simple and fast way to enjoy a full game of Pagan with the added bonus of being short and showing you the basics. Since it is very fast, expert players may enjoy it for its unforgiving nature. The starter set only needs ", "headingPath": "Starter deck", "sharpsignalDocId": 507}, {"page": 11, "score": 0.030303, "snippet": "Factions are used in scenarios. See Advanced rules on page 25. There are 9 villagers in a game of Pagan. The villagers are located on the village board and consist of 3 blue villagers, 3 red villagers and 3 green villagers. A villager is either ready, occupied or eliminated. A villager is occupied i", "headingPath": "Faction name · Villager Cards · Suspect Cards", "sharpsignalDocId": 507}, {"page": 5, "score": 0.029851, "snippet": "♦ 3 red , 3 blue & 3 green Villagers ♦ 9 corresponding Suspects ♦ 3 Villager overview cards On the left side you can find a list of all Hunter Actions. Locations as well as Allies must be placed on the designated spaces on the right. See page 14 for more details. On the left side you can find a list", "headingPath": "Villager and Suspect Cards · Hunter Board · Witch Board", "sharpsignalDocId": 507}, {"page": 10, "score": 0.029412, "snippet": "Pagan includes a variety of card types. You play cards by visiting a villager with a 'play' action or by using a 'play' effect of another card or board item. When you play a card with a one-time effect - i. e. Charms or Events , apply the card effect immediately. Then place the card in your discard ", "headingPath": "Cards · Anatomy of a Card", "sharpsignalDocId": 507}]
- citations (raw)
- [{"page": 6, "quote": null, "headingPath": "Game Setup", "sharpsignalDocId": 507}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 507 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 507 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:10
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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Action phase · A. Villager action · B. Player board action | p.9 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Villager set / Factions & Scenario cards · Scenario cards | p.27 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Game Setup | 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 |
| #4 | RULEBOOK Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Deckbuilding · Rules | p.28 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Starter deck | p.29 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Faction name · Villager Cards · Suspect Cards | p.11 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Villager and Suspect Cards · Hunter Board · Witch Board | p.5 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Cards · Anatomy of a Card | p.10 | 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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507) | Game Setup | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 272 ms · first delta 8217 ms · total 10370 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 272 ms · ask 10088 ms · gateway work 10370 ms · total 10370 ms
- tokens in (the prompt the answerer read)
- 4072
- tokens out (what the answerer generated)
- 291
- tok/sec
- 138.2 tok/sec — 291 output tokens in 2.105 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 27s 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
- BEGIN — "begin" / "beginning"
- matched words (in the normalized question)
-
beginning
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 438), 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.