RuleSage cited table rulings
← The Shipwreck Arcana

You asked

How do I play?

Answered counted as answered

Asked with: The Shipwreck Arcanabg-220517-en-1e

During a player's turn, the active player takes the following steps in order:
1. Draw fates from the token bag until you have 2 fates in your hand, or 1 new fate if you are starting your turn with a fate from a previous turn.[1]
2. Play 1 of your fates face-up in front of 1 of the 5 cards in the central play area, obeying that card's ability text.[1]
3. Predict (optional): Your allies may make a single unanimous prediction attempting to guess the value of the fate still in your hand.[1] They may discuss and ask you to flip number line tokens to reflect what they think they have learned.[1][2]
4. Resolve: If a prediction was made, a correct prediction allows you to be freed from that fate and the players score 1 point (moving the green score tracker up 1 space); an incorrect prediction advances the players' doom (moving the red doom tracker up 1 space).[1] After any prediction, discard your fate back to the bag and reset your number line.[1]
5. Fade: At the end of each turn, check to see if any arcana cards fade.[1] An arcana card fades when the sum of the pips (hours) from all fates in front of it is greater than or equal to its duration.[3] When a card fades, discard the fates in front of it to the bag, flip the card over, place it below the central play area, and refill the row with the top card of the arcana deck.[3] Fading a card advances the players' doom by 2, unless allies made a correct prediction this turn.[3]
[1] RULEBOOK The Shipwreck Arcana — Rulebook · p.2 · PLAYER TURN · 1. Draw · 2. Play · 3. Predict (optional) · 4. Resolve · 5. Fade · …
[2] RULEBOOK The Shipwreck Arcana — Rulebook · p.1 · FATE TOKENS · NUMBER LINE TOKENS
[3] RULEBOOK The Shipwreck Arcana — Rulebook · p.2 · FADING · ENDING THE GAME · STRATEGY

Settled. Play on.

🔧 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 85 ms · ask 2928 ms · total 3015 ms
single-flight (PR-5)
queued 0 ms · generation 3015 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 2, "score": 0.04866, "snippet": "During a player's turn, they are the active player, and take the following steps in order: Draw fates from the token bag until you have 2 fates in your hand. You may not show these fates to your allies or look at the other fates in the bag. Later in the game, you may start your turn holding a fate f", "headingPath": "PLAYER TURN · 1. Draw · 2. Play · 3. Predict (optional) · 4. Resolve · 5. Fade · …", "sharpsignalDocId": 754}, {"page": 2, "score": 0.047643, "snippet": "An arcana card will fade when the number of hours in front of it (the sum of the pips from all its fates) is greater than or equal to its duration (the moons at the bottom of the card). When a card fades, do the following: Discard all of the fates in front of it back to the bag. Flip it over and pla", "headingPath": "FADING · ENDING THE GAME · STRATEGY", "sharpsignalDocId": 754}, {"page": 2, "score": 0.047643, "snippet": "Players can easily join or leave the game after it has started. If a player joins the game, give them a set of number line tokens and choose a spot for them in the turn order. If a player leaves the game, discard any fate they were holding and put away their number line tokens. If you wish to increa", "headingPath": "ADDING OR REMOVING PLAYERS · 2-PLAYER CHALLENGE MODE · FREQUENTLY ASKED QUESTIONS · CREDITS", "sharpsignalDocId": 754}, {"page": 1, "score": 0.046898, "snippet": "When an arcana card fades (see: Fading), flip it over and place it below the central play area. The back of each arcana card has a helpful power that can be used once by the players; after using a card's faded power, place that card face-up on the bottom of the arcana deck. Each faded power describe", "headingPath": "FADED CARD POWERS", "sharpsignalDocId": 754}, {"page": 1, "score": 0.04598, "snippet": "Trapped in a drowned world, you and your allies are doomed - or are you? Using a mystical deck and a healthy dose of logic, you can predict each other's fates and escape unscathed. This is a cooperative deduction game for 2-5 players. You and your friends are fortune tellers trying to prevent terrib", "headingPath": "COMPONENTS · SETUP · THE HOURS CARD · ARCANA CARDS · FRONT SIDE FEATURES · BACK SIDE FEATURES", "sharpsignalDocId": 754}, {"page": 1, "score": 0.045928, "snippet": "Fate tokens are black. The front of each fate shows its value (numeral 1 through 7), and how many hours (pips) it consumes when played. A fate's value is what the other players will try to predict (using the arcana cards). The hours on it determine how quickly that fate will cause arcana cards to fa", "headingPath": "FATE TOKENS · NUMBER LINE TOKENS", "sharpsignalDocId": 754}, {"page": 2, "score": 0.030769, "snippet": "Jacqueline Bishop, Tonya Brenner, Dan Miller, Peter Plashko, Laetetia Sledz, AJ & Jessica Perez, Joe Farrell & Diane Kuhn, Benjamin Yamada, Sheri Paschen, Andrew Helton, Phil Gallagher, Shawn French, Harley Cox, Kerry Milan, Ned Bates, Adam Holt", "headingPath": "PLAYTESTERS", "sharpsignalDocId": 754}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 2, "quote": null, "headingPath": "PLAYER TURN · 1. Draw · 2. Play · 3. Predict (optional) · 4. Resolve · 5. Fade · …", "sharpsignalDocId": 754}, {"page": 1, "quote": null, "headingPath": "FATE TOKENS · NUMBER LINE TOKENS", "sharpsignalDocId": 754}, {"page": 2, "quote": null, "headingPath": "FADING · ENDING THE GAME · STRATEGY", "sharpsignalDocId": 754}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 754 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 754 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.92242 of 1173 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until
Nov 26, 2026 07:18 UTC

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) PLAYER TURN · 1. Draw · 2. Play · 3. Predict (optional) · 4. Resolve · 5. Fade · … p.2 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 The Shipwreck Arcana — Rulebook (corpus doc 754) FADING · ENDING THE GAME · STRATEGY p.2 0.047643 (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 The Shipwreck Arcana — Rulebook (corpus doc 754) ADDING OR REMOVING PLAYERS · 2-PLAYER CHALLENGE MODE · FREQUENTLY ASKED QUESTIONS · CREDITS p.2 0.047643 (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 The Shipwreck Arcana — Rulebook (corpus doc 754) FADED CARD POWERS p.1 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
#5 RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) COMPONENTS · SETUP · THE HOURS CARD · ARCANA CARDS · FRONT SIDE FEATURES · BACK SIDE FEATURES p.1 0.04598 (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 The Shipwreck Arcana — Rulebook (corpus doc 754) FATE TOKENS · NUMBER LINE TOKENS p.1 0.045928 (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 The Shipwreck Arcana — Rulebook (corpus doc 754) PLAYTESTERS p.2 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)) 245

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 7 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 atdocumentheadingpage fused rankfused RRF scorecarried byhow it got its slot
#1 RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) PLAYER TURN · 1. Draw · 2. Play · 3. Predict (optional) · 4. Resolve · 5. Fade · … p.2 #1 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)) vector + full-text + the doc-priority boost arm the re-ranker chose it
#2 RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) FADING · ENDING THE GAME · STRATEGY p.2 #2 0.047643 (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 The Shipwreck Arcana — Rulebook (corpus doc 754) FATE TOKENS · NUMBER LINE TOKENS p.1 #6 0.045928 (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 The Shipwreck Arcana — Rulebook (corpus doc 754) PLAYTESTERS p.2 #7 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 The Shipwreck Arcana — Rulebook (corpus doc 754) FADED CARD POWERS p.1 #4 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)) vector + full-text + the doc-priority boost arm the re-ranker chose it
#6 RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) COMPONENTS · SETUP · THE HOURS CARD · ARCANA CARDS · FRONT SIDE FEATURES · BACK SIDE FEATURES p.1 #5 0.04598 (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
#7 RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) ADDING OR REMOVING PLAYERS · 2-PLAYER CHALLENGE MODE · FREQUENTLY ASKED QUESTIONS · CREDITS p.2 #3 0.047643 (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

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 The Shipwreck Arcana — Rulebook (corpus doc 754) PLAYER TURN · 1. Draw · 2. Play · 3. Predict (optional) · 4. Resolve · 5. Fade · … p.2 no quote on the wire
[2] RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) FATE TOKENS · NUMBER LINE TOKENS p.1 no quote on the wire
[3] RULEBOOK The Shipwreck Arcana — Rulebook (corpus doc 754) FADING · ENDING THE GAME · STRATEGY p.2 no quote on the wire
timing split
retrieval 85 ms · first delta 1169 ms · total 3015 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 85 ms · ask 2928 ms · gateway work 3015 ms · total 3015 ms
tokens in (the prompt the answerer read)
3042
tokens out (what the answerer generated)
358
tok/sec
199.1 tok/sec — 358 output tokens in 1.798 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 58s 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 60h, checked 3s 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.
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 688), 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.