You asked
how do i setup the game?
Answered counted as answeredTo set up the game, follow these steps based on the provided sources: **Board and Components:** * Place the Viticulture World board on the table. Use the side with extra orange spaces if using structure cards from the Tuscany expansion [1]. * Shuffle the decks of small cards (green, yellow, purple, blue, and orange) and place them face down on their indicated spots on the board [1]. * Place the gray temporary worker token on the wake-up chart (the pocket watch) [1]. * Place all grape/wine tokens and the lira next to the board to form a general supply [1]. * Place the innovation tiles next to the board in two separate stacks by shape [1]. * Place the influence token on the track position corresponding to the player count [1]. * Place the green grape token on the first position of the year track [1]. **Continent Selection:** * Choose a continent. If new to Viticulture World, Greengully is recommended [1]. * Gather all cards for the selected continent and place the event token nearby [1]. * Read the story card for the chosen continent aloud and set it aside [1]. * Read the setup and rules cards for the continent aloud, follow those instructions, and set them aside [1]. **Event Deck:** * For your first game in each continent: Use event cards 1-6 for that continent. Sort them into a face-down deck (top card is 1, bottom is 6) and place it on its spot on the board; return unused cards to the box [1]. * For subsequent games (except Greengully): Shuffle all event cards for the selected continent and randomly place 6 cards face down as the event deck; return unused cards to the box [1]. **Player Setup:** * Each player takes a vineyard mat and places field cards on it [2]. * Each player places their own tokens next to their vineyard mat [2]. * Each player starts with 1 grande worker and 4 regular workers. To set this up, return 1 regular worker to the box (leaving 4) and attach 2 yellow hats and 2 blue hats to the 4 remaining regular workers [3][2]. * Place your residual payment token in the center of the residual payment tracker and place your victory point token on the start position [2]. * Each player draws one red card and one blue card and gains their benefits [3]. **Note on Workers:** * The 4 regular workers with yellow hats are summer workers; those with blue hats are winter workers. These can only be placed during their respective seasons (though they can also be used for year-round actions) [4]. * Grande workers, regular workers without hats, and the gray temporary worker are "trained" and can be placed in any season [4].
🔧 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 307 ms · ask 16297 ms · total 16628 ms
- single-flight (PR-5)
- queued 0 ms · generation 16628 ms
- retrieval refs (raw)
- [{"page": 2, "score": 0.032787, "snippet": "Game Board: Place the Viticulture World board on the table. Use the side with extra orange spaces at the top if you're using structure cards from the Tuscany expansion. Shuffle the decks of small cards (green, yellow, purple, blue, and orange, if used) and place each deck face down on its indicated ", "headingPath": "General setup", "sharpsignalDocId": 80}, {"page": 4, "score": 0.016129, "snippet": "During the spring season, perform the following 3 steps in order: Reveal 1 Event Card: Read the top card of the face-down event deck, starting with the historical flavor text and then the gameplay effect. Keep this card face-up next to the event deck. The gameplay effect only modifies the rules for ", "headingPath": "sprinG", "sharpsignalDocId": 80}, {"page": 7, "score": 0.015873, "snippet": "In turn order, choose one of the following two options: Place a winter worker, a trained worker, or a grande worker on a winter action or a (or a year-round action) OR pass. 1 . reveal a new event card summer spring A B draw play Most actions are similar to those found on the core game board; howeve", "headingPath": "winter", "sharpsignalDocId": 80}, {"page": 7, "score": 0.015625, "snippet": "When you pass during summer, you move into fall and perform the following steps in order: Move your rooster into the corresponding inner ring position on the wake-up chart (player order does not change). Choose one of the depicted benefits (gain , draw any 1 card, or age 1 of your grape tokens). The", "headingPath": "Fall", "sharpsignalDocId": 80}, {"page": 6, "score": 0.015385, "snippet": "In turn order (clockwise from the icon at the top of the track), choose one of the following two options: Place a summer worker, a trained worker, or a grande worker on a summer action (or a year-round action) OR pass. 1 . reveal a new event card spring Most actions are similar to those found on the", "headingPath": "summer", "sharpsignalDocId": 80}, {"page": 1, "score": 0.015152, "snippet": "Using the new game board, tiles, tokens, and event cards combined with the original vineyard mats and game cards, you have 6 years to achieve the two conditions necessary for victory in the selected region: (1) Each player must reach 25 victory points and (2) the shared influence token must reach th", "headingPath": "overview", "sharpsignalDocId": 80}, {"page": 3, "score": 0.014925, "snippet": "Red and Blue Cards: Each player draws one of each card and gains the benefits shown. As indicated on these cards, each player will start the game with 1 grande worker and all 4 regular workers. 4 Note : You may shuffle the new red cards in with the original Mama cards and the new blue cards in with ", "headingPath": "player setup", "sharpsignalDocId": 80}, {"page": 4, "score": 0.014706, "snippet": "Cards in Hand: Each player's hand of cards (visitor, vine, wine order, structure) may be open or closed information, depending on your group's preferred play style. During cooperative play, the word 'opponent' on visitor or structure cards refers to your fellow players. Victory Point Track: Part of ", "headingPath": "General rules", "sharpsignalDocId": 80}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "General setup", "sharpsignalDocId": 80}, {"page": 3, "quote": null, "headingPath": "Continent Difficulty Ranking:", "sharpsignalDocId": 80}, {"page": 3, "quote": null, "headingPath": "player setup", "sharpsignalDocId": 80}, {"page": 5, "quote": null, "headingPath": "worker plaCement", "sharpsignalDocId": 80}]
- 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 20, 2026 18:10
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 World — Rulebook (corpus doc 80) | General setup | p.2 | 0.032787 (at the 2-arm ceiling (0.03279) — the top of a 2-arm fuse; whether more arms ran here was never recorded) | 300 |
| #2 | RULEBOOK Viticulture World — Rulebook (corpus doc 80) | sprinG | p.4 | 0.016129 (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 World — Rulebook (corpus doc 80) | winter | p.7 | 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 Viticulture World — Rulebook (corpus doc 80) | Fall | p.7 | 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 Viticulture World — Rulebook (corpus doc 80) | summer | 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) | 300 |
| #6 | RULEBOOK Viticulture World — Rulebook (corpus doc 80) | overview | p.1 | 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 World — Rulebook (corpus doc 80) | player setup | p.3 | 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 World — Rulebook (corpus doc 80) | General rules | p.4 | 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 World — Rulebook (corpus doc 80) | General setup | p.2 | no quote on the wire |
| [2] | RULEBOOK Viticulture World — Rulebook (corpus doc 80) | Continent Difficulty Ranking: | p.3 | no quote on the wire |
| [3] | RULEBOOK Viticulture World — Rulebook (corpus doc 80) | player setup | p.3 | no quote on the wire |
| [4] | RULEBOOK Viticulture World — Rulebook (corpus doc 80) | worker plaCement | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 307 ms · first delta n/a · total 16628 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 307 ms · ask 16297 ms · gateway work 16628 ms · total 16628 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 44s 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 14), 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.