RuleSage cited table rulings
← Hearts

You asked

How do I take my turn?

Error counted as app error

Asked with: Heartsbg-6887-en-1e

Answered before

This question didn't get an answer just now — but Hearts has been asked something like it before. The corpus may have changed since, so check the date and the answerer on each one before you rule from it.

How do I take my turn?

Answered Aug 4, 2026 gemma4:26b read Hearts

Something went wrong while producing this ruling — no answer is shown because none can be trusted. The wrench below has the failure detail.

🔧 debug — where this ruling came from
outcome
ERROR — Error
corpus profile
live
answerer pin (deploy-frozen, attribution only)
gemma4:26b think:false 5571076f3d70
timings
search null ms · ask null ms · total 7 ms
single-flight (PR-5)
queued 0 ms · generation 7 ms
retrieval refs (raw)
citations (raw)
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 222 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 222 boosted
answered-before recall
past answered rulings were found and offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
  • ruling 1019 — matched by the same question (normalized, punctuation folded) — measured similarity 1.0
error detail
CorpusRefused: search_documents refused: Error executing tool search_documents: requested group scope is not permitted for this MCP principal — refusing (D-1 narrows, it never widens)
debug row retained until
Nov 2, 2026 20:16

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.

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

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 n/a · first delta n/a · total 7 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 n/a ms · ask n/a ms · gateway work 7 ms · total 7 ms
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 36s ago)
stream path
wanted, but the ask never ran — retrieval failed or the group was empty, so the gateway was never asked to generate
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
ERROR — Error
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 148), 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.