retrieval — what the search arm returned

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 So Clover! — Rulebook (corpus doc 122)	François Romain · SETUP · CONTENTS	p.1	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 So Clover! — Rulebook (corpus doc 122)	END OF THE GAME · ADD A CHALLENGE · CREDITS	p.6	0.016393 (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 So Clover! — Rulebook (corpus doc 122)	Examples · 2. RESOLUTION	p.4	0.016129 (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 So Clover! — Rulebook (corpus doc 122)	Perfect · Second attempt	p.5	0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#5	RULEBOOK So Clover! — Rulebook (corpus doc 122)	GAMEPLAY · 1. CHOOSING CLUES	p.2	0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	300
#6	RULEBOOK So Clover! — Rulebook (corpus doc 122)	Invalid Clues · Examples	p.3	0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded)	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 So Clover! — Rulebook (corpus doc 122)	François Romain · SETUP · CONTENTS	p.1	no quote on the wire

generation — timing and the path taken

timing split

retrieval 214 ms · first delta 1697 ms · total 2233 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 214 ms · ask 2007 ms · gateway work 2233 ms · total 2233 ms

tokens in (the prompt the answerer read)

1537

tokens out (what the answerer generated)

69

tok/sec

137.7 tok/sec — 69 output tokens in 0.501 s of generation

live seat (read from the running child)

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