RuleSage cited table rulings
← Wyrmspan

You asked

how do dragons hatch

Refused — this game's rulebook isn't loaded yet counted as app error

This game's rulebook isn't loaded yet.

The corpus group bg-410201-en-1e exists but has no searchable documents yet — the rulebook is still being ingested. This is not a gap in the rules; there is simply nothing to search yet.

🔧 debug — where this ruling came from
outcome
REFUSED_EMPTY_GROUP — Refused — this game's rulebook isn't loaded yet
corpus profile
fixture
answerer pin (deploy-frozen, attribution only)
unset-dev (corpus lane freezes the deploy value)
timings
search 0 ms · ask null ms · total 0 ms
single-flight (PR-5)
queued n/a ms · generation 0 ms
retrieval refs (raw)
[]
citations (raw)
boost provenance — errata + base rulebook (E2/E3)
gate not evaluated for this ruling (boost, supersedence, and wrench all off at ask time), and the base-rulebook arm went unrecorded for the same reason — the wrench that would have stored it was off; rulesage.errata.boost-enabled=false, rulesage.errata.supersedence-enabled=false
answered-before recall
no past answered ruling for this game matched closely enough
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
debug row retained until
Oct 6, 2026 23:33

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 rankdocumentheadingpage fused RRF scoresnippet chars

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.

no payload was recorded for this ruling (the call never returned one)

timing split
retrieval 0 ms · first delta n/a · total 0 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued n/a ms · retrieval 0 ms · ask n/a ms · gateway work 0 ms · total 0 ms
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 51s ago)
stream path
not recorded — this ruling predates the stream-path column (V41)
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.
outcome
REFUSED_EMPTY_GROUP — Refused — this game's rulebook isn't loaded yet
abstain rationale
the answerer offered no rationale text with this refusal (or the ruling predates the abstain_rationale column, V41)
decision
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

this game registers NO errata cards (edition 4), 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.