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 TWO-ARM fuse (full-text + vector), whose arithmetic ceiling is 0.03279 — both arms ranking the same chunk #1 (ceiling = arms/(k+1) at k=60). Measured healthy band on this fuse: 0.016–0.033. 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 7 Wonders: Leaders — Rulebook (corpus doc 218)	SETUP · GAMEPLAY · A. SELECTION PHASE	p.2	0.032787 (at the 2-arm ceiling (0.03279) — every arm ranked it #1)	300
#2	RULEBOOK 7 Wonders: Leaders — Rulebook (corpus doc 218)	B. RECRUITMENT PHASE · A. Recruit this Leader · B. Construct a stage of your Wonder · C. Sell this Leader · RECRUITMENT IN AGE III	p.3	0.016129 (inside the measured healthy band 0.016–0.033)	300
#3	RULEBOOK 7 Wonders: Leaders — Rulebook (corpus doc 218)	END OF THE GAME · CLARIFICATION ON GREEN CARDS · CREDITS	p.4	0.015873 (below the measured healthy band (< 0.016) — a weak fuse)	300
#4	RULEBOOK 7 Wonders: Leaders — Rulebook (corpus doc 218)	CONTENTS · OVERVIEW · WONDER BOARDS · LEADER CARDS · COINS · SCORE PAD · …	p.1	0.015625 (below the measured healthy band (< 0.016) — a weak fuse)	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 7 Wonders: Leaders — Rulebook (corpus doc 218)	SETUP · GAMEPLAY · A. SELECTION PHASE	p.2	no quote on the wire

generation — timing and the path taken

timing split

retrieval 198 ms · first delta 1727 ms · total 2680 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 198 ms · ask 2474 ms · gateway work 2680 ms · total 2680 ms

tokens in (the prompt the answerer read)

1569

tokens out (what the answerer generated)

132

tok/sec

146.0 tok/sec — 132 output tokens in 0.904 s of generation

live seat (read from the running child)

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