You asked
How do I set up the game?
Answered counted as answeredAsked with: PARKSbg-266524-en-1e
To set up the game, follow these steps: 1. Place the board in between all players [1]. 2. Place the two token trays to the left and right of the board with their lids returned to the box [1]. 3. Shuffle all the Park cards face down to form the Parks deck, deal three face up into the top slots of the board, and place the deck onto the Parks deck area on the top right of the board [1]. 4. Shuffle all the Gear cards face down to form the Gear deck, deal three face up into the bottom Gear slots on the board, and place the deck onto the Gear deck area on the bottom right of the board [1]. 5. Shuffle the Canteen cards face down, deal one face up to each player as their starting Canteen, and place the remaining Canteen deck onto its area on the top left of the board [2]. 6. Shuffle the Year deck, deal two cards to each player, have players choose one as their Personal Bonus for the Year and discard the other facedown (for the first game, just deal one to each player), and return any unused Year cards facedown to the box [2]. 7. Shuffle the Season deck, place it onto the Season area of the board, and reveal the topmost card as the first Season [2]. 8. Create the first Season's Trail by placing the TRAILHEAD tile on the far left below the board [2]. 9. Gather the five Basic Site tiles (denoted with a ⓐ in the bottom right) [2]. 10. If playing a 4-5 player game, add the Site ( 4+ in the bottom right) to the Basic Sites; otherwise, return it to the box [2]. 11. Shuffle the Advanced Site tiles and add one to the Basic Sites to form the Trail deck [2]. 12. Place the remaining Advanced Sites facedown to the left of the Trailhead [2]. 13. Shuffle the Trail deck (the Basic Sites and one Advanced Site) and reveal one Site at a time directly to the right of the Trailhead, placing each additional Site to the right of the previous one until all are placed face up [2]. 14. Place the TRAIL END to the right of the last Site, ensuring it is not on the side showing the SOLO icon (for Solo mode, place it on the SOLO side) [2][3]. 15. Give each player two Hikers of the same color and place them onto the Trailhead [2]. 16. Give each player a Campfire matching their Hiker color and place it on the lit side in front of them [2]. 17. Give the FIRST HIKER MARKER to the player who most recently took a hike [2]. 18. Give the CAMERA to the player to the right of the First Hiker [2]. 19. Return any unused Hikers and Campfires to the box [2].
🔧 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 265 ms · ask 8642 ms · total 1790427 ms
- single-flight (PR-5)
- queued 1781511 ms · generation 8916 ms
- retrieval refs (raw)
- [{"page": 2, "score": 0.04918, "snippet": "CANTEENS · Shuffle the Canteen cards face down. Deal one face up to each player. This is their starting Canteen. Place the remaining Canteen deck onto its area on the top left of the board. YEAR · Shuffle the Year deck. Deal two cards to each player. Players choose one of the two as their Personal B", "headingPath": "SETUP CONTINUED", "sharpsignalDocId": 236}, {"page": 6, "score": 0.046898, "snippet": "When setting up the Trail, place the Trail End on the SOLO side. After choosing your Hiker and Campfire color, choose one for the Rangers. Rangers do not need their Campfire. Place your Hikers and the Rangers at the Trailhead. Place the Ranger Tracker from the SOLO deck next to your play area. Shuff", "headingPath": "SOLO MODE SCORING", "sharpsignalDocId": 236}, {"page": 2, "score": 0.045724, "snippet": "1 1 Tri-fold board 2 Token trays ( EACH HOLDS ALL TOKEN TYPES ) 48 Park cards ( TAROT · 70 X 120 MM ) 10 Season cards ( SMALL · 50 X 75 MM ) 12 Year cards ( 50 X 75 MM ) 36 Gear cards ( 50 X 75 MM ) 15 Canteen cards ( 50 X 75 MM ) 9 Solo cards (SOLO MODE) ( 50 X 75 MM ) 10 Trail Sites 1 Trailhead an", "headingPath": "GAME COMPONENTS · OVERVIEW & GOAL · PARKS AREA", "sharpsignalDocId": 236}, {"page": 4, "score": 0.032258, "snippet": "The TRAIL END gives Hikers a moment to reflect on the journey. When a Hiker arrives here, the player immediately relights their Campfire if it is extinguished, and then chooses one of the available areas for their Hikerplacing it vertically in the farthest right available slot of that area: PLACE RE", "headingPath": "AT THE TRAIL END", "sharpsignalDocId": 236}, {"page": 3, "score": 0.031746, "snippet": "The four SEASONS of the Year will make up the four rounds of play over the course of the game. Seasons change-up gameplay each round, and a Season ends when all Hikers reach the Trail End. To start, see how the Season affects gameplay for the round and if any immediate action is necessary from its e", "headingPath": "STARTING A SEASON · TAKING TURNS · TRAIL SITES · BASIC SITES · ADVANCED SITES", "sharpsignalDocId": 236}, {"page": 4, "score": 0.03125, "snippet": "ONGOING ABILITY All Gear cards have ongoing abilities, but this one also has an action that rewards the player with a Canteen when purchased VISIT A PARK · Any number of Hikers can occupy the Visit a Park area. To Visit a Park, choose one of the three available on the board or one you have reserved ", "headingPath": "AT THE TRAIL END", "sharpsignalDocId": 236}, {"page": 7, "score": 0.030303, "snippet": "TAKING TURNS · Turns alternate between you and the Rangers. On your turn, choose either of your Hikers and move them down the Trail to visit a Site and take its action-following the same movement rules as multiplayer. For the Rangers' turn, flip over the top Gear card from the deck and place it in a", "headingPath": "SOLO MODE REFERENCE", "sharpsignalDocId": 236}, {"page": 6, "score": 0.029412, "snippet": "GAME DESIGN · Henry Audubon / GAME DEVELOPMENT · Mattox Shuler, Matt Aiken, Jennifer Graham-Macht, and Kyle Key RULE EDITING · Travis D. Hill / THANKS TO · Our Kickstarter Backers' love of national parks and making this project a reality LAYOUT DESIGN & ART DIRECTION · Mattox Shuler and J.P. Boneyar", "headingPath": "CREDITS & THANKS · SOLO MODE RULES", "sharpsignalDocId": 236}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "GAME COMPONENTS · OVERVIEW & GOAL · PARKS AREA", "sharpsignalDocId": 236}, {"page": 2, "quote": null, "headingPath": "SETUP CONTINUED", "sharpsignalDocId": 236}, {"page": 6, "quote": null, "headingPath": "SOLO MODE SCORING", "sharpsignalDocId": 236}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 236 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 236 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 6, 2026 14:40
retrieval — what the search arm returned
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 PARKS — Rulebook (corpus doc 236) | SETUP CONTINUED | p.2 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | 300 |
| #2 | RULEBOOK PARKS — Rulebook (corpus doc 236) | SOLO MODE SCORING | p.6 | 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 |
| #3 | RULEBOOK PARKS — Rulebook (corpus doc 236) | GAME COMPONENTS · OVERVIEW & GOAL · PARKS AREA | p.2 | 0.045724 (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 PARKS — Rulebook (corpus doc 236) | AT THE TRAIL END | p.4 | 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 |
| #5 | RULEBOOK PARKS — Rulebook (corpus doc 236) | STARTING A SEASON · TAKING TURNS · TRAIL SITES · BASIC SITES · ADVANCED SITES | p.3 | 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 |
| #6 | RULEBOOK PARKS — Rulebook (corpus doc 236) | AT THE TRAIL END | p.4 | 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 PARKS — Rulebook (corpus doc 236) | SOLO MODE REFERENCE | 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 |
| #8 | RULEBOOK PARKS — Rulebook (corpus doc 236) | CREDITS & THANKS · SOLO MODE RULES | p.6 | 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 |
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 PARKS — Rulebook (corpus doc 236) | GAME COMPONENTS · OVERVIEW & GOAL · PARKS AREA | p.2 | no quote on the wire |
| [2] | RULEBOOK PARKS — Rulebook (corpus doc 236) | SETUP CONTINUED | p.2 | no quote on the wire |
| [3] | RULEBOOK PARKS — Rulebook (corpus doc 236) | SOLO MODE SCORING | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 265 ms · first delta 4605 ms · total 1790427 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 1781511 ms · retrieval 265 ms · ask 8642 ms · gateway work 8916 ms · total 1790427 ms
- tokens in (the prompt the answerer read)
- 3696
- tokens out (what the answerer generated)
- 629
- tok/sec
- 147.9 tok/sec — 629 output tokens in 4.253 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 58s 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.
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)
-
set up
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 162), 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.