Ruling — Tamashii: Chronicle of Ascend

You asked

How do I setup the game?

Answered counted as answered

Asked with: Tamashii: Chronicle of Ascendbg-356754-en-1e

The setup for Tamashii is divided into two phases: the first phase sets up all basic game components, and the second phase is scenario-specific.[1]

Phase 1: Basic Game Components

1. Place all Basic, Open Data, Ascend, Success, Universal, Damage, and EXP markers, and all dice in a Neutral pool where all players can easily reach them.[1]

2. Each player chooses one of the 4 Player Boards and the Dump tile of the same color.[1]

3. Place the Dump tile into the slot on the bottom of the Player Board.[1]

4. Place 4 Lock tokens on the rightmost marked column of the Launcher (skip this step if playing the Prologue).[1]

5. Place 1 Universal marker on slot 0 of the Trace track.[1]

6. Place 1 Universal marker on slot 0 of each of the four Asset tracks.[1]

7. Place an ITG Limiter in the same color as your Player Board on slot 5 of the Integrity track, then place 1 on slot 5 of the Integrity track inside the Limiter.[1]

8. Take 2 different, double-sided Core Data tokens; insert one with the icon matching your Player Board into the Core Data slot and place the other next to your Player Board.[1]

9. Each player takes 1 Data Bag and 3 Help cards (skip these steps if playing the Prologue).[1]

1 and 10. Each player chooses 1 Class Augment deck (Reaper, Brawler, Trickster, or Whisperer).[1]

11. Remove the Augment card with 'Solo/Pvp' on its back from the game.[1][2]

12. Place the other 2 Starting Augments face up in the indicated space near your Player Board.[2]

13. Shuffle the rest of the Class Augments and place them face down near your Player Board.[2]

Phase 2: Scenario-Specific Setup

The specific steps depend on the chosen Scenario, but generally include:

1. Map setup: Place the listed District tiles as indicated by the illustration, revealing some face up.[3]

2. Exploration tokens: Place 1 Exploration token on each indicated District tile.[3]

3. Enemy deck: Set cards so that the Enemies listed first are on top of the deck.[3]

4. Corrupted Data pool: Place the proper number of Corrupted Data tokens in the reserved space on the Time track.[3]

5. Faction Augment decks: Prepare and place the listed Faction Augment decks in the play area, if applicable.[3]

6. Players: Place player Characters on the indicated District tile and resolve other instructions.[3]

7. Scenario cards: Take the listed Scenario cards and place them in the play area next to the Time track; draw the first card and place it in the 'Scenario card' slot of the Time track.[3]

Modifications for Specific Modes

* Solo Mode: When selecting starting Augments, remove the Augment with 'Co-op' on its back and take the 'Solo/Pvp' one instead.[4] When placing your Character on the starting District tile, take one additional Walker Character and place it on the same tile (do not place a rubber ring on this additional Walker; this is J.O.R.D.A.N. BOT's Character).[4] Additionally, take the J.O.R.D.A.N. BOT card, place it near your Player Board, and place 1 in each Battery slot.[4]

* Prologue Scenario: Place players' standees/miniatures on the Damaged District tile (tile number 2).[5] Take all Scenario cards coded with 'A' and place them in the play area; draw card A01 and place it in the 'Scenario card' slot of the Time track.[5] Place all 16 Corrupted Data tokens in the Corrupted Data pool slot on the Time track.[5]

* Competitive Mode (Scenario Generator Setup): Choose a game length (Short: 5, Medium: 7, Long: 9).[6] Choose the First Player.[6] Take 1 random Map setup card and prepare the Map.[6] Place Characters on chosen starting District tiles (Shelter or Damaged District) such that each player starts on a different tile.[6] Take 1 random Conditions card, prepare the Enemy deck, and grant starting bonuses to all players.[6] Place any Data tokens directly in Data bags.[6] Take 1 random Enhancement card and place it face up in the play/area.[6] Take 1 random PvP card and place it face up in the

[1] RULEBOOK Tamashii: Chronicle of Ascend — Rulebook · p.4 · Before your first game

[2] RULEBOOK Tamashii: Chronicle of Ascend — Rulebook · p.4 · Before your first game

[3] RULEBOOK Tamashii: Chronicle of Ascend — Rulebook · p.5 · Scenario setup

[4] RULEBOOK Tamashii: Chronicle of Ascend — Rulebook · p.21 · Setup · Solo mode rules

[5] RULEBOOK Tamashii: Chronicle of Ascend — Rulebook · p.5 · SCENARIO SETUP EXAMPLE - PROLOGUE

[6] RULEBOOK Tamashii: Chronicle of Ascend — Rulebook · p.21 · Scenario generator (competitive mode): · Game Setup

So says the rulebook. So plays the table.

🔧 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 147 ms · ask 6163 ms · total 6313 ms
single-flight (PR-5): queued 0 ms · generation 6313 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 21, "score": 0.048172, "snippet": "Setup the game according to the normal Setup, with the following modifications: In the Setup, step 3 c) : when selecting the starting Augments, remove the Augment with the 'Co-op' on its back from the game and take the 'Solo/Pvp' one instead. In the Setup, step 1 1 : when placing your Character on t", "headingPath": "Setup · Solo mode rules", "sharpsignalDocId": 1296}, {"page": 4, "score": 0.047183, "snippet": "Before playing your first game of Tamashii , make sure you read the unboxing guide attached to the box. Then, when you are ready, the very first Scenario you play must always be the Prologue. Not only because it teaches you how to play in a simplified way, but also because it has an introduction sto", "headingPath": "Before your first game", "sharpsignalDocId": 1296}, {"page": 21, "score": 0.047163, "snippet": "In this game mode, players compete against each other to earn as much Victory Points (VP) as possible. The player who has the most VP at the end of the game is the winner. Perform a standard game Setup with the following modifications: In the Setup, step 3 c) : when selecting the starting Augments, ", "headingPath": "Scenario generator (competitive mode): · Game Setup", "sharpsignalDocId": 1296}, {"page": 5, "score": 0.045635, "snippet": "Place the Districts number 1 and 2 face up in the positions as shown on the illustration. Then, gather Districts: 3, 1 1, 1 2, 1 3, 1 4, and 16. Shuffle them and place them face down as indicated on the illustration. Take all the Exploration tokens and put all and back in the box. Then, shuffle the ", "headingPath": "SCENARIO SETUP EXAMPLE - PROLOGUE", "sharpsignalDocId": 1296}, {"page": 14, "score": 0.042745, "snippet": "The Planning phase is the initial preparation part of the turn. It is resolved simultaneously by all players (during this phase you plan your turn in advance and establish the plan with your teammates) . Trace Roll step: [skip this step during your first turn of the game, all players will have their", "headingPath": "Planning phase (resolved simultaneously)", "sharpsignalDocId": 1296}, {"page": 5, "score": 0.03125, "snippet": "Choose one of the available Scenario sheets - the art and description on the front of the Scenario sheet should help you decide and suggest what to expect in each individual story. Each Scenario has a different setup, but most setup sections are very similar and contain the following: Map setup: Tak", "headingPath": "Scenario setup", "sharpsignalDocId": 1296}, {"page": 4, "score": 0.030303, "snippet": "3c. Skip this step if you are playing the Prologue. 1 chosen Class Augment deck (each player chooses 1 of the 4 available Classes - Reaper, Brawler, Trickster, or Whisperer) . Then, remove the Augment card with 'Solo/Pvp' on its back from the game. Place the other 2 Starting Augments face up in the ", "headingPath": "Before your first game", "sharpsignalDocId": 1296}, {"page": 2, "score": 0.030214, "snippet": "2 Table of contents 1. Game introduction ..................................................................... 1 1a. Table of contents...................................................................... 2 1b. List of all Components ............................................................. 2 2.", "headingPath": "", "sharpsignalDocId": 1296}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 4, "quote": null, "headingPath": "Before your first game", "sharpsignalDocId": 1296}, {"page": 4, "quote": null, "headingPath": "Before your first game", "sharpsignalDocId": 1296}, {"page": 5, "quote": null, "headingPath": "Scenario setup", "sharpsignalDocId": 1296}, {"page": 21, "quote": null, "headingPath": "Setup · Solo mode rules", "sharpsignalDocId": 1296}, {"page": 5, "quote": null, "headingPath": "SCENARIO SETUP EXAMPLE - PROLOGUE", "sharpsignalDocId": 1296}, {"page": 21, "quote": null, "headingPath": "Scenario generator (competitive mode): · Game Setup", "sharpsignalDocId": 1296}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1296 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1296 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.88899 of 3288 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Oct 24, 2026 21:20 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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Setup · Solo mode rules	p.21	0.048172 (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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Before your first game	p.4	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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Scenario generator (competitive mode): · Game Setup	p.21	0.047163 (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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	SCENARIO SETUP EXAMPLE - PROLOGUE	p.5	0.045635 (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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Planning phase (resolved simultaneously)	p.14	0.042745 (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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Scenario setup	p.5	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
#7	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Before your first game	p.4	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
#8	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)		p.2	0.030214 (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 73 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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Setup · Solo mode rules	p.21	#1	0.048172 (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
#2	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Before your first game	p.4	#2	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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	SCENARIO SETUP EXAMPLE - PROLOGUE	p.5	#4	0.045635 (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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Before your first game	p.4	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Trace · Enemy deck setup · Enemies	p.12	#18	0.025015 (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
#6	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Locked vs Unlocked components	p.5	#20	0.024387 (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
#7	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Scenario setup	p.5	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Scenario generator (competitive mode): · Game Setup	p.21	#3	0.047163 (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 Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Before your first game	p.4	no quote on the wire
[2]	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Before your first game	p.4	no quote on the wire
[3]	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Scenario setup	p.5	no quote on the wire
[4]	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Setup · Solo mode rules	p.21	no quote on the wire
[5]	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	SCENARIO SETUP EXAMPLE - PROLOGUE	p.5	no quote on the wire
[6]	RULEBOOK Tamashii: Chronicle of Ascend — Rulebook (corpus doc 1296)	Scenario generator (competitive mode): · Game Setup	p.21	no quote on the wire

generation — timing and the path taken

timing split: retrieval 147 ms · first delta 1140 ms · total 6313 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 147 ms · ask 6163 ms · gateway work 6313 ms · total 6313 ms
tokens in (the prompt the answerer read): 3172
tokens out (what the answerer generated): 1024
tok/sec: 200.9 tok/sec — 1024 output tokens in 5.096 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 54s 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 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: 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 1226), 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.