You asked
How do I set up the game?
Answered counted as answeredAsked with: Viticulture Essential Editionbg-183394-en-1e
1. Set up your own vineyard as usual [1]. 2. Each player receives a vineyard mat and 3 different field cards:, and. Place them side by side (field side up) on the vineyard mat [2]. 3. Shuffle the 4 decks of small cards (green, yellow, purple, and blue) and place them on the board [2]. 4. Choose a player color for the Automa and place that VP marker on the End space on the victory point track [1]. 5. Place 1 glass token on each row of the wake-up chart [1]. 6. Shuffle the Automa deck and place it next to the wake-up chart [1]. 7. Remove any visitor cards that only give you a benefit if another player takes an action (alternatively, you can keep them in the deck and redraw when you draw one) [1]. 8. Each player places their rooster token above the wake-up chart [3]. 9. Each player places their cork token on the start space on the victory point track [3]. 10. Each player places their wine bottle token on the middle of the Residual Payment Tracker [3]. 11. After randomly selecting the first player, shuffle the red cards and deal one face-up to each player; do the same for the blue cards [4]. 12. Draw cards as indicated on your red card to form your opening hand before gaining resources from your blue card [4]. 13. Players make a choice regarding blue cards (starting with a specific structure or gaining extra lira) in clockwise order starting with the first player [4]. 14. After all starting resources are accounted for, discard the red and blue cards [4].
🔧 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 422 ms · ask 11156 ms · total 1275196 ms
- single-flight (PR-5)
- queued 1263604 ms · generation 11592 ms
- retrieval refs (raw)
- [{"page": 4, "score": 0.04866, "snippet": "Red and Blue Cards: After randomly selecting the first player, shuffle the red cards and deal one face-up to each player; do the same for the blue cards. These cards determine each player's starting resources. Advanced Variant: Some groups might prefer to let each player draw 2 red cards and 2 blue ", "headingPath": "sEtup", "sharpsignalDocId": 90}, {"page": 4, "score": 0.048387, "snippet": "Vineyard Mat: Each player receives a vineyard mat and 3 different field cards: , and . Place them side by side (field side up) on the vineyard mat. Shuffle the 4 decks of small cards (green, yellow, purple, and blue) and place them on the board. Deck Maintenance: If any of the four decks are exhaust", "headingPath": "GamE board sEtup", "sharpsignalDocId": 90}, {"page": 19, "score": 0.047371, "snippet": "You can play the game in campaign mode to add variation and challenge. The campaign mode consists of eight challenges, you must beat the Automa in each one to complete the campaign. Each time you lose, restart with the same challenge and begin with a number of bonus action tokens in hand equal to th", "headingPath": "campaiGn play", "sharpsignalDocId": 90}, {"page": 3, "score": 0.046244, "snippet": "Each player places their rooster token above the wake-up chart and their cork token on the start space on the victory point track. Each player should also place their wine bottle token on the middle of the Residual Payment Tracker. Note 1: There are negative numbers on the victory point track for a ", "headingPath": "GamE board sEtup", "sharpsignalDocId": 90}, {"page": 18, "score": 0.03125, "snippet": "Set up your own vineyard as usual. Choose a player color for the Automa and place that VP marker on the End space on the victory point track. Place 1 glass token on each row of the wake-up chart. Shuffle the Automa deck and place it next to the wake-up chart. Remove any visitor cards that onl y give", "headingPath": "sEtup", "sharpsignalDocId": 90}, {"page": 1, "score": 0.030769, "snippet": "Players allocate workers and play visitors to complete various tasks throughout the seasons (each worker is placed on one action each year). In the spring , players decide the schedule their workers will follow. An early rise gives the player the chance to act first; however, offering workers a late", "headingPath": "objEct of thE GamE", "sharpsignalDocId": 90}, {"page": 6, "score": 0.030303, "snippet": "Starting with the player who has the first player token and proceeding clockwise, each player will place their rooster on an open row of the wake-up chart to gain an instant bonus and determine player order for the rest of the year.", "headingPath": "Spring", "sharpsignalDocId": 90}, {"page": 19, "score": 0.029412, "snippet": "You can play against the Automa on five different difficulty levels: Very Easy: Add an eighth year. In this eighth year you can choose any wake-up chart row and you get a bonus action token. Easy: Start at 3 . Normal: As described in the rules above. Hard : Keep drawing Automa cards and place worker", "headingPath": "Difficulty Levels", "sharpsignalDocId": 90}]
- citations (raw)
- [{"page": 18, "quote": null, "headingPath": "sEtup", "sharpsignalDocId": 90}, {"page": 4, "quote": null, "headingPath": "GamE board sEtup", "sharpsignalDocId": 90}, {"page": 3, "quote": null, "headingPath": "GamE board sEtup", "sharpsignalDocId": 90}, {"page": 4, "quote": null, "headingPath": "sEtup", "sharpsignalDocId": 90}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 90 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 90 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:30
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 Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.4 | 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 Viticulture Essential Edition — Rulebook (corpus doc 90) | GamE board sEtup | p.4 | 0.048387 (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 Viticulture Essential Edition — Rulebook (corpus doc 90) | campaiGn play | p.19 | 0.047371 (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 Viticulture Essential Edition — Rulebook (corpus doc 90) | GamE board sEtup | p.3 | 0.046244 (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 Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.18 | 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 |
| #6 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | objEct of thE GamE | p.1 | 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 |
| #7 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Spring | 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)) | 232 |
| #8 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Difficulty Levels | p.19 | 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 Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.18 | no quote on the wire |
| [2] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | GamE board sEtup | p.4 | no quote on the wire |
| [3] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | GamE board sEtup | p.3 | no quote on the wire |
| [4] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.4 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 422 ms · first delta 8887 ms · total 1275196 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 1263604 ms · retrieval 422 ms · ask 11156 ms · gateway work 11592 ms · total 1275196 ms
- tokens in (the prompt the answerer read)
- 1667
- tokens out (what the answerer generated)
- 365
- tok/sec
- 137.4 tok/sec — 365 output tokens in 2.656 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 45s 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 21), 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.