Ruling — Pagan: Fate of Roanoke

You asked

Before anyone takes a turn, how is everything laid out on the table?

Abstained — no grounded answer; closest passages below counted as honest abstain

Asked with: Pagan: Fate of Roanokebg-319910-en-1e

The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.

RULEBOOK Pagan: Fate of Roanoke — Rulebook · p.28 · Deckbuilding · Rules

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

RULEBOOK Pagan: Fate of Roanoke — Rulebook · p.10 · Cards · Anatomy of a Card

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

RULEBOOK Pagan: Fate of Roanoke — Rulebook · p.31 · Glossary

| List (continued) Ready (state) | Refers to villagers with no action pawns on them. | | Ready (action) | Refers to the action of removing an opponent's action pawn or action pawns from a target villager. | | Remove | Refers to removing something (e.g. card or token) in play. Tokens go to the supply

RULEBOOK Pagan: Fate of Roanoke — Rulebook · p.13 · Event ∂ · Investigation π

An Event is an unexpected and sudden change. It is played and handled instantly and then goes to the discard pile. When you play an Investigation , place it on the village board on a target villager. If an Investigation affects the Witch, place it on the Witch's side of the village board (showing a

RULEBOOK Pagan: Fate of Roanoke — Rulebook · p.9 · Action phase · A. Villager action · B. Player board action

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

🔧 debug — where this ruling came from

outcome: ABSTAINED — Abstained — no grounded answer; closest passages below
corpus profile: live
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 243 ms · ask 8048 ms · total 8305 ms
single-flight (PR-5): queued 0 ms · generation 8305 ms
retrieval refs (raw): [{"page": 28, "score": 0.032787, "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": 10, "score": 0.032258, "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}, {"page": 31, "score": 0.031746, "snippet": "| List (continued) Ready (state) | Refers to villagers with no action pawns on them. | | Ready (action) | Refers to the action of removing an opponent's action pawn or action pawns from a target villager. | | Remove | Refers to removing something (e.g. card or token) in play. Tokens go to the supply", "headingPath": "Glossary", "sharpsignalDocId": 507}, {"page": 13, "score": 0.03125, "snippet": "An Event is an unexpected and sudden change. It is played and handled instantly and then goes to the discard pile. When you play an Investigation , place it on the village board on a target villager. If an Investigation affects the Witch, place it on the Witch's side of the village board (showing a ", "headingPath": "Event ∂ · Investigation π", "sharpsignalDocId": 507}, {"page": 9, "score": 0.030769, "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": 30, "score": 0.030303, "snippet": "| List | | | Add | Adding the specified tokens or cards to what is already present. | | Blank | Treating a specific part of a card as if it wasn't there. Everything else still applies. E.g. When the text box of an Ally is treated as blank, the Hunter would still have to pay the Upkeep cost , to keep", "headingPath": "Glossary", "sharpsignalDocId": 507}, {"page": 27, "score": 0.029851, "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.029412, "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}]
citations (raw): []
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: no past answered ruling for this game matched closely enough
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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507)	Deckbuilding · Rules	p.28	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)	Cards · Anatomy of a Card	p.10	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)	Glossary	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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507)	Event ∂ · Investigation π	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 Pagan: Fate of Roanoke — Rulebook (corpus doc 507)	Action phase · A. Villager action · B. Player board action	p.9	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)	Glossary	p.30	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 set / Factions & Scenario cards · Scenario cards	p.27	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)	Game Setup	p.6	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

#	document	heading	page	quote chars

generation — timing and the path taken

timing split: retrieval 243 ms · first delta 8183 ms · total 8305 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 8048 ms · gateway work 8305 ms · total 8305 ms
tokens in (the prompt the answerer read): 3825
tokens out (what the answerer generated): 9
tok/sec: 136.4 tok/sec — 9 output tokens in 0.066 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 4s 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: ABSTAINED — Abstained — no grounded answer; closest passages below
abstain rationale: I don't have enough information.
the answerer's own words, verbatim — hostile corpus/LLM text, rendered escaped

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 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.