You asked
How do I take my turn?
Answered counted as answeredAsked with: Dragon Eclipsebg-381247-en-1e
That's the page. Back to the table.
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live,vps
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 245 ms · ask 2048 ms · total 2296 ms
- single-flight (PR-5)
- queued 0 ms · generation 2296 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 22, "score": 0.047712, "snippet": "During its turn, an Enemy resolves one of their effects. Every few turns, the Enemy resolves its Special Ability. To resolve an Enemy turn, follow the steps below. Slide cards. Draw an Enemy Attack card. Resolve the Enemy Attack card Check and resolve the Special Ability. Enemy turn ends. Resolve th", "headingPath": "Enemy Turn Order · Enemy Keywords", "sharpsignalDocId": 1288}, {"page": 18, "score": 0.047379, "snippet": "Combat in Dragon Eclipse is played in turns. Turns are taken alternately, starting with the player. Combat ends with you losing, winning, or Taming the Enemy. It's worth noting that not all Enemies can be Tamed; the Adventure Journal provides information about whether the Enemy is valid for Taming o", "headingPath": "Combat rules · Actions · Golden Rules of Combat", "sharpsignalDocId": 1288}, {"page": 22, "score": 0.032258, "snippet": "After the player's turn, it's time for the Enemy to act. : Remember that the turn order is different. First, it is the turn of the player with the Taunt token, then the other player, and finally the Enemy. After the Enemy turn, the player with the Taunt token has their turn, and so on. Enemies have ", "headingPath": "Enemy Turn", "sharpsignalDocId": 1288}, {"page": 8, "score": 0.031746, "snippet": "The townsfolk have always deemed her a little nutty, mostly due to her habit of talking to herself, but no one would say that to her face as Christine does a lot for the community, from powering the smelter together with the Emberling to keeping wild beasts at bay. - - Place Continue the Exploration", "headingPath": "Try to repair the machine -Turn off the machine -Choose one:", "sharpsignalDocId": 1288}, {"page": 8, "score": 0.030769, "snippet": "When players encounter a situation during the game when they cannot agree on something, the player with the Decision token makes the decision and then passes the token to the other player. Try to use the Decision token sparingly. For example, players may want to use the Decision token when you must ", "headingPath": "Try to repair the machine -Turn off the machine -Choose one:", "sharpsignalDocId": 1288}, {"page": 22, "score": 0.030303, "snippet": "22 Enemy Turn After the/uni00A0player’s turn, it’s time for/uni00A0the/uni00A0Enemy to/uni00A0act. : Remember that/uni00A0 the/uni00A0 turn order is different. First, it is the/uni00A0 turn of/uni00A0 the/uni00A0 player with the/uni00A0 Taunt token, then the/uni00A0 other player, and /f_inally the/u", "headingPath": "", "sharpsignalDocId": 1288}, {"page": 19, "score": 0.029958, "snippet": ": Taunt change – whenever a/uni00A0 player deal to/uni00A0 an/uni00A0 Enemy during their turn, and they don’t have the/uni00A0 Taunt token, they take it from the/uni00A0other player. Dealing Conditions or interacting with the Enemy in other ways does not give you the Taunt token. The/uni00A0Enemy wi", "headingPath": "", "sharpsignalDocId": 1288}, {"page": 5, "score": 0.029851, "snippet": "The steps below prepare you for the adventure that awaits you. Before the Scenario, you visit familiar places, befriend wild Mystlings, gather information, choose your next destination, and prepare your Mystlings by constructing Action decks for them. Take out the following components and place them", "headingPath": "BEFORE THE SCENARIO · 1. Components Setup · 2. Taking Inventory · The Unexplored side · 3. Navigating the World Map · Navigation · …", "sharpsignalDocId": 1288}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 18, "quote": null, "headingPath": "Combat rules · Actions · Golden Rules of Combat", "sharpsignalDocId": 1288}, {"page": 19, "quote": null, "headingPath": "", "sharpsignalDocId": 1288}, {"page": 19, "quote": null, "headingPath": "", "sharpsignalDocId": 1288}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 1288 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1288 boosted
- answered-before recall
-
this ruling was answered, so past rulings were not offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- answer fence
- passed — letter density 0.86076 of 395 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row recorded
- Oct 24, 2026 20:07 UTC
retrieval — what the passage search returned
what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.
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 Dragon Eclipse — Rulebook (corpus doc 1288) | Enemy Turn Order · Enemy Keywords | p.22 | 0.047712 (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 Dragon Eclipse — Rulebook (corpus doc 1288) | Combat rules · Actions · Golden Rules of Combat | p.18 | 0.047379 (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 Dragon Eclipse — Rulebook (corpus doc 1288) | Enemy Turn | p.22 | 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 |
| #4 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Try to repair the machine -Turn off the machine -Choose one: | p.8 | 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 |
| #5 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Try to repair the machine -Turn off the machine -Choose one: | p.8 | 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 Dragon Eclipse — Rulebook (corpus doc 1288) | p.22 | 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 Dragon Eclipse — Rulebook (corpus doc 1288) | p.19 | 0.029958 (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 Dragon Eclipse — Rulebook (corpus doc 1288) | BEFORE THE SCENARIO · 1. Components Setup · 2. Taking Inventory · The Unexplored side · 3. Navigating the World Map · Navigation · … | p.5 | 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 |
what the answerer read — the passages it actually had in front of it
what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.
candidate pool: the answering read scored 80 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.
floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.
arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.
| read at | document | heading | page | fused rank | fused RRF score | carried by | how it got its slot |
|---|---|---|---|---|---|---|---|
| #1 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Enemy Turn Order · Enemy Keywords | p.22 | #1 | 0.047712 (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)) | vector + full-text + the doc-priority boost arm | the re-ranker chose it |
| #2 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Enemy Turn | p.22 | #3 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #3 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Quick battle setup · Challenge | p.27 | #15 | 0.02451 (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)) | vector + full-text | the re-ranker chose it |
| #4 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Example of a Player Turn | p.21 | #30 | 0.011905 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one)) | vector | the re-ranker chose it |
| #5 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | p.19 | #9 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it | |
| #6 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | p.19 | #10 | 0.02904 (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)) | vector + full-text | the re-ranker chose it | |
| #7 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | p.3 | #31 | 0.011765 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one)) | vector | the re-ranker chose it | |
| #8 | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | Combat rules · Actions · Golden Rules of Combat | p.18 | #2 | 0.047379 (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)) | vector + full-text + the doc-priority boost arm | the re-ranker chose it |
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 Dragon Eclipse — Rulebook (corpus doc 1288) | Combat rules · Actions · Golden Rules of Combat | p.18 | no quote on the wire |
| [2] | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | p.19 | no quote on the wire | |
| [3] | RULEBOOK Dragon Eclipse — Rulebook (corpus doc 1288) | p.19 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 245 ms · first delta 1446 ms · total 2296 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 245 ms · ask 2048 ms · gateway work 2296 ms · total 2296 ms
- tokens in (the prompt the answerer read)
- 4599
- tokens out (what the answerer generated)
- 152
- tok/sec
- 198.4 tok/sec — 152 output tokens in 0.766 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 55s ago)
- gateway schema (read from the running child)
- schema head 0042_definer_search_path (live revision not readable by this principal)
- answerer host (measured by rulesage)
- reachable (for 5h, checked 8s ago)
- answerer node (the seat proxy's own header — this probe, not this ask)
- node1
- 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
- NOT_SETUP_SHAPED — no setup-shape pattern matched this question
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 1218), 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.