You asked
How do I setup the game?
Answered counted as answeredTo set up the game, follow these steps: 1. Set up your own vineyard as usual [1]. 2. Choose a player color for the Automa and place that VP marker on the End space on the victory point track [1]. 3. Place 1 glass token on each row of the wake-up chart [1]. 4. Shuffle the Automa deck and place it next to the wake-up chart [1]. 5. Remove any visitor cards that only give you a benefit if another player takes an action, or alternatively, keep them in the deck and redraw when you draw one [1]. 6. Randomly select the first player, then shuffle the red cards and deal one face-up to each player; do the same for the blue cards [2]. 7. Use the red and blue cards to determine starting resources: every red card provides 2 regular workers, and every blue card provides 1 grande worker and a certain amount of lira [2]. 8. Draw cards as indicated on your red card to form your opening hand before gaining resources from your blue card [2]. 9. Make choices regarding blue card benefits (such as starting with a specific structure or gaining extra lira) in clockwise order starting with the first player [2]. 10. Discard the red and blue cards once all starting resources are accounted for [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 4338 ms · ask 9116 ms · total 13461 ms
- single-flight (PR-5)
- queued 0 ms · generation 13461 ms
- retrieval refs (raw)
- [{"page": 19, "score": 0.032018, "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": 4, "score": 0.016393, "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": 6, "score": 0.016129, "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": 18, "score": 0.015873, "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": 4, "score": 0.015385, "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": 6, "score": 0.015152, "snippet": "Starting with the top player on the wake-up chart and proceeding down the chart, each player will either place 1 worker on any available action space in the summer (yellow action spaces) and then immediately take that action, or that player may choose to save their remaining workers for the winter b", "headingPath": "Summer", "sharpsignalDocId": 90}, {"page": 9, "score": 0.014925, "snippet": "Build one unbuilt structure on your vineyard mat by paying the cost and placing the corresponding structure token on your vineyard mat. (See page 12 for an explanation of each structure.) Gain Bonus: . : Note Players may only have one of each structure on their vineyard mat. Plant One Vine: Plant a ", "headingPath": "Build One Structure:", "sharpsignalDocId": 90}, {"page": 1, "score": 0.014706, "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}]
- citations (raw)
- [{"page": 18, "quote": null, "headingPath": "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 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 23, 2026 21:00
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 Viticulture Essential Edition — Rulebook (corpus doc 90) | campaiGn play | p.19 | 0.032018 (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 Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.4 | 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 |
| #3 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Spring | p.6 | 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 232 |
| #4 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.18 | 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 |
| #5 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | GamE board sEtup | 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 Viticulture Essential Edition — Rulebook (corpus doc 90) | Summer | p.6 | 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 Viticulture Essential Edition — Rulebook (corpus doc 90) | Build One Structure: | p.9 | 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 Viticulture Essential Edition — Rulebook (corpus doc 90) | objEct of thE GamE | p.1 | 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 Viticulture Essential Edition — Rulebook (corpus doc 90) | sEtup | p.18 | no quote on the wire |
| [2] | 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 4338 ms · first delta n/a · total 13461 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 4338 ms · ask 9116 ms · gateway work 13461 ms · total 13461 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 38s 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 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.