You asked
How do I setup the game?
Abstained — no grounded answer; closest passages below counted as honest abstainAsked with: Andromeda's Edgebg-358661-en-1e
Answered before
This question didn't get an answer just now — but Andromeda's Edge has been asked something like it before. The corpus may have changed since, so check the date and the answerer on each one before you rule from it.
The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.
Players form teams of 2. Each player sits next to their teammate. Each player chooses and controls their own faction, as in a normal 4-player game. To choose a start player, each player rolls their 6 dice as normal, but each team combines their rolls and compares their new team roll with the roll of
7Player SetupPlayer Setup RESOURCES ENERGY Use:Use: station modules, weapons, jumps TITANIUM Use:Use: factories, industry modules, building ships NANOCARBON Use:Use: observatories, science modules ICE Use:Use: cities, civilization modules CREDITS Use:Use: wild for titanium, ice, nanocarbon Over the
Player Materials: Each player takes the following materials in their chosen color: 1 station mat 1 player aid 6 transports 1 fighter 1 science vessel 1 heavy cruiser 9 leaders 6 dice 5 track markers 1 VP marker Station mats are double-sided for flexibility. Note the orientation of the four colorful
Special regions add unique effects and scoring bonuses to the game. You may choose either the 2 Quasar tiles or the 2 Vortex tiles to include in your game. Before you place any other starting tiles on the board, place the selected special region tiles on the board in the spaces marked with and . The
Each player places 1 leader on each Alliance Base on the board. Each player rolls a die and places 2 leaders on the nebula matching the die rolled (more than 1 player can have leaders in the same nebula). Each player places their remaining 1 leader in the leaders area of their station. Choose a star
🔧 debug — where this ruling came from
- outcome
- ABSTAINED — Abstained — no grounded answer; closest passages below
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 273 ms · ask 9734 ms · total 10016 ms
- single-flight (PR-5)
- queued 0 ms · generation 10016 ms
- retrieval refs (raw)
- [{"page": 27, "score": 0.04866, "snippet": "Players form teams of 2. Each player sits next to their teammate. Each player chooses and controls their own faction, as in a normal 4-player game. To choose a start player, each player rolls their 6 dice as normal, but each team combines their rolls and compares their new team roll with the roll of", "headingPath": "Setup · Battle · CREDITS", "sharpsignalDocId": 320}, {"page": 7, "score": 0.047883, "snippet": "7Player SetupPlayer Setup RESOURCES ENERGY Use:Use: station modules, weapons, jumps TITANIUM Use:Use: factories, industry modules, building ships NANOCARBON Use:Use: observatories, science modules ICE Use:Use: cities, civilization modules CREDITS Use:Use: wild for titanium, ice, nanocarbon Over the ", "headingPath": "", "sharpsignalDocId": 320}, {"page": 6, "score": 0.046898, "snippet": "Player Materials: Each player takes the following materials in their chosen color: 1 station mat 1 player aid 6 transports 1 fighter 1 science vessel 1 heavy cruiser 9 leaders 6 dice 5 track markers 1 VP marker Station mats are double-sided for flexibility. Note the orientation of the four colorful ", "headingPath": "PLAYER SETUP · Station Mat: · Factions: · Ship Upgrades: · Progress Tracks:", "sharpsignalDocId": 320}, {"page": 26, "score": 0.046432, "snippet": "Special regions add unique effects and scoring bonuses to the game. You may choose either the 2 Quasar tiles or the 2 Vortex tiles to include in your game. Before you place any other starting tiles on the board, place the selected special region tiles on the board in the spaces marked with and . The", "headingPath": "Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · …", "sharpsignalDocId": 320}, {"page": 7, "score": 0.03125, "snippet": "Each player places 1 leader on each Alliance Base on the board. Each player rolls a die and places 2 leaders on the nebula matching the die rolled (more than 1 player can have leaders in the same nebula). Each player places their remaining 1 leader in the leaders area of their station. Choose a star", "headingPath": "Leaders: · Start Player:", "sharpsignalDocId": 320}, {"page": 5, "score": 0.030769, "snippet": "Shuffle the discovery tokens and stack 5 tokens face down on each of the 2 marked spaces on the science track. Stack another 5 discovery tokens face down on the observatory discoveries space at the top of the science track. Return the remaining tokens to the game box. Shuffle the supremacy tokens an", "headingPath": "Progress Tracks:", "sharpsignalDocId": 320}, {"page": 9, "score": 0.029851, "snippet": "On your turn, you must either launch a ship onto the board or bring back all your ships in a return TO STATION . You can also use any number of free actions during your turn. Launch and Return to Station turns, as well as free actions, are covered in detail over the following sections. At the end of", "headingPath": "TAKING YOUR TURN · LAUNCHING · First Launch · Subsequent Launches · Additional Launch Requirements", "sharpsignalDocId": 320}, {"page": 4, "score": 0.029412, "snippet": "4 Place the main board in the center of the table. Place the event board next to the main board and place the event marker on the start space for your player count. Choose an event deck for this game. We recommend Galactic Dawn for your first foray into the Edge. Shuffle the chosen deck and place it", "headingPath": "Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · …", "sharpsignalDocId": 320}]
- citations (raw)
- []
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 320 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 320 boosted
- answered-before recall
-
past answered rulings were found and offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
- ruling 1899 — matched by trigram similarity — measured similarity 0.8148
- debug row retained until
- Nov 6, 2026 17:22
retrieval — what the search arm returned
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 Andromeda's Edge — Rulebook (corpus doc 320) | Setup · Battle · CREDITS | p.27 | 0.04866 (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 Andromeda's Edge — Rulebook (corpus doc 320) | p.7 | 0.047883 (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 Andromeda's Edge — Rulebook (corpus doc 320) | PLAYER SETUP · Station Mat: · Factions: · Ship Upgrades: · Progress Tracks: | p.6 | 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 |
| #4 | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | Setup · SCORING · Placing Raiders · DESTINY CARDS · Quasars · NO ACTION IN A QUASAR · … | p.26 | 0.046432 (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 Andromeda's Edge — Rulebook (corpus doc 320) | Leaders: · Start Player: | p.7 | 0.03125 (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 Andromeda's Edge — Rulebook (corpus doc 320) | Progress Tracks: | p.5 | 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 |
| #7 | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | TAKING YOUR TURN · LAUNCHING · First Launch · Subsequent Launches · Additional Launch Requirements | p.9 | 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 Andromeda's Edge — Rulebook (corpus doc 320) | Table of Contents · Main Board: · Event Board: · Scrapyard: · Starting Regions: · Moon tokens: · … | p.4 | 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 |
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 273 ms · first delta 9910 ms · total 10016 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 273 ms · ask 9734 ms · gateway work 10016 ms · total 10016 ms
- tokens in (the prompt the answerer read)
- 3264
- tokens out (what the answerer generated)
- 9
- tok/sec
- 136.4 tok/sec — 9 output tokens in 0.066 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 23s 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
- ABSTAINED — Abstained — no grounded answer; closest passages below
- abstain rationale
-
I don't have enough information.
the answerer's own words, verbatim — hostile corpus/LLM text, rendered escaped
setup-shape — why the checklist band did or didn't render
- decision
- NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
- pattern that matched
- SETUP — "setup" / "set up"
- matched words (in the normalized question)
-
setup
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 249), 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.