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. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.

score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP	p.12	0.031778 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#2	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP	p.12	0.031754 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#3	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	ADDING TRAVELLERS	p.26	0.030303 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#4	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP	p.12	0.030118 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#5	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	PREPARING THE NIGHT	p.14	0.029762 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#6	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	ADDING TRAVELLERS	p.26	0.029206 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#7	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	ABILITIES	p.22	0.028298 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	300
#8	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	RUNNING THINGS SMOOTHLY	p.31	0.028006 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded))	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.

the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.

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 Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP	p.12	no quote on the wire
[2]	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP	p.12	no quote on the wire
[3]	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	ADDING TRAVELLERS	p.26	no quote on the wire
[4]	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP · 8. ADD REMINDER TOKENS TO THE GRIMOIRE.	p.13	no quote on the wire

generation — timing and the path taken

timing split

retrieval 892 ms · first delta 20683 ms · total 25500 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 892 ms · ask 23638 ms · gateway work 25500 ms · total 25500 ms

tokens in (the prompt the answerer read)

4137

tokens out (what the answerer generated)

688

tok/sec

146.9 tok/sec — 688 output tokens in 4.685 s of generation

live seat (read from the running child)

answering — gemma4:26b think:false · num_ctx 32768 (live-verified 41s 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 81), 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.