You asked
How do I play?
Answered counted as answeredAsked with: Roads & Boatsbg-875-en-1e
The table has its answer — dice up.
🔧 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 156 ms · ask 3655 ms · total 3812 ms
- single-flight (PR-5)
- queued 0 ms · generation 3812 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 7, "score": 0.04866, "snippet": "sources have been used elsewhere. A river may not run off the map. Place the plastic sheet over the map. Make sure the entire map is covered. Fix the sheet in place with adhesive tape that can be removed easily after playing. Covering the Map Put the praying figures in a cup and take them out one by", "headingPath": "SETTING/.notdefUP · DETERMININGTHESTARTINGSEQUENCE · STARTINGPLACESANDRESOURCES · ORDEROFPLAY", "sharpsignalDocId": 680}, {"page": 17, "score": 0.048652, "snippet": "N most cases, all players play simultaneously. However, on some occasions a player may want to perform an action before or after another player, so that conflict arises. In that case it is necessary to determineaplaying sequence. Other types of conflict do not occur. It is impossible under any circu", "headingPath": "CONFLICT · CHOOSINGAPLAYINGSEQUENCE", "sharpsignalDocId": 680}, {"page": 6, "score": 0.046875, "snippet": "There are two ways to make a map. Inexperienced players are advised to select one of the maps provided in the scenario book. More experienced players may want to makeamapoftheirownusingthefollowingrules. Determine how big the map is going to be. As a rough estimate, use about ten land tiles per play", "headingPath": "SETTING/.notdefUP", "sharpsignalDocId": 680}, {"page": 6, "score": 0.046239, "snippet": "a game board in two parts, featuring the temple row on top (number 1 in the figure on the right), the wonder (2), the phase chart indicating the four phase of the game (3), and the sequence chart (4) with numbers 1 to 6; one more glass stone (to use on the phase chart); rule book and scenario book; ", "headingPath": "SETTING/.notdefUP · FIRST-TIMEPREPARATIONS · SETTINGUP · CREATINGTHEWORLD", "sharpsignalDocId": 680}, {"page": 5, "score": 0.046154, "snippet": "OADS & BOATS is played in turns. Each turn consists of four phases. In each phase, all players play simultaneously. Players first go through a phase in which all buildings produce goods. There are which produce goods every production phase (such as a woodcutter, which produces one pile of trunks eve", "headingPath": "SUMMARY · MATERIAL", "sharpsignalDocId": 680}, {"page": 18, "score": 0.04598, "snippet": "See Figure 1 on next page - Figure a shows the row at the temple. Production Both mines produce gold. Blue declares he wants the order of play to be determined. Starting from Red, each player has the chance to stop praying. Red decides to be pious. Blue, however, stops praying and moves his praying ", "headingPath": "EXAMPLEOFACONFLICTROUND", "sharpsignalDocId": 680}, {"page": 3, "score": 0.045009, "snippet": "4 In , each player builds up a civi- lization over a long period of time, like in many other games. Unlike most games, however, is not about warfare, population growth, city or statebuilding. The emphasis instead is on logistics, or rather: on transport. Each player starts the game with three donkey", "headingPath": "", "sharpsignalDocId": 680}, {"page": 18, "score": 0.044337, "snippet": "last, Blue cannot predict which mine will be closed off, and therefore cannot prevent it. Blue moves a donkey with two boards to A. The donkey on the mine stays there and the third Blue donkey moves to the second mine. Yellow moves the donkey with two stones to mine 2. Yellow's other donkeys stay pu", "headingPath": "CONFLICT", "sharpsignalDocId": 680}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 5, "quote": null, "headingPath": "SUMMARY · MATERIAL", "sharpsignalDocId": 680}, {"page": 7, "quote": null, "headingPath": "SETTING/.notdefUP · DETERMININGTHESTARTINGSEQUENCE · STARTINGPLACESANDRESOURCES · ORDEROFPLAY", "sharpsignalDocId": 680}, {"page": 17, "quote": null, "headingPath": "CONFLICT · CHOOSINGAPLAYINGSEQUENCE", "sharpsignalDocId": 680}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 680 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 680 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.91318 of 933 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row recorded
- Aug 28, 2026 12:44 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 Roads & Boats — Rulebook (corpus doc 680) | SETTING/.notdefUP · DETERMININGTHESTARTINGSEQUENCE · STARTINGPLACESANDRESOURCES · ORDEROFPLAY | p.7 | 0.04866 (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 Roads & Boats — Rulebook (corpus doc 680) | CONFLICT · CHOOSINGAPLAYINGSEQUENCE | p.17 | 0.048652 (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 Roads & Boats — Rulebook (corpus doc 680) | SETTING/.notdefUP | p.6 | 0.046875 (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 Roads & Boats — Rulebook (corpus doc 680) | SETTING/.notdefUP · FIRST-TIMEPREPARATIONS · SETTINGUP · CREATINGTHEWORLD | p.6 | 0.046239 (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 Roads & Boats — Rulebook (corpus doc 680) | SUMMARY · MATERIAL | p.5 | 0.046154 (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 Roads & Boats — Rulebook (corpus doc 680) | EXAMPLEOFACONFLICTROUND | p.18 | 0.04598 (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 Roads & Boats — Rulebook (corpus doc 680) | p.3 | 0.045009 (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 Roads & Boats — Rulebook (corpus doc 680) | CONFLICT | p.18 | 0.044337 (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 32 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 Roads & Boats — Rulebook (corpus doc 680) | SUMMARY · MATERIAL | p.5 | #5 | 0.046154 (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 Roads & Boats — Rulebook (corpus doc 680) | CONFLICT | p.18 | #8 | 0.044337 (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 Roads & Boats — Rulebook (corpus doc 680) | EXAMPLEOFACONFLICTROUND | p.18 | #6 | 0.04598 (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 |
| #4 | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | SETTING/.notdefUP | p.6 | #3 | 0.046875 (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 |
| #5 | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | GAMEMATERIAL | p.5 | #12 | 0.014493 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one)) | vector | the re-ranker chose it |
| #6 | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | p.3 | #7 | 0.045009 (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 | |
| #7 | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | CONFLICT · CHOOSINGAPLAYINGSEQUENCE | p.17 | #2 | 0.048652 (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 |
| #8 | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | SETTING/.notdefUP · DETERMININGTHESTARTINGSEQUENCE · STARTINGPLACESANDRESOURCES · ORDEROFPLAY | p.7 | #1 | 0.04866 (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
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 Roads & Boats — Rulebook (corpus doc 680) | SUMMARY · MATERIAL | p.5 | no quote on the wire |
| [2] | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | SETTING/.notdefUP · DETERMININGTHESTARTINGSEQUENCE · STARTINGPLACESANDRESOURCES · ORDEROFPLAY | p.7 | no quote on the wire |
| [3] | RULEBOOK Roads & Boats — Rulebook (corpus doc 680) | CONFLICT · CHOOSINGAPLAYINGSEQUENCE | p.17 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 156 ms · first delta 2507 ms · total 3812 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 156 ms · ask 3655 ms · gateway work 3812 ms · total 3812 ms
- tokens in (the prompt the answerer read)
- 3109
- tokens out (what the answerer generated)
- 252
- tok/sec
- 201.8 tok/sec — 252 output tokens in 1.249 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 36s ago)
- answerer host (measured by rulesage)
- reachable (for 22h, checked 6s 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
- 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 613), 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.