RuleSage cited table rulings
← T.I.M.E Stories

You asked

How should we prepare everything before the first turn?

Answered counted as answered

Asked with: T.I.M.E Storiesbg-146508-en-1e

1. Set up the game board facing the players [1][2]. 2. Place half of the normal shields with the skull side showing and other half with the white shield showing, and sort the other three kinds of shields by type [2]. 3. Sort the 24 state tokens and place them to the left of the board [2]. 4. Place the Life points as well as the resource tokens above the board [3][1][2]. 5. Place the 6 action dice and the Time Captain die near the players [1][2]. 6. Place the time token and the group pawn near the players [1][2]. 7. Each player takes one of the main pawns of the color of their choice, as well as the small one of the matching color [1][2]. 8. Install your scenario’s Base cards while respecting the letters shown on the back of the cards [3]. 9. Place the rest of the deck in the indicated space [3]. 10. Pull out the N.T. [4][5].

[1] RULEBOOK T.I.M.E Stories — Rulebook · p.5 · SET-UP · The set-up of all scenarios remains the same. Simply follow the numbers below step-by-step.
[2] RULEBOOK T.I.M.E Stories — Rulebook · p.5 ·
[3] RULEBOOK T.I.M.E Stories — Rulebook · p.15 ·
[4] RULEBOOK T.I.M.E Stories — Rulebook · p.15 ·
[5] RULEBOOK T.I.M.E Stories — Rulebook · p.15 · AND YOU'RE READY TO START!
🔧 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 189 ms · ask 12596 ms · total 22050 ms
single-flight (PR-5)
queued 9254 ms · generation 12796 ms
retrieval refs (raw)
[{"page": 5, "score": 0.032787, "snippet": "As much as possible, sit on the same side of the game board so that everyone can clearly see the card panoramas during the game. 1> Set up the game board facing the players. This aids immersion and also helps in your missions as some details from the artwork can turn out to be vital… 3> Place the Li", "headingPath": "SET-UP · The set-up of all scenarios remains the same. Simply follow the numbers below step-by-step.", "sharpsignalDocId": 425}, {"page": 15, "score": 0.032258, "snippet": "You've now reached the end of the rules and can start your first mission. When all players are ready, pull out the N.T. 1921: Asylum deck and perform the following set-up: 17/06/2015 12:05 Livre_D01_US_Asylum_TS_080615.indb 1 17/06/2015 13:27 Advice for how to explain the rules: If you are the only ", "headingPath": "AND YOU'RE READY TO START!", "sharpsignalDocId": 425}, {"page": 8, "score": 0.031746, "snippet": "As with any other decision of the party, you can debate and argue as much as you want, but in the end each player does as they wish. However, if at least one agent decides to enter a location, all of them must do so as well. (Theo- retically, after reading card A, the group might decide to change lo", "headingPath": "", "sharpsignalDocId": 425}, {"page": 15, "score": 0.03125, "snippet": "(5) Select a player at random to read the Base’s card A out loud, then, in turn, each player reads one of the following cards. (3) Install your scenario’s Base cards while respecting the letters shown on the back of the cards. (6) And this is how the adventure begins! (4) Place the rest of the deck ", "headingPath": "", "sharpsignalDocId": 425}, {"page": 5, "score": 0.030769, "snippet": "5 PLAYER 1 PLAYER 2 PLAYER 3 PLAYER 4 1> Set up the game board facing the players. SET-UP The set-up of all scenarios remains the same. Simply follow the numbers below step-by-step. 4> Sort the 24 state tokens and place them to the left of the board. 2> Place half of the normal shields with the skul", "headingPath": "", "sharpsignalDocId": 425}, {"page": 6, "score": 0.030303, "snippet": "At the beginning of the scenario, you are at the T.I.M.E Agency base and you receive your mission briefing. It's then a question of you successfully completing that mission, ideally in a minimum number of attempts. An attempt is commonly called a 'run'. A run equals a complete game, meaning the use ", "headingPath": "OBJECT OF THE GAME · ANATOMY OF A DECK · SET-UP OF A DECK · RESETTING THE DECK", "sharpsignalDocId": 425}, {"page": 10, "score": 0.029851, "snippet": "Some die rolls result from rules specific to a location and cost no TU as they do not refer to a receptacle's characteristics. If you feel that you've explored everything or if you simply want a change of scenery, you can leave one location for another. This happens in five easy steps. Each player t", "headingPath": "Special rolls (no TU) · LOCATION CHANGE · 1. Leave the current location · 2. Choose a new location · Clarifications: · 3. Putting away the current location · …", "sharpsignalDocId": 425}, {"page": 9, "score": 0.029412, "snippet": "Note that there are no game turns, properly speaking, and all of these actions take place during a single TU. However, each player executes and resolves their action in an order chosen by the players . Green and Pink are in the middle of combat. They separately roll the number of dice appropriate fo", "headingPath": "All for 1 TU! · For 1 TU", "sharpsignalDocId": 425}]
citations (raw)
[{"page": 5, "quote": null, "headingPath": "SET-UP · The set-up of all scenarios remains the same. Simply follow the numbers below step-by-step.", "sharpsignalDocId": 425}, {"page": 5, "quote": null, "headingPath": "", "sharpsignalDocId": 425}, {"page": 15, "quote": null, "headingPath": "", "sharpsignalDocId": 425}, {"page": 15, "quote": null, "headingPath": "", "sharpsignalDocId": 425}, {"page": 15, "quote": null, "headingPath": "AND YOU'RE READY TO START!", "sharpsignalDocId": 425}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 425 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 425 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 7, 2026 05:02

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) SET-UP · The set-up of all scenarios remains the same. Simply follow the numbers below step-by-step. p.5 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
#2 RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) AND YOU'RE READY TO START! p.15 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
#3 RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) p.8 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
#4 RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) p.15 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
#5 RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) 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
#6 RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) OBJECT OF THE GAME · ANATOMY OF A DECK · SET-UP OF A DECK · RESETTING THE DECK p.6 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 T.I.M.E Stories — Rulebook (corpus doc 425) Special rolls (no TU) · LOCATION CHANGE · 1. Leave the current location · 2. Choose a new location · Clarifications: · 3. Putting away the current location · … p.10 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 T.I.M.E Stories — Rulebook (corpus doc 425) All for 1 TU! · For 1 TU p.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)) 300

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.

#documentheadingpagequote chars
[1] RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) SET-UP · The set-up of all scenarios remains the same. Simply follow the numbers below step-by-step. p.5 no quote on the wire
[2] RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) p.5 no quote on the wire
[3] RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) p.15 no quote on the wire
[4] RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) p.15 no quote on the wire
[5] RULEBOOK T.I.M.E Stories — Rulebook (corpus doc 425) AND YOU'RE READY TO START! p.15 no quote on the wire
timing split
retrieval 189 ms · first delta 11058 ms · total 22050 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 9254 ms · retrieval 189 ms · ask 12596 ms · gateway work 12796 ms · total 22050 ms
tokens in (the prompt the answerer read)
2881
tokens out (what the answerer generated)
235
tok/sec
139.5 tok/sec — 235 output tokens in 1.684 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 47s 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.
outcome
ANSWERED — Answered
abstain rationale (n/a — this ruling answered)
answered — no abstain rationale applies
decision
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

this game registers NO errata cards (edition 354), 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.