You asked
How do I play?
Abstained — no grounded answer; closest passages below counted as honest abstainAsked with: Skyminesbg-359438-en-1e
I looked through Skymines's rulebook and couldn't find a solid answer to that one — and I'd rather tell you so than guess at your table. Try asking it another way, or ask me about setup, turns, or how the game ends: those I know cold.
The closest rulebook passages are below — check them before ruling.
Play the game as usual, following the normal basic game rules and the mission cards rules. Carry the end of the game and the Final scoring phase out as usual. Then write down the success points for each player as described on page 24. In this chapter, one player can earn the following additional suc
The game is played according to the usual Belt side rules with one addition: The card in the game board's center poses a threat. This threat entails a specific consequence that affects all players at the end of the game. However, in order to negate that consequence for all players, the threat can be
a After setting the game up as usual, take the 6 mission cards and shuffle them face down. Depending on the number of human players (Luna doesn't count), place one or two mission cards face up next to the game board: · If there are 1 or 2 human players, place 1 mission card. If there are 3 or 4 huma
10 Each player: Choose a player color and take the corresponding player token. Then take the following items: Take a player board and place it in front of you with the standard side up. (Make sure that you leave room above and below your player board for cards.) Then place your player token onto the
The Planning phase is carried out by all players simultaneously and comprises 2 steps: Each player plans their Action phase by placing cards face down in their action area All players turn their placed cards face up Each player: Choose cards from your hand and place them face down in the available a
🔧 debug — where this ruling came from
- outcome
- ABSTAINED — Abstained — no grounded answer; closest passages below
- warm abstain
-
- this ruling — W1 — generic warm abstain · receipt: none (generic)
- corpus profile
- live,vps
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 91 ms · ask 2744 ms · total 2838 ms
- single-flight (PR-5)
- queued 0 ms · generation 2838 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 30, "score": 0.046402, "snippet": "Play the game as usual, following the normal basic game rules and the mission cards rules. Carry the end of the game and the Final scoring phase out as usual. Then write down the success points for each player as described on page 24. In this chapter, one player can earn the following additional suc", "headingPath": "Playing the game · End of the game · Chapter 4: Lurking in the Belt · Setup · Module: Threat cards", "sharpsignalDocId": 564}, {"page": 31, "score": 0.045831, "snippet": "The game is played according to the usual Belt side rules with one addition: The card in the game board's center poses a threat. This threat entails a specific consequence that affects all players at the end of the game. However, in order to negate that consequence for all players, the threat can be", "headingPath": "Playing the game · End of the game", "sharpsignalDocId": 564}, {"page": 25, "score": 0.045055, "snippet": "a After setting the game up as usual, take the 6 mission cards and shuffle them face down. Depending on the number of human players (Luna doesn't count), place one or two mission cards face up next to the game board: · If there are 1 or 2 human players, place 1 mission card. If there are 3 or 4 huma", "headingPath": "Setup · Playing the game", "sharpsignalDocId": 564}, {"page": 7, "score": 0.032787, "snippet": "10 Each player: Choose a player color and take the corresponding player token. Then take the following items: Take a player board and place it in front of you with the standard side up. (Make sure that you leave room above and below your player board for cards.) Then place your player token onto the", "headingPath": "", "sharpsignalDocId": 564}, {"page": 10, "score": 0.032258, "snippet": "The Planning phase is carried out by all players simultaneously and comprises 2 steps: Each player plans their Action phase by placing cards face down in their action area All players turn their placed cards face up Each player: Choose cards from your hand and place them face down in the available a", "headingPath": "1) Planning phase · a) Place cards face down in your action area · b) Flip cards face up · 2) Action phase", "sharpsignalDocId": 564}, {"page": 5, "score": 0.030478, "snippet": "Below you find the setup and rules for the basic game of Skymines , which is played on the Moon side of the board. We recommend playing the basic game once or twice first. Afterwards you could try the 4-chapter campaign (see page 24), which is an exciting challenge and introduces you to the addition", "headingPath": "Folding boxes", "sharpsignalDocId": 564}, {"page": 1, "score": 0.030303, "snippet": "A game by Alexander Pfister and Viktor Kobilke for 1 to 4 players, aged 12 and up", "headingPath": "", "sharpsignalDocId": 564}, {"page": 19, "score": 0.029851, "snippet": "After the Action phase of round 7, the game ends. Now, the Final scoring phase takes place as follows: Each player: First, pick up all cards of your resting decks and add them to your hand. Then find from your hand all cards that show an additional company share on their right side. Sort these by co", "headingPath": "End of the game", "sharpsignalDocId": 564}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- []
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 564 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 564 boosted
- answered-before recall
-
no past answered ruling for this game matched closely enough
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- debug row recorded
- Aug 27, 2026 20:49 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 Skymines — Rulebook (corpus doc 564) | Playing the game · End of the game · Chapter 4: Lurking in the Belt · Setup · Module: Threat cards | p.30 | 0.046402 (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 Skymines — Rulebook (corpus doc 564) | Playing the game · End of the game | p.31 | 0.045831 (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 Skymines — Rulebook (corpus doc 564) | Setup · Playing the game | p.25 | 0.045055 (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 Skymines — Rulebook (corpus doc 564) | p.7 | 0.032787 (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 Skymines — Rulebook (corpus doc 564) | 1) Planning phase · a) Place cards face down in your action area · b) Flip cards face up · 2) Action phase | p.10 | 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 |
| #6 | RULEBOOK Skymines — Rulebook (corpus doc 564) | Folding boxes | p.5 | 0.030478 (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 Skymines — Rulebook (corpus doc 564) | p.1 | 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)) | 81 | |
| #8 | RULEBOOK Skymines — Rulebook (corpus doc 564) | End of the game | p.19 | 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 57 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 Skymines — Rulebook (corpus doc 564) | p.7 | #4 | 0.032787 (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 | |
| #2 | RULEBOOK Skymines — Rulebook (corpus doc 564) | Playing the game · End of the game | p.31 | #2 | 0.045831 (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 Skymines — Rulebook (corpus doc 564) | Playing the game · End of the game · Chapter 4: Lurking in the Belt · Setup · Module: Threat cards | p.30 | #1 | 0.046402 (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 Skymines — Rulebook (corpus doc 564) | p.31 | #12 | 0.027826 (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 Skymines — Rulebook (corpus doc 564) | Setup | p.30 | #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 Skymines — Rulebook (corpus doc 564) | End of the game | p.19 | #8 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #7 | RULEBOOK Skymines — Rulebook (corpus doc 564) | Folding boxes | p.5 | #6 | 0.030478 (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 Skymines — Rulebook (corpus doc 564) | Setup · Playing the game | p.25 | #3 | 0.045055 (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 |
|---|
generation — timing and the path taken
- timing split
- retrieval 91 ms · first delta 2737 ms · total 2838 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 2744 ms · gateway work 2838 ms · total 2838 ms
- tokens in (the prompt the answerer read)
- 3307
- tokens out (what the answerer generated)
- 9
- tok/sec
- 180.0 tok/sec — 9 output tokens in 0.050 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 0s ago)
- answerer host (measured by rulesage)
- reachable (for 22h, checked 6s 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
- ABSTAINED — Abstained — no grounded answer; closest passages below
- abstain rationale
-
I don't have enough information.
BOILERPLATE, not reasoning: this is the answerer's fixed abstention phrase, the same sentence it emits whenever it declines. It records THAT the answerer declined and never why — no per-ruling reason was captured, because none was sent. Hostile corpus/LLM text, rendered escaped
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 496), 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.