You asked
How do I setup the game?
Answered counted as answeredAsked with: Bloodborne: The Board Gamebg-273330-en-1e
🔧 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 74 ms · ask 8280 ms · total 8356 ms
- single-flight (PR-5)
- queued 0 ms · generation 8356 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 9, "score": 0.048172, "snippet": "Place the Hunt board in view of all players. 1 Take only the Chapter card corresponding to the Chapter you are playing and place it on the Chapter card slot on the Hunt board. Place the Mission deck facedown next to it. Then, place the Introduction card faceup within reach of all players. NOTE: The ", "headingPath": "3. HUNT BOARD SETUP", "sharpsignalDocId": 694}, {"page": 7, "score": 0.047643, "snippet": "There are 4 Campaigns to choose from in Bloodborne: The Board Game . Each Campaign features its own unique story, revealed over the course of its 3 Chapters. Each Chapter has its own unique missions, enemies, and surprises to uncover. Before setting up the game, players must select the Campaign they", "headingPath": "CAMPAIGNS · 1. CAMPAIGN SETUP", "sharpsignalDocId": 694}, {"page": 10, "score": 0.047371, "snippet": "Hunters begin every Chapter on the Central Lamp tile . Set out this tile and place it in the middle of your play area, within reach of all players. Place all the Hunter miniatures on it, in any space, chosen by their player. Take the Chapter card specific to the Chapter you are playing and read its ", "headingPath": "4. CHAPTER SETUP", "sharpsignalDocId": 694}, {"page": 3, "score": 0.046642, "snippet": "...............................8 Setting up the Hunter Dashboard ......................8 3. Hunt Board Setup .............................................9 4. Chapter Setup ................................................. 10 ADVANCING THROUGH THE HUNT ........... 12 WINNING AND LOSING THE HUNT ....", "headingPath": "", "sharpsignalDocId": 694}, {"page": 8, "score": 0.032258, "snippet": "Each player chooses a Hunter and takes that Hunter's Trick Weapon dashboard , Firearm card , and miniature . Each player also takes 1 Hunter dashboard and its colormatching counter base , which should be attached to the Hunter's miniature. Finally, each player takes 6 HP (Health Points) and 1 Player", "headingPath": "2. HUNTER SETUP ChOOSing a huntEr · SEtting up thE huntEr DECk · SEtting up thE huntEr DaShBOarD", "sharpsignalDocId": 694}, {"page": 12, "score": 0.030303, "snippet": "Start every Campaign by reading the Introduction card . This card gives the players a brief summary of the threat facing the city and a starting point for their investigation. It is up to the players to uncover the source of the threat and how to solve it. Each Campaign is composed of 3 separate Cha", "headingPath": "BEGINNING THE HUNT · HUNT MISSIONS AND INSIGHT MISSIONS · READING A MISSION CARD", "sharpsignalDocId": 694}, {"page": 25, "score": 0.030214, "snippet": "Fog Gates are only removed when the Mission card that created them is completed, or when specifically instructed to do so. When a Fog Gate is removed, also remove any Broken Lamp tokens caused by it. Enemies may now spawn on that tile as usual on the next . EXAMPLE : This Insight Mission card instru", "headingPath": "FOG GATES · PROGRESSING THE CAMPAIGN · SAVING PROGRESS", "sharpsignalDocId": 694}, {"page": 18, "score": 0.029851, "snippet": "Once the last Hunter Turn and Enemy Activation have been completed, the round ends and a new one beings. Take the following steps, in order: Advance the Hunt Track by 1 : Move the token 1 space on the Hunt Track. If, after this move, the token has reached the final space of the Hunt Track, the Fin", "headingPath": "STARTING A NEW ROUND · COMBAT", "sharpsignalDocId": 694}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 7, "quote": null, "headingPath": "CAMPAIGNS · 1. CAMPAIGN SETUP", "sharpsignalDocId": 694}, {"page": 8, "quote": null, "headingPath": "2. HUNTER SETUP ChOOSing a huntEr · SEtting up thE huntEr DECk · SEtting up thE huntEr DaShBOarD", "sharpsignalDocId": 694}, {"page": 9, "quote": null, "headingPath": "3. HUNT BOARD SETUP", "sharpsignalDocId": 694}, {"page": 10, "quote": null, "headingPath": "4. CHAPTER SETUP", "sharpsignalDocId": 694}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 694 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 694 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.90556 of 2033 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row retained until
- Nov 12, 2026 23:13
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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | 3. HUNT BOARD SETUP | p.9 | 0.048172 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | CAMPAIGNS · 1. CAMPAIGN SETUP | p.7 | 0.047643 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | 4. CHAPTER SETUP | p.10 | 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 |
| #4 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | p.3 | 0.046642 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | 2. HUNTER SETUP ChOOSing a huntEr · SEtting up thE huntEr DECk · SEtting up thE huntEr DaShBOarD | 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 |
| #6 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | BEGINNING THE HUNT · HUNT MISSIONS AND INSIGHT MISSIONS · READING A MISSION CARD | p.12 | 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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | FOG GATES · PROGRESSING THE CAMPAIGN · SAVING PROGRESS | p.25 | 0.030214 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | STARTING A NEW ROUND · COMBAT | p.18 | 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 |
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 44 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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | 4. CHAPTER SETUP | p.10 | #3 | 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)) | vector + full-text + the doc-priority boost arm | the re-ranker chose it |
| #2 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | CAMPAIGNS · 1. CAMPAIGN SETUP | p.7 | #2 | 0.047643 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | 4. CHAPTER SETUP | p.11 | #9 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #4 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | FOG GATES · PROGRESSING THE CAMPAIGN · SAVING PROGRESS | p.25 | #7 | 0.030214 (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 re-ranker chose it |
| #5 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | 2. HUNTER SETUP ChOOSing a huntEr · SEtting up thE huntEr DECk · SEtting up thE huntEr DaShBOarD | p.8 | #5 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #6 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | p.3 | #15 | 0.013333 (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 | |
| #7 | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | p.3 | #4 | 0.046642 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | 3. HUNT BOARD SETUP | p.9 | #1 | 0.048172 (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 Bloodborne: The Board Game — Rulebook (corpus doc 694) | CAMPAIGNS · 1. CAMPAIGN SETUP | p.7 | no quote on the wire |
| [2] | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | 2. HUNTER SETUP ChOOSing a huntEr · SEtting up thE huntEr DECk · SEtting up thE huntEr DaShBOarD | p.8 | no quote on the wire |
| [3] | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | 3. HUNT BOARD SETUP | p.9 | no quote on the wire |
| [4] | RULEBOOK Bloodborne: The Board Game — Rulebook (corpus doc 694) | 4. CHAPTER SETUP | p.10 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 74 ms · first delta 3956 ms · total 8356 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 74 ms · ask 8280 ms · gateway work 8356 ms · total 8356 ms
- tokens in (the prompt the answerer read)
- 2531
- tokens out (what the answerer generated)
- 616
- tok/sec
- 141.1 tok/sec — 616 output tokens in 4.365 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)
-
setup
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 627), 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.