You asked
How do I set up the game?
Answered counted as answeredAsked with: Dunebg-283355-en-1e
1. Place all spice tokens in the Spice Bank [1]. 2. Shuffle the Spice Deck and Treachery Deck and place them face down next to the game board [1]. 3. Players take their Player Shields and player sheets [2]. 4. Players set up their factions [2]. 5. Players choose factions by either using faction cards from the Prediction Deck to randomly determine what faction each player will play (shuffling the cards and dealing 1 card to each player), or by having each player randomly draw a card from the Bene Gesserit turn prediction cards and selecting a faction in the order of their drawn card, with the highest card choosing first [1]. 6. Players may swap factions with each other at this point if they wish [1]. 7. Players place their Player Marker on the player circle closest to their shield and seat at the table [3].
🔧 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 230 ms · ask 9884 ms · total 316759 ms
- single-flight (PR-5)
- queued 306636 ms · generation 10123 ms
- retrieval refs (raw)
- [{"page": 6, "score": 0.047371, "snippet": "Place all spice tokens in the Spice Bank. 'I must not fear. Fear is the mind-killer. Fear is the little-death that brings total obliteration. The Spice Deck and Treachery Deck are shuffled and placed face down next to the game board. Played cards will be piled face up next to the decks as discards a", "headingPath": "SET-UP FOR PLAY", "sharpsignalDocId": 104}, {"page": 6, "score": 0.045724, "snippet": "For 4 player, consider leaving out both the Spacing Guild and Bene Gesserit, while for 5 player games try playing with no Bene Gesserit. Players take their Player Shields and player sheets and set up their factions as follows.", "headingPath": "Four & Five player games", "sharpsignalDocId": 104}, {"page": 10, "score": 0.032787, "snippet": "Each player picks up a Battle Wheel and secretly dials a number from zero to the number of forces they have in the disputed territory. Both players will lose the number of forces dialed on the Battle Wheel.", "headingPath": "Battle Wheel", "sharpsignalDocId": 104}, {"page": 6, "score": 0.032258, "snippet": "Players place their Player Marker on the player circle closest to their shield and seat at the table.", "headingPath": "1. Positions", "sharpsignalDocId": 104}, {"page": 7, "score": 0.03125, "snippet": "The first time the storm is moved, the Storm Marker is placed at a random location along the map edge using the following procedure. The two players whose player circles are nearest on either side of the Storm Start Sector will secretly dial a number from 0 to 20 on the wheels. The two numbers are s", "headingPath": "First Storm", "sharpsignalDocId": 104}, {"page": 4, "score": 0.030769, "snippet": "The Rulebook contains the Basic Game and Advanced Game Sections as well as Strategy Hints, Q&A, and Dune Synopsis. There are 6 sequence of play quick reference cards to help you keep track of the order that everything happens in a turn. SPICE BLOW", "headingPath": "Rulebook, Quick Start Guide, & Quick Reference cards", "sharpsignalDocId": 104}, {"page": 13, "score": 0.030303, "snippet": "The Basic Game is changed by increasing the number of Spice Blows, adding a spice advantage for holding a city or Tuek's Sietch , (the smuggler stronghold), an enhanced Karama Card, and an advanced battle system.", "headingPath": "INTRODUCTION", "sharpsignalDocId": 104}, {"page": 4, "score": 0.029412, "snippet": "The game board is a map of the planet Dune showing four types of territories: Sand: Yellow or tan with a single border. Rock: Brown with double borders. Strongholds: Red brown with triple borders. Polar Sink: Mottled white with a double border. Some territories are marked with a Spice Blow icon to s", "headingPath": "Game Board", "sharpsignalDocId": 104}]
- citations (raw)
- [{"page": 6, "quote": null, "headingPath": "SET-UP FOR PLAY", "sharpsignalDocId": 104}, {"page": 6, "quote": null, "headingPath": "Four & Five player games", "sharpsignalDocId": 104}, {"page": 6, "quote": null, "headingPath": "1. Positions", "sharpsignalDocId": 104}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 104 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 104 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 6, 2026 14:13
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 Dune — Rulebook (corpus doc 104) | SET-UP FOR PLAY | p.6 | 0.047371 (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 Dune — Rulebook (corpus doc 104) | Four & Five player games | p.6 | 0.045724 (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)) | 226 |
| #3 | RULEBOOK Dune — Rulebook (corpus doc 104) | Battle Wheel | p.10 | 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)) | 206 |
| #4 | RULEBOOK Dune — Rulebook (corpus doc 104) | 1. Positions | p.6 | 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)) | 101 |
| #5 | RULEBOOK Dune — Rulebook (corpus doc 104) | First Storm | p.7 | 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 |
| #6 | RULEBOOK Dune — Rulebook (corpus doc 104) | Rulebook, Quick Start Guide, & Quick Reference cards | p.4 | 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)) | 247 |
| #7 | RULEBOOK Dune — Rulebook (corpus doc 104) | INTRODUCTION | p.13 | 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)) | 212 |
| #8 | RULEBOOK Dune — Rulebook (corpus doc 104) | Game Board | p.4 | 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 Dune — Rulebook (corpus doc 104) | SET-UP FOR PLAY | p.6 | no quote on the wire |
| [2] | RULEBOOK Dune — Rulebook (corpus doc 104) | Four & Five player games | p.6 | no quote on the wire |
| [3] | RULEBOOK Dune — Rulebook (corpus doc 104) | 1. Positions | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 230 ms · first delta 8821 ms · total 316759 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 306636 ms · retrieval 230 ms · ask 9884 ms · gateway work 10123 ms · total 316759 ms
- tokens in (the prompt the answerer read)
- 1721
- tokens out (what the answerer generated)
- 183
- tok/sec
- 148.1 tok/sec — 183 output tokens in 1.236 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 59s 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)
-
set up
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 35), 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.