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. 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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	spectator tiles · Bet on the overall winner or the overall loser · end of a leg	p.4	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5	p.5	0.047883 (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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:	p.3	0.047123 (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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money	p.2	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
#5	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	end of the game · Example:	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))	300
#6	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME	p.2	0.030415 (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 Camel Up (Second Edition) — Rulebook (corpus doc 181)		p.1	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
#8	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	spectator tiles	p.3	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.

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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME	p.2	no quote on the wire
[2]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money	p.2	no quote on the wire
[3]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	spectator tiles · Bet on the overall winner or the overall loser · end of a leg	p.4	no quote on the wire
[4]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:	p.3	no quote on the wire
[5]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5	p.5	no quote on the wire

generation — timing and the path taken

timing split

retrieval 374 ms · first delta 4092 ms · total 6136 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 374 ms · ask 5752 ms · gateway work 6136 ms · total 6136 ms

tokens in (the prompt the answerer read)

4549

tokens out (what the answerer generated)

270

tok/sec

136.2 tok/sec — 270 output tokens in 1.983 s of generation

live seat (read from the running child)

answering — gemma4:26b think:false · num_ctx 32768 (live-verified 25s 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

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 99), 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.