You asked
How do I setup the game?
Answered counted as answered1. Gain 3 tokens in any combination of gold, crystal, meat, and milk [1]. 2. Place starting coins to the left of your mat [1]. 3. Place your adventurer in Base Camp on your player mat [1]. 4. Place your guild token on the Dragon Guild space labeled 'START' [1]. 5. Place remaining player markers, dragons, and cave cards nearby [1]. 6. Note that although there are 2 nest icons, players begin with only 1 egg [1]. 7. Place training tokens in reach of all players [2]. 8. Randomly give a player the start player marker to begin the game [1]. 9. All players gain 6 coins and 1 egg at the beginning of the game [3].
🔧 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 550 ms · ask 13321 ms · total 13897 ms
- single-flight (PR-5)
- queued 0 ms · generation 13897 ms
- retrieval refs (raw)
- [{"page": 2, "score": 0.016393, "snippet": "Gain the 3 tokens in any combination of gold, crystal, meat, and milk. TIP: We recommend that players first look at their starting cards, then choose which resources to gain from the public supply based on those starting cards. Typically (though not always) players will wish to gain resources that m", "headingPath": "3 resources of their choice", "sharpsignalDocId": 52}, {"page": 2, "score": 0.016129, "snippet": "Place the training tokens in reach of all players. Perform all other setup steps as usual. 4 1ST PLACE 2ND 5 2", "headingPath": "SETUP CHANGES", "sharpsignalDocId": 53}, {"page": 2, "score": 0.015873, "snippet": "Places their player mat in front of them (see the image on the right). A Places their starting resources in their player area (left of their mat). B Places their starting egg on 1 of the 2 nest icons on their player mat. C 3 dragon cards (drawn from the deck) & 3 cave cards (drawn from the deck) Cho", "headingPath": "EACH PLAYER THEN:", "sharpsignalDocId": 52}, {"page": 2, "score": 0.015625, "snippet": "G SCORE IMPORTANT: At the beginning of the game, all players gain 6 coins and 1 egg, per normal rules. 6 7 3 2 4 3 In rounds 1, 2, and 3, on the turn when you choose to pass for the round, place your adventurer onto a space on the updated round tracker board in the section that corresponds to the cu", "headingPath": "RULE CHANGES 1 PLACE 3RD", "sharpsignalDocId": 53}, {"page": 4, "score": 0.015385, "snippet": "During a game of Wyrmspan, you will build a sanctuary for dragons. Your sanctuary begins with 3 excavated spaces-the leftmost space in your Crimson Cavern, your Golden Grotto, and your Amethyst Abyss. Throughout the game, you will build out these 3 caves from left to right, first excavating each emp", "headingPath": "OVERVIEW", "sharpsignalDocId": 52}, {"page": 5, "score": 0.015152, "snippet": "Select one action on your player mat (excavate, entice, or explore), move your adventurer there, pay the cost of that action (place the coin/eggs on the action), and then perform the action. If the public supply of eggs or coins runs low, players may return excess tokens from their mats to the suppl", "headingPath": "ON YOUR TURN", "sharpsignalDocId": 52}, {"page": 5, "score": 0.014925, "snippet": "PLAY A CAVE CARD INTO 1 OF YOUR CAVES. 1 The first space in each cave is already excavated, so over the course of the game you may excavate the 2nd, 3rd, and 4th spaces in each cave. Any cave card can be placed in any cave; the colors of the cave cards are purely for aesthetics. Select the left-most", "headingPath": "EXCAVATE", "sharpsignalDocId": 52}, {"page": 2, "score": 0.014706, "snippet": "Place the following items in the center of the table: DRAGON GUILD BOARD Select 1 of the 4 Dragon Guild tiles at random and place it in the center of the Dragon Guild board with the appropriate side (based on player count) face up. 1 CARD DISPLAY BOARD 2 DRAGONS Shuffle all dragons together and plac", "headingPath": "SETUP", "sharpsignalDocId": 52}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "3 resources of their choice", "sharpsignalDocId": 52}, {"page": 2, "quote": null, "headingPath": "SETUP CHANGES", "sharpsignalDocId": 53}, {"page": 2, "quote": null, "headingPath": "RULE CHANGES 1 PLACE 3RD", "sharpsignalDocId": 53}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
- 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
- Oct 24, 2026 04:45
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 Wyrmspan — Rulebook (corpus doc 52) | 3 resources of their choice | p.2 | 0.016393 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #2 | RULEBOOK Wyrmspan — Dragon Academy Expansion (corpus doc 53) | SETUP CHANGES | p.2 | 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 110 |
| #3 | RULEBOOK Wyrmspan — Rulebook (corpus doc 52) | EACH PLAYER THEN: | p.2 | 0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #4 | RULEBOOK Wyrmspan — Dragon Academy Expansion (corpus doc 53) | RULE CHANGES 1 PLACE 3RD | p.2 | 0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #5 | RULEBOOK Wyrmspan — Rulebook (corpus doc 52) | OVERVIEW | p.4 | 0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #6 | RULEBOOK Wyrmspan — Rulebook (corpus doc 52) | ON YOUR TURN | p.5 | 0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #7 | RULEBOOK Wyrmspan — Rulebook (corpus doc 52) | EXCAVATE | p.5 | 0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #8 | RULEBOOK Wyrmspan — Rulebook (corpus doc 52) | SETUP | p.2 | 0.014706 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 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 Wyrmspan — Rulebook (corpus doc 52) | 3 resources of their choice | p.2 | no quote on the wire |
| [2] | RULEBOOK Wyrmspan — Dragon Academy Expansion (corpus doc 53) | SETUP CHANGES | p.2 | no quote on the wire |
| [3] | RULEBOOK Wyrmspan — Dragon Academy Expansion (corpus doc 53) | RULE CHANGES 1 PLACE 3RD | p.2 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 550 ms · first delta n/a · total 13897 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 550 ms · ask 13321 ms · gateway work 13897 ms · total 13897 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 50s ago)
- stream path
- not recorded — this ruling predates the stream-path column (V41)
- 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 4), 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.