RuleSage cited table rulings
← Viticulture Essential Edition

You asked

How do I take my turn?

Answered counted as answered

To take your turn, follow these rules based on the provided sources: * **Turn Order:** The player at the top of the wake-up chart takes the first turn (either placing 1 worker or passing) each season, followed by each other player in wake-up order [1]. This order remains the same throughout the year [1]. * **Action Selection:** During your turn, you may place 1 worker on any available action space for the current season and must immediately take that action [2][3][4]. Alternatively, you may choose to pass; if you pass, you may place no more workers that season [2][3][4]. * **Season Specifics:** In the summer, you may choose to save your remaining workers for the winter by passing [3]. In the winter, you may place a worker on any available action space or pass [2]. * **Bonus Actions:** You may spend 1 Bonus Action Token (accumulated from previous years) when you place 1 of your workers on the board. If you do, discard the token to take the action and also gain the bonus associated with that action; these can be taken in any order [5]. * **Special Cards:** Certain cards provide unique ways to take actions or manage turns: * **Manager:** Allows you to take an action from a previous season without placing a worker [6]. * **Planner:** Allows you to place a worker on an action in a future season and take that action at the beginning of that season [6]. * **Organizer:** Allows you to move your position on the wake-up chart, take a bonus, and then pass to the next season [6].

[1] RULEBOOK Viticulture Essential Edition — Rulebook · p.20 · Glossary
[2] RULEBOOK Viticulture Essential Edition — Rulebook · p.6 · Winter
[3] RULEBOOK Viticulture Essential Edition — Rulebook · p.6 · Summer
[4] RULEBOOK Viticulture Essential Edition — Rulebook · p.7 · WorkEr placEmEnt
[5] RULEBOOK Viticulture Essential Edition — Rulebook · p.18 · Bonus Action Tokens
[6] RULEBOOK Viticulture Essential Edition — Rulebook · p.11 · ExamplEs & clarifications
🔧 debug — where this ruling came from
outcome
ANSWERED — Answered
corpus profile
live
answerer pin (deploy-frozen, attribution only)
gemma4:12b think:false 4eb23ef187e2
timings
search 573 ms · ask 14278 ms · total 14868 ms
single-flight (PR-5)
queued 0 ms · generation 14868 ms
retrieval refs (raw)
[{"page": 6, "score": 0.032266, "snippet": "Starting with the top player on the wake-up chart and proceeding down the chart, each player will place 1 worker on any available action space in the winter (blue action spaces) and then immediately take that action, or that player may choose to end their year by passing. This cycle of turns continu", "headingPath": "Winter", "sharpsignalDocId": 90}, {"page": 18, "score": 0.031754, "snippet": "Whenever you choose your wake-up slot at the beginning of the year, remove the glass token from the slot and place it to the side of your vineyard mat. Y ou may accumulate these Bonus Action T okens from year to year. Y ou may spend 1 of those tokens per turn when you place 1 of your workers on the ", "headingPath": "Bonus Action Tokens", "sharpsignalDocId": 90}, {"page": 20, "score": 0.031281, "snippet": "The temporary worker is considered to be that player's worker in all regards for the remainder of the current year, including any reference to \"your workers\" or \"your regular workers.\" When you retrieve workers at the end of the year, retrieve the temporary worker token and place it back on the wake", "headingPath": "Glossary", "sharpsignalDocId": 90}, {"page": 6, "score": 0.031258, "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": 11, "score": 0.026703, "snippet": "Cultivator Plant 1 . You may plant it on a field even if the total value of that field exceeds the max vine value. This is a one-time exception to the rules about planting on fields up to a certain vine value. That is, you may not continue to plant on that field in excess of the max vine value on fu", "headingPath": "ExamplEs & clarifications", "sharpsignalDocId": 90}, {"page": 7, "score": 0.025678, "snippet": "A player may use each worker only once a year. Thus a worker placed in the summer cannot be used in the winter. A player may place 1 worker per turn. In a 3-6 player game, multiple spaces are available for each action. The worker you place may go on any unoccupied space, even if there are other work", "headingPath": "WorkEr placEmEnt", "sharpsignalDocId": 90}, {"page": 18, "score": 0.015625, "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": 6, "score": 0.015385, "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}]
citations (raw)
[{"page": 20, "quote": null, "headingPath": "Glossary", "sharpsignalDocId": 90}, {"page": 6, "quote": null, "headingPath": "Winter", "sharpsignalDocId": 90}, {"page": 6, "quote": null, "headingPath": "Summer", "sharpsignalDocId": 90}, {"page": 7, "quote": null, "headingPath": "WorkEr placEmEnt", "sharpsignalDocId": 90}, {"page": 18, "quote": null, "headingPath": "Bonus Action Tokens", "sharpsignalDocId": 90}, {"page": 11, "quote": null, "headingPath": "ExamplEs & clarifications", "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 21, 2026 22:42

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) Winter p.6 0.032266 (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) Bonus Action Tokens p.18 0.031754 (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) Glossary p.20 0.031281 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#4 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) Summer p.6 0.031258 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#5 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) ExamplEs & clarifications p.11 0.026703 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#6 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) WorkEr placEmEnt p.7 0.025678 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) 300
#7 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) sEtup p.18 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
#8 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) Spring p.6 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) 232

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 Viticulture Essential Edition — Rulebook (corpus doc 90) Glossary p.20 no quote on the wire
[2] RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) Winter p.6 no quote on the wire
[3] RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) Summer p.6 no quote on the wire
[4] RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) WorkEr placEmEnt p.7 no quote on the wire
[5] RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) Bonus Action Tokens p.18 no quote on the wire
[6] RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) ExamplEs & clarifications p.11 no quote on the wire
timing split
retrieval 573 ms · first delta n/a · total 14868 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 573 ms · ask 14278 ms · gateway work 14868 ms · total 14868 ms
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 58s 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.
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 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.