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 Battleship — Rulebook (corpus doc 147)	CONTENTS · OBJECT · THE FIRST TIME YOU PLAY · PREPARE FOR BATTLE! · CONTENU · TA FLOTTE DE 5 VAISSEAUX · …	p.1	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))	300
#2	RULEBOOK Battleship — Rulebook (corpus doc 147)	IT'S A HIT! · POSITIONNEMENT DES VAISSEAUX · POUR JOUER · PASSE À L'ATTAQUE !	p.1	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
#3	RULEBOOK Battleship — Rulebook (corpus doc 147)	THE SALVO GAME · C'EST RATÉ ! · COULER UN VAISSEAU	p.1	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
#4	RULEBOOK Battleship — Rulebook (corpus doc 147)	TOUCHÉ ! · IT'S A MISS! · SINKING A SHIP · WINNING THE GAME	p.1	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
#5	RULEBOOK Battleship — Rulebook (corpus doc 147)	ATAQUE MÚLTIPLE · ÁGUA!	p.2	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 Battleship — Rulebook (corpus doc 147)	GAGNER LA PARTIE · MODE SALVE	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
#7	RULEBOOK Battleship — Rulebook (corpus doc 147)	¡ FALLASTE! · HUNDIR UNA NAVE · CÓMO GANAR EL JUEGO	p.2	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
#8	RULEBOOK Battleship — Rulebook (corpus doc 147)	COMO AFUNDAR UM NAVIO · VENCENDO O JOGO · JOGO DA SALVA DE TIROS	p.2	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 Battleship — Rulebook (corpus doc 147)	CONTENTS · OBJECT · THE FIRST TIME YOU PLAY · PREPARE FOR BATTLE! · CONTENU · TA FLOTTE DE 5 VAISSEAUX · …	p.1	no quote on the wire
[2]	RULEBOOK Battleship — Rulebook (corpus doc 147)	INCLUYE · OBJETIVO DEL JUEGO · LA PRIMERA VEZ QUE JUEGUES · ¡ PREPÁRATE PARA LA BATALLA! · OBJETIVO · AO JOGAR PELA PRIMEIRA VEZ · …	p.2	no quote on the wire
[3]	RULEBOOK Battleship — Rulebook (corpus doc 147)	REGLAS PARA UBICAR LAS NAVES · CÓMO JUGAR · ¡ ANUNCIA TU ATAQUE! · ¡ ACERTASTE! · REGRAS PARA O POSICIONAMENTO DOS NAVIO	p.2	no quote on the wire

generation — timing and the path taken

timing split

retrieval 263 ms · first delta 3584 ms · total 2146027 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)

full breakdown

queued 2141153 ms · retrieval 263 ms · ask 4601 ms · gateway work 4874 ms · total 2146027 ms

tokens in (the prompt the answerer read)

3558

tokens out (what the answerer generated)

179

tok/sec

146.5 tok/sec — 179 output tokens in 1.222 s of generation

live seat (read from the running child)

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