You asked
How do I take my turn?
Answered counted as answeredAsked with: Andromeda's Edgebg-358661-en-1e
On your turn, you must choose to either launch a ship onto the board or bring back all your ships in a return TO STATION [1][2]. You may also use any number of free actions during your turn [1][3]. **Launch Turn** 1. Choose a ship in your Launch Bay and place it in a region of your choice on the board [1]. * If you have no ships on the board, you may launch to any unoccupied region (a region is occupied if it contains a raider or at least 1 player's ship) [1]. * If you have 1 or more ships on the board, you must launch to a region within range of at least one of your other ships using that ship's range value; you may not launch to a region where you already have ships [1]. * You may only launch to an Alliance Base if you are able to activate it and do not use a nebula unless the ship has Voyage [1][2]. 2. Activate the region to take its specific action [1]. 3. If the active region is occupied by 2 or more players or by 1 or more players and raiders, resolve a battle [4]. 4. At the end of your turn, discard any resources in excess of your limits [1]. **Return to Station Turn** 1. Return all your ships one-by-one from the board and Scrapyard to your station [5]. 2. During this step, you may activate any number of modules on your station, in any order, to gain their printed benefit [5]. * To activate a module, take 1 ship from anywhere on the board (or the Repair Barge area of the Scrapyard) and place it on the module, or take 1 energy from your storage area and place it on the module [5]. * You may not activate a module that already has a ship or energy on it, nor modules with damage markers [5]. * You may only activate a module using energy if you have already activated a module in the same row using a ship [5]. 3. Return all ships from modules, the Scrapyard, and the board to the Launch Bay on your station [3]. 4. Remove all damage markers from any ships with shields [3]. 5. Return all energy spent to activate modules to the supply [3][6]. 6. Discard any tactics cards with sustain abilities [3][6]. **Free Actions (can be used during your turn)** * Slot a moon token into a module or Tactical Operations area [3]. * Play tactics cards (at their indicated time) [3][7]. * Use a development card [3]. * Discard a discovery/supremacy token to gain its benefit [3][7]. * Recruit any number of leaders of your color from regions where you have ships [7]. * Discard a claimed moon to gain resources/VP or to repair a ship/module [7]. * Gain bonus resources from regions where you have ships [7]. * Use faction abilities (unless otherwise specified) [7].
🔧 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 236 ms · ask 13441 ms · total 13688 ms
- single-flight (PR-5)
- queued 0 ms · generation 13688 ms
- retrieval refs (raw)
- [{"page": 9, "score": 0.048412, "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": 13, "score": 0.047183, "snippet": "Taking Your Turn // Free ActionsTaking Your Turn // Free Actions STEPSTEP 33 Discard ENERGY After ships are returned to the Launch Bay, return all energy you spent to activate modules to the supply. If you have played any tactics cards with sustain abilities, these are also discarded at this time. H", "headingPath": "", "sharpsignalDocId": 320}, {"page": 25, "score": 0.045235, "snippet": "97 98 98 0 96 97 99 95 96 1 95 97 When any player's VP marker reaches or surpasses the terminus marker on the VP track, this triggers the end of the game. 94 98 96 96 94 0 1 2 When game end is triggered, immediately remove the event marker from the event track. Event cards can't be triggered during ", "headingPath": "Final Scoring · Resolving Ties", "sharpsignalDocId": 320}, {"page": 12, "score": 0.045009, "snippet": "During a Return to Station turn, you return all your ships one-by-one from the board and Scrapyard to your station. The ships you return from the board and the Repair Barge area of the Scrapyard may be used to activate modules on your station. If you have no ships left in your Launch Bay at the star", "headingPath": "RETURN TO STATION · Core Modules", "sharpsignalDocId": 320}, {"page": 25, "score": 0.044563, "snippet": "25 When any player’s VP markerVP marker reaches or surpasses the terminus marker on the VP track, this triggers the end of the game. When game end is triggered, immediately remove the event remove the event marker from the event track. marker from the event track. Event cards can’t be triggered duri", "headingPath": "", "sharpsignalDocId": 320}, {"page": 7, "score": 0.031746, "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": 21, "score": 0.03125, "snippet": "During the final step of a Launch turn, if the active region is occupied by 2 or more players or by 1 or more players and the raiders, a battle must be resolved. Battle can occur even if the active player does not have any ships in the active region. Everyone with ships in the active region must par", "headingPath": "BATTLE · BATTLE preparations", "sharpsignalDocId": 320}, {"page": 13, "score": 0.030886, "snippet": "EXAMPLE 13 ON ANY TURNON ANY TURN Slot a Moon TokenSlot a Moon Token Play Tactics CardsPlay Tactics Cards ON YOUR TURNON YOUR TURN Use Development CardUse Development Card Discard a Discovery/ Discard a Discovery/ Supremacy TokenSupremacy Token Recruit LeadersRecruit Leaders Abandon a Mo", "headingPath": "", "sharpsignalDocId": 320}]
- citations (raw)
- [{"page": 9, "quote": null, "headingPath": "TAKING YOUR TURN · LAUNCHING · First Launch · Subsequent Launches · Additional Launch Requirements", "sharpsignalDocId": 320}, {"page": 8, "quote": null, "headingPath": "GAME OVERVIEW · 96 REGIONS OF THE EDGE · Planets · 91 Alliance Bases · Nebulae", "sharpsignalDocId": 320}, {"page": 13, "quote": null, "headingPath": "", "sharpsignalDocId": 320}, {"page": 21, "quote": null, "headingPath": "BATTLE · BATTLE preparations", "sharpsignalDocId": 320}, {"page": 12, "quote": null, "headingPath": "RETURN TO STATION · Core Modules", "sharpsignalDocId": 320}, {"page": 13, "quote": null, "headingPath": "", "sharpsignalDocId": 320}, {"page": 14, "quote": null, "headingPath": "Action · Event · SUSTAIN · Diplomacy · Battle · Tactics Card Limit · …", "sharpsignalDocId": 320}]
- 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
-
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 12:12
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) | TAKING YOUR TURN · LAUNCHING · First Launch · Subsequent Launches · Additional Launch Requirements | p.9 | 0.048412 (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.13 | 0.047183 (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) | Final Scoring · Resolving Ties | p.25 | 0.045235 (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) | RETURN TO STATION · Core Modules | p.12 | 0.045009 (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) | p.25 | 0.044563 (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) | Leaders: · Start Player: | p.7 | 0.031746 (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) | BATTLE · BATTLE preparations | p.21 | 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 |
| #8 | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | p.13 | 0.030886 (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 |
|---|---|---|---|---|
| [1] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | TAKING YOUR TURN · LAUNCHING · First Launch · Subsequent Launches · Additional Launch Requirements | p.9 | no quote on the wire |
| [2] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | GAME OVERVIEW · 96 REGIONS OF THE EDGE · Planets · 91 Alliance Bases · Nebulae | p.8 | no quote on the wire |
| [3] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | p.13 | no quote on the wire | |
| [4] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | BATTLE · BATTLE preparations | p.21 | no quote on the wire |
| [5] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | RETURN TO STATION · Core Modules | p.12 | no quote on the wire |
| [6] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | p.13 | no quote on the wire | |
| [7] | RULEBOOK Andromeda's Edge — Rulebook (corpus doc 320) | Action · Event · SUSTAIN · Diplomacy · Battle · Tactics Card Limit · … | p.14 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 236 ms · first delta 8660 ms · total 13688 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 236 ms · ask 13441 ms · gateway work 13688 ms · total 13688 ms
- tokens in (the prompt the answerer read)
- 4021
- tokens out (what the answerer generated)
- 672
- tok/sec
- 135.4 tok/sec — 672 output tokens in 4.962 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 46s 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 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.