Ruling — Stationfall

You asked

How do I setup the game?

Answered counted as answered

Asked with: Stationfallbg-316624-en-1e

For the tutorial game, follow these steps:

1. Use the Board setup shown in the Component and Section presentation at the start of the Launch Manual.[1]

2. Place the station board between all players.[1]

3. For a 3-player tutorial, use 12 specific Characters (Astrochimp, Counselor, Cyborg, Daredevil, Engineer, Exile, Medical, Security, Station Chief, Stowaway, Stranger, and Troubleshooter) and 4 player colors (3 for the players and one for the scripted player 'Lindsey').[1]

4. If playing with more than 3 players, some can play 1 Character together.[1]

5. If playing with 2 or 1 player, play with the surplus players' cards open and decide together what the surplus players do during their turns.[1]

6. Each player takes 8 Influence cubes, 1 Activation disc, 1 Bribe token, 1 Reveal marker, 1 Guilt marker, and 3 Time markers in a color of their choice.[1]

7. Randomly assign a starting player and give that player the '1st player marker'.[1]

8. Place the 12 specific Character cards on the table next to the board.[1]

9. Find the Identity cards, Character pawns, and Kompromats for the 12 Characters in play.[1]

10. Place the Reentry token on the 0 spot on the Minute track.[2]

[1] RULEBOOK Stationfall — Rulebook · p.6 · TUTORIAL GAME SETUP · PLAYER COMPONENTS · CHARACTER CARDS · Player Setup example:

[2] RULEBOOK Stationfall — Rulebook · p.14 · ESCAPE AND PODS

That settles it — whose turn was it?

🔧 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 145 ms · ask 2690 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": 6, "score": 0.04918, "snippet": "Use the Board setup shown in the Component and Section presentation at the start of this Launch Manual. It shows the setup as it is intended in the tutorial game. Start by placing the station board between all players. The Tutorial game is meant to be played by 3 players, using 12 specific Character", "headingPath": "TUTORIAL GAME SETUP · PLAYER COMPONENTS · CHARACTER CARDS · Player Setup example:", "sharpsignalDocId": 709}, {"page": 22, "score": 0.048131, "snippet": "Decide how many Bots you want to use. The more, the more difficult to win. Assign each Bot and each human player a color, and a set of player components. Randomly decide the starting player, which could be either a player or a Bot. There should be a minimum of 3 players (human or Bot) in a game of S", "headingPath": "SETUP", "sharpsignalDocId": 709}, {"page": 7, "score": 0.047379, "snippet": "Place the following on the board: Each player's Guilt marker on 'Innocent '. The 3-9 player Minute marker on the Minute track's slot 13. Randomize the 3 Reentry tokens face down , and place 1 on the 0 Minute slot on the Minute track. The 'Abandon ship marker' on the 'Abandon Ship' box in top right o", "headingPath": "Markers:", "sharpsignalDocId": 709}, {"page": 5, "score": 0.031746, "snippet": "This is the book you are reading and it is the best place to start your journey. In it you will find: The Components and a map with all related terminology indicated , located on the foldout part of the cover. A Tutorial game where you play following special game instructions. The rules are not alte", "headingPath": "STATIONFALL LAUNCH MANUAL · STATIONFALL REFERENCE MANUAL · STATIONFALL CHARACTER DOSSIER", "sharpsignalDocId": 709}, {"page": 15, "score": 0.030769, "snippet": "Turn: 5 Start the turn by moving the Minute marker to 9. Here the Tutorial game splits into two paths. If this is the first time you are playing this tutorial keep reading. If it is the second time please skip ahead to the next paragraph, ' The 2nd time you play the tutorial .' Continue playing on y", "headingPath": "9 MINUTES TO STATIONFALL · THE 1ST TIME YOU PLAY THE TUTORIAL: · THE 2ND TIME YOU PLAY THE TUTORIAL:", "sharpsignalDocId": 709}, {"page": 7, "score": 0.030303, "snippet": "be your Secret Identity and the other will become your Bonus Character (BC) which score Friend or Grudge points for you. Keep your Secret Identity as it is and rotate the BC 180 degrees, keeping both secret from the other players. Put components on the map following the list below: Map modifications", "headingPath": "SECRET IDENTITIES AND HOW TO WIN · SECTIONS, ITEMS AND PAWNS ON THE STATION", "sharpsignalDocId": 709}, {"page": 21, "score": 0.029851, "snippet": "Read the tips on your Identity Card. by Petr Pospíšil You may not need to trigger Abandon Ship if Rocket Wings, Inspector's Shuttle, Medevac Pod, or Boarder is in the game. Read all Characters Abilities carefully and find who can be helpful to you. If you are not familiar with the game do not read A", "headingPath": "What to do at the beginning? · STATIONFALL PRIMER · When to Reveal? · What to do in the mid game? · What to do in the end game? · Oh no, I am dead! (Downed).", "sharpsignalDocId": 709}, {"page": 23, "score": 0.029412, "snippet": "Follow the instructions on the script card and perform the first possible Manoeuver in that script. (See the chapter 'Running the Bots' below for more information about the Manoeuvres and Eligibility). Remember to place the Bots Activation disc on the Character it ends up Activating. If a Manoeuvre ", "headingPath": "Bot Activate? · Bot Renegotiate?", "sharpsignalDocId": 709}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 6, "quote": null, "headingPath": "TUTORIAL GAME SETUP · PLAYER COMPONENTS · CHARACTER CARDS · Player Setup example:", "sharpsignalDocId": 709}, {"page": 14, "quote": null, "headingPath": "ESCAPE AND PODS", "sharpsignalDocId": 709}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 709 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 709 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.88337 of 986 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Oct 24, 2026 22:16 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 Stationfall — Rulebook (corpus doc 709)	TUTORIAL GAME SETUP · PLAYER COMPONENTS · CHARACTER CARDS · Player Setup example:	p.6	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Stationfall — Rulebook (corpus doc 709)	SETUP	p.22	0.048131 (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 Stationfall — Rulebook (corpus doc 709)	Markers:	p.7	0.047379 (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 Stationfall — Rulebook (corpus doc 709)	STATIONFALL LAUNCH MANUAL · STATIONFALL REFERENCE MANUAL · STATIONFALL CHARACTER DOSSIER	p.5	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
#5	RULEBOOK Stationfall — Rulebook (corpus doc 709)	9 MINUTES TO STATIONFALL · THE 1ST TIME YOU PLAY THE TUTORIAL: · THE 2ND TIME YOU PLAY THE TUTORIAL:	p.15	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
#6	RULEBOOK Stationfall — Rulebook (corpus doc 709)	SECRET IDENTITIES AND HOW TO WIN · SECTIONS, ITEMS AND PAWNS ON THE STATION	p.7	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))	300
#7	RULEBOOK Stationfall — Rulebook (corpus doc 709)	What to do at the beginning? · STATIONFALL PRIMER · When to Reveal? · What to do in the mid game? · What to do in the end game? · Oh no, I am dead! (Downed).	p.21	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 Stationfall — Rulebook (corpus doc 709)	Bot Activate? · Bot Renegotiate?	p.23	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 59 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 Stationfall — Rulebook (corpus doc 709)	TUTORIAL GAME SETUP · PLAYER COMPONENTS · CHARACTER CARDS · Player Setup example:	p.6	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Stationfall — Rulebook (corpus doc 709)	12 MINUTES TO STATIONFALL · LINDSEY'S STRATEGY	p.11	#10	0.026879 (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 Stationfall — Rulebook (corpus doc 709)	SUSPECT · LINDSEY'S STRATEGY · LINDSEY'S ACTIONS · PLAYERS' ACTIONS - TURN 5	p.16	#13	0.024585 (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
#4	RULEBOOK Stationfall — Rulebook (corpus doc 709)	9 MINUTES TO STATIONFALL · THE 1ST TIME YOU PLAY THE TUTORIAL: · THE 2ND TIME YOU PLAY THE TUTORIAL:	p.15	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Stationfall — Rulebook (corpus doc 709)	ESCAPE AND PODS	p.14	#29	0.012195 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#6	RULEBOOK Stationfall — Rulebook (corpus doc 709)	What to do at the beginning? · STATIONFALL PRIMER · When to Reveal? · What to do in the mid game? · What to do in the end game? · Oh no, I am dead! (Downed).	p.21	#7	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 Stationfall — Rulebook (corpus doc 709)	SETUP · DIFFERENCES BETWEEN BOTS AND HUMAN PLAYERS · A BOT'S TURN · Reveal? · Bot Influence?	p.23	#11	0.025245 (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 Stationfall — Rulebook (corpus doc 709)	SETUP	p.22	#2	0.048131 (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

#	document	heading	page	quote chars
[1]	RULEBOOK Stationfall — Rulebook (corpus doc 709)	TUTORIAL GAME SETUP · PLAYER COMPONENTS · CHARACTER CARDS · Player Setup example:	p.6	no quote on the wire
[2]	RULEBOOK Stationfall — Rulebook (corpus doc 709)	ESCAPE AND PODS	p.14	no quote on the wire

generation — timing and the path taken

timing split: retrieval 145 ms · first delta 1172 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 145 ms · ask 2690 ms · gateway work 2838 ms · total 2838 ms
tokens in (the prompt the answerer read): 3832
tokens out (what the answerer generated): 316
tok/sec: 199.7 tok/sec — 316 output tokens in 1.582 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 29s 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 5h, checked 4s 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: 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 643), 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.