You asked
How do I play?
Answered counted as answeredAsked with: Star Wars: X-Wing Miniatures Gamebg-103885-en-1e
🔧 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 91 ms · ask 4039 ms · total 4132 ms
- single-flight (PR-5)
- queued 0 ms · generation 4132 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 21, "score": 0.047875, "snippet": "Missions are a special way of playing the game which changes the victory conditions and offers some unique rules and objectives for the game session. After learning the basics of X-Wing , players can play missions to add variety and unique objectives to the game. Before following the standard steps ", "headingPath": "Missions · Component Limitations · playing a MiSSion · MiSSion play area Size", "sharpsignalDocId": 377}, {"page": 4, "score": 0.047073, "snippet": "X-Wing is not played on a board. Instead, it is played on any flat surface with at least 3' x 3' of space. Players may want to use a felt or cloth surface, which provides a little friction and helps to prevent players from accidentally bumping or moving the ships. For a game with three ships, the pl", "headingPath": "The Play Area", "sharpsignalDocId": 377}, {"page": 4, "score": 0.046696, "snippet": "4 Before playing, set up the game as follows: choose a Faction: Players agree on which factions to control. One player controls Rebels while the other controls Imperials. If players cannot agree, randomly assign factions. All components belonging to a player's own faction are considered friendly , a", "headingPath": "range ruler · Setup", "sharpsignalDocId": 377}, {"page": 20, "score": 0.045921, "snippet": "Although a game of X-Wing always consists of two sides, the Rebellion and the Empire, it is possible to play the game with more than two players. To play with more than two players, the players divide themselves as equally as possible into teams. One team plays the Rebellion while the other team pla", "headingPath": "Team Play Rules · Sharing inForMaTion", "sharpsignalDocId": 377}, {"page": 6, "score": 0.044758, "snippet": "6 During this phase, each player uses maneuver dials to secretly choose one maneuver for each of his ships. The selection on the dial dictates how his ships move during the next Activation phase. Players must assign a dial to each ship. After all ships have been assigned maneuver dials, continue to ", "headingPath": "The Game Round · planning phaSe · chooSing a maneuver · typeS of maneuverS · Bearing · Speed", "sharpsignalDocId": 377}, {"page": 5, "score": 0.043908, "snippet": "X-Wing is played over a series of game rounds. During each game round, players perform the following four phases in order: planning phase: Each player secretly chooses one maneuver for each of his ships by using its maneuver dial. activation phase: Each ship moves and performs one action. In ascendi", "headingPath": "The Game Round", "sharpsignalDocId": 377}, {"page": 28, "score": 0.029851, "snippet": "28 Quick Reference The gaMe rounD 1. planning phase: Each player secretly plans his ships’ maneuvers by assigning them facedown maneuver dials. 2. activation phase: Each ship moves and performs one action. In ascending order of pilot skill, reveal each ship’s maneuver dial, execute the chosen maneuv", "headingPath": "", "sharpsignalDocId": 377}, {"page": 10, "score": 0.029412, "snippet": "During this phase, each ship may perform one attack against one enemy ship that is inside its firing arc and within range. Starting with the ship with the highest pilot skill , players resolve the following combat steps in order: Declare Target: The attacker chooses which enemy ship he wishes to att", "headingPath": "coMBaT phaSe · 1. declare target", "sharpsignalDocId": 377}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 5, "quote": null, "headingPath": "The Game Round", "sharpsignalDocId": 377}, {"page": 6, "quote": null, "headingPath": "The Game Round · planning phaSe · chooSing a maneuver · typeS of maneuverS · Bearing · Speed", "sharpsignalDocId": 377}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 377 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 377 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.93875 of 898 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row retained until
- Nov 14, 2026 14:09
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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | Missions · Component Limitations · playing a MiSSion · MiSSion play area Size | p.21 | 0.047875 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Play Area | p.4 | 0.047073 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | range ruler · Setup | p.4 | 0.046696 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | Team Play Rules · Sharing inForMaTion | p.20 | 0.045921 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Game Round · planning phaSe · chooSing a maneuver · typeS of maneuverS · Bearing · Speed | p.6 | 0.044758 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Game Round | p.5 | 0.043908 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | p.28 | 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 | |
| #8 | RULEBOOK Star Wars: X-Wing Miniatures Game — Rulebook (corpus doc 377) | coMBaT phaSe · 1. declare target | p.10 | 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)) | 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 47 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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Play Area | p.4 | #2 | 0.047073 (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 Star Wars: X-Wing Miniatures Game — Rulebook (corpus doc 377) | range ruler · Setup | p.4 | #3 | 0.046696 (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 |
| #3 | RULEBOOK Star Wars: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Game Round | p.5 | #6 | 0.043908 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | Secondary weaponS · oBSTacleS · adding oBStacleS to a Standard game · moving into and through oBStacleS · attacking through oBStacleS | p.20 | #12 | 0.027242 (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 |
| #5 | RULEBOOK Star Wars: X-Wing Miniatures Game — Rulebook (corpus doc 377) | p.24 | #11 | 0.02753 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Game Round · planning phaSe · chooSing a maneuver · typeS of maneuverS · Bearing · Speed | p.6 | #5 | 0.044758 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | Missions · Component Limitations · playing a MiSSion · MiSSion play area Size | p.21 | #1 | 0.047875 (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 |
| #8 | RULEBOOK Star Wars: X-Wing Miniatures Game — Rulebook (corpus doc 377) | Team Play Rules · Sharing inForMaTion | p.20 | #4 | 0.045921 (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: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Game Round | p.5 | no quote on the wire |
| [2] | RULEBOOK Star Wars: X-Wing Miniatures Game — Rulebook (corpus doc 377) | The Game Round · planning phaSe · chooSing a maneuver · typeS of maneuverS · Bearing · Speed | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 91 ms · first delta 2926 ms · total 4132 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 91 ms · ask 4039 ms · gateway work 4132 ms · total 4132 ms
- tokens in (the prompt the answerer read)
- 3427
- tokens out (what the answerer generated)
- 237
- tok/sec
- 203.6 tok/sec — 237 output tokens in 1.164 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 25s 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 306), 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.