You asked
How do I play?
Answered counted as answeredAsked with: Star Wars: Destinybg-205359-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 108 ms · ask 9297 ms · total 19670 ms
- single-flight (PR-5)
- queued 10262 ms · generation 9408 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 10, "score": 0.048139, "snippet": "Each player has their own in-play and out-of-play areas. After an upgrade, downgrade, or support is played, it is added to the in-play area. Characters and plots start the game in play. The abilities on cards in play can be used. A card enters play when it transitions from an out-of-play area to the", "headingPath": "PART 3. AREAS OF PLAY · CHARACTERS, PLOTS, & PLAYED CARDS · DICE POOL · RESOURCES · BATTLEFIELD (IF CONTROLLED) · OUT-OF-PLAY · …", "sharpsignalDocId": 758}, {"page": 14, "score": 0.04612, "snippet": "Whenever a player wishes to play a card, that player follows these steps, in order: 1 Declare intent by showing the card and add it to the queue. 2 Check play restrictions. If the play restrictions cannot be met, the action is illegal. 3 If the card is an upgrade or downgrade, choose a target to att", "headingPath": "PLAY A CARD · ACTIVATE A CARD", "sharpsignalDocId": 758}, {"page": 22, "score": 0.044071, "snippet": "More than two players can participate in a free-for-all game, though 3-4 is recommended. Players should follow the normal rules of the game, with the following exceptions and additions: To set up the game, follow these steps in order: Randomly seat the players at the table. 2. All players roll off f", "headingPath": "FREE-FOR-ALL · SETUP · ACTIONS · CHOOSING OPPONENTS · PLAYER ELIMINATION · ALLIANCES", "sharpsignalDocId": 758}, {"page": 13, "score": 0.042005, "snippet": "The game is a fast-paced, back-and-forth battle where players alternate taking turns. To set up the game, follow these steps in order: 1 Each player places their character and plot cards faceup in front of them, along with those characters' matching dice. 2 Each player sets aside their battlefield f", "headingPath": "PART 5. GAME STRUCTURE · SETUP · ROUNDS · ACTION PHASE · UPKEEP PHASE", "sharpsignalDocId": 758}, {"page": 13, "score": 0.041517, "snippet": "Actions are taken by a player whenever it is their turn. On a player's turn, they must take an action or pass. Whenever a player wishes to take an action, that player first declares their intent (and shows the card to be used, if necessary). The different actions are listed below: Play a card Activa", "headingPath": "ACTIONS", "sharpsignalDocId": 758}, {"page": 22, "score": 0.040941, "snippet": "A player can play an upgrade on one of their teammate's characters, or use Redeploy to move an upgrade on one of their characters to a teammate's character. When resolving a focus side, a player can turn their teammate's dice. If a player controls 4 or more supports with a matching die, they must ch", "headingPath": "ADDITIONAL RULES AND CLARIFICATIONS", "sharpsignalDocId": 758}, {"page": 2, "score": 0.040775, "snippet": "CUSTOMIZATION ............................... 12 Building a team, building a deck, and selecting a battlefield. PART 5. GAME STRUCTURE ........................... 13 How to set up and play the game. PART 6. GAME CONCEPTS ............................. 16 Important rules that are used in every game. P", "headingPath": "", "sharpsignalDocId": 758}, {"page": 14, "score": 0.039197, "snippet": "Each side of a die may have a symbol on it (see page 9). A player may resolve one or more dice in their pool that are showing the same symbol, one at a time (unless adding a modified die, then the dice are resolved simultaneously). To resolve a die, a player must pay any costs and carry out the effe", "headingPath": "RESOLVE DICE · REROLL DICE · USE A CARD ACTION · CLAIM THE BATTLEFIELD", "sharpsignalDocId": 758}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 30, "quote": null, "headingPath": "FAQ", "sharpsignalDocId": 758}, {"page": 13, "quote": null, "headingPath": "ACTIONS", "sharpsignalDocId": 758}, {"page": 14, "quote": null, "headingPath": "PLAY A CARD · ACTIVATE A CARD", "sharpsignalDocId": 758}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 758 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 758 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.87919 of 1283 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row retained until
- Nov 23, 2026 16:12 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 Star Wars: Destiny — Rulebook (corpus doc 758) | PART 3. AREAS OF PLAY · CHARACTERS, PLOTS, & PLAYED CARDS · DICE POOL · RESOURCES · BATTLEFIELD (IF CONTROLLED) · OUT-OF-PLAY · … | p.10 | 0.048139 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | PLAY A CARD · ACTIVATE A CARD | p.14 | 0.04612 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | FREE-FOR-ALL · SETUP · ACTIONS · CHOOSING OPPONENTS · PLAYER ELIMINATION · ALLIANCES | p.22 | 0.044071 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | PART 5. GAME STRUCTURE · SETUP · ROUNDS · ACTION PHASE · UPKEEP PHASE | p.13 | 0.042005 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | ACTIONS | p.13 | 0.041517 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | ADDITIONAL RULES AND CLARIFICATIONS | p.22 | 0.040941 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | p.2 | 0.040775 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | RESOLVE DICE · REROLL DICE · USE A CARD ACTION · CLAIM THE BATTLEFIELD | p.14 | 0.039197 (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 76 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 Star Wars: Destiny — Rulebook (corpus doc 758) | FAQ | p.30 | #13 | 0.026374 (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 |
| #2 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | FAQ | p.30 | #10 | 0.027271 (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 |
| #3 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | PART 3. AREAS OF PLAY · CHARACTERS, PLOTS, & PLAYED CARDS · DICE POOL · RESOURCES · BATTLEFIELD (IF CONTROLLED) · OUT-OF-PLAY · … | p.10 | #1 | 0.048139 (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 |
| #4 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | ADDITIONAL RULES AND CLARIFICATIONS | p.22 | #6 | 0.040941 (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 |
| #5 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | FAQ | p.32 | #16 | 0.025744 (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 |
| #6 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | ACTIONS | p.13 | #5 | 0.041517 (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 |
| #7 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | FAQ | p.32 | #24 | 0.023632 (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 |
| #8 | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | PLAY A CARD · ACTIVATE A CARD | p.14 | #2 | 0.04612 (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 Star Wars: Destiny — Rulebook (corpus doc 758) | FAQ | p.30 | no quote on the wire |
| [2] | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | ACTIONS | p.13 | no quote on the wire |
| [3] | RULEBOOK Star Wars: Destiny — Rulebook (corpus doc 758) | PLAY A CARD · ACTIVATE A CARD | p.14 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 108 ms · first delta 6187 ms · total 19670 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 10262 ms · retrieval 108 ms · ask 9297 ms · gateway work 9408 ms · total 19670 ms
- tokens in (the prompt the answerer read)
- 3237
- tokens out (what the answerer generated)
- 421
- tok/sec
- 133.0 tok/sec — 421 output tokens in 3.165 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 47s 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 60h, checked 3s 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 692), 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.