You asked
How do I take my turn?
Answered counted as answeredAsked with: Xia: Legends of a Drift Systembg-82222-en-1e
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 234 ms · ask 13913 ms · total 14157 ms
- single-flight (PR-5)
- queued 0 ms · generation 14157 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 16, "score": 0.048652, "snippet": "NPC Turns At the beginning of the game, the NPC Cards are shuffled and dealt to the first three players. A player takes a turn for the NPC he controls directly after his turn. NPC turns do not have phases like player turns. To take an NPC turn, the player simply reads the NPC card from top to bottom", "headingPath": "Mine / Salvage / Harvest", "sharpsignalDocId": 332}, {"page": 10, "score": 0.047938, "snippet": "During their Action Phase, players take Actions. To take an Action, the player: · Declares the Action they are taking; Spends any required Energy or Armed Markers and associated dice; and Resolves the Action. (ex. Player 1 first declares he will take a Move Action using his Engine Outfit. He spends ", "headingPath": "Player Turn Detail", "sharpsignalDocId": 332}, {"page": 9, "score": 0.047123, "snippet": "Player 2 turn - Player 1 is attacked and dies in Tier 2 ^ or 3 & ship. Player 3 turn Player 1 turn - This turn is skipped. Player 2 turn Player 3 turn Player 1 turn - Respawn, then take turn as normal. (Note: If Player 1 had died on her own turn, she still would have skipped the denoted turn.) Move ", "headingPath": "Example Tier 2 ^ or 3 & :", "sharpsignalDocId": 332}, {"page": 9, "score": 0.046898, "snippet": "After death, at the start of their next non-skipped turn, the player (or NPC) must first Respawn. Respawn: To Respawn, roll the Ï [d20] and place the ship on the unoccupied Spawn Point with the number closest to the number rolled. In the case of a tie, place the ship on the higher-numbered Spawn Poi", "headingPath": "Respawn · Example Tier 1 $ :", "sharpsignalDocId": 332}, {"page": 3, "score": 0.045079, "snippet": "The Action Phase includes fighting, flying, using abilities, collecting, trading, and working on/completing Missions. The player will use the inherent abilities of his ship, Outfits he has equipped on his ship, and his bonus abilities from Ability Cards to take Actions. A player may continue taking ", "headingPath": "1. Action Phase · 3. Status Phase", "sharpsignalDocId": 332}, {"page": 13, "score": 0.04374, "snippet": "Titles are a mark of Fame for pilots who complete certain exploits. Once a Title is drawn, all players compete to complete its objective and claim the Title for their own. Titles are unique and range in difficulty and reward. Titles are worth 1 @ to 3 @ Fame Points and grant small abilities called S", "headingPath": "Titles", "sharpsignalDocId": 332}, {"page": 10, "score": 0.04311, "snippet": "Ability Cards: Some Abilities are designated as Actions. Rescue a Stranded Player: A player may rescue an adjacent player who has no Energy/Armed Markers by giving her 2 Energy. Jettison Cargo (Minor): A player may discard her current Mission Card or Jettison any Cargo Cubes in her Hold. To do the l", "headingPath": "Other", "sharpsignalDocId": 332}, {"page": 10, "score": 0.030303, "snippet": "Claim Fame: The player claims any unclaimed Titles and Fame Points acquired during their turn. If the player reaches the Victory Marker, the game ends and the player claims victory! Draw Titles: Title Cards are drawn the first time any player's Marker reaches a purple Title space on the Fame Point T", "headingPath": "Status Phase", "sharpsignalDocId": 332}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 9, "quote": null, "headingPath": "Respawn · Example Tier 1 $ :", "sharpsignalDocId": 332}, {"page": 10, "quote": null, "headingPath": "Player Turn Detail", "sharpsignalDocId": 332}, {"page": 10, "quote": null, "headingPath": "Other", "sharpsignalDocId": 332}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 332 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 332 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)
- debug row retained until
- Nov 6, 2026 18:12
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. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.
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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Mine / Salvage / Harvest | p.16 | 0.048652 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Player Turn Detail | p.10 | 0.047938 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Example Tier 2 ^ or 3 & : | p.9 | 0.047123 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Respawn · Example Tier 1 $ : | p.9 | 0.046898 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | 1. Action Phase · 3. Status Phase | p.3 | 0.045079 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Titles | p.13 | 0.04374 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Other | p.10 | 0.04311 (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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Status Phase | p.10 | 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 |
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.
the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.
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 Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Respawn · Example Tier 1 $ : | p.9 | no quote on the wire |
| [2] | RULEBOOK Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Player Turn Detail | p.10 | no quote on the wire |
| [3] | RULEBOOK Xia: Legends of a Drift System — Rulebook (corpus doc 332) | Other | p.10 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 234 ms · first delta 12909 ms · total 14157 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 234 ms · ask 13913 ms · gateway work 14157 ms · total 14157 ms
- tokens in (the prompt the answerer read)
- 3886
- tokens out (what the answerer generated)
- 160
- tok/sec
- 135.7 tok/sec — 160 output tokens in 1.179 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 55s 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
- 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 260), 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.