RuleSage cited table rulings
← Viticulture Essential Edition

You asked

How do I setup the game?

Abstained — no grounded answer; closest passages below counted as honest abstain

Asked with: Viticulture Essential Editionbg-183394-en-1e

Answered before

This question didn't get an answer just now — but Viticulture Essential Edition has been asked something like it before. The corpus may have changed since, so check the date and the answerer on each one before you rule from it.

How do I setup the game?

Answered Aug 2, 2026 gemma4:26b

How do I setup the game?

Answered Aug 2, 2026 gemma4:26b

How do I setup the game?

Answered Aug 1, 2026 gemma4:26b

The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.

RULEBOOK Viticulture Essential Edition — Rulebook · p.4 · sEtup
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
RULEBOOK Viticulture Essential Edition — Rulebook · p.4 · GamE board sEtup
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
RULEBOOK Viticulture Essential Edition — Rulebook · p.19 · campaiGn play
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
RULEBOOK Viticulture Essential Edition — Rulebook · p.3 · GamE board sEtup
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
RULEBOOK Viticulture Essential Edition — Rulebook · p.18 · sEtup
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
🔧 debug — where this ruling came from
outcome
ABSTAINED — Abstained — no grounded answer; closest passages below
corpus profile
live
answerer pin (deploy-frozen, attribution only)
gemma4:26b think:false 5571076f3d70
timings
search 220 ms · ask 6523 ms · total 6752 ms
single-flight (PR-5)
queued 0 ms · generation 6752 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.046875, "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.046696, "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.031746, "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.030769, "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": 1, "score": 0.029851, "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": 9, "score": 0.029412, "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}]
citations (raw)
[]
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
past answered rulings were found and offered
similarity threshold in force: 0.55 (rulesage.answered-before.similarity-threshold; the exact-question tier is not gated by it)
  • ruling 784 — matched by the same question (normalized, punctuation folded) — measured similarity 1.0
  • ruling 697 — matched by the same question (normalized, punctuation folded) — measured similarity 1.0
  • ruling 537 — matched by the same question (normalized, punctuation folded) — measured similarity 1.0
debug row retained until
Nov 3, 2026 05:43

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 rankdocumentheadingpage fused RRF scoresnippet 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.046875 (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.046696 (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.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 Viticulture Essential Edition — Rulebook (corpus doc 90) Spring p.6 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)) 232
#7 RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) objEct of thE GamE p.1 0.029851 (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 Viticulture Essential Edition — Rulebook (corpus doc 90) Build One Structure: p.9 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

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
timing split
retrieval 220 ms · first delta 6644 ms · total 6752 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 220 ms · ask 6523 ms · gateway work 6752 ms · total 6752 ms
tokens in (the prompt the answerer read)
1600
tokens out (what the answerer generated)
9
tok/sec
152.5 tok/sec — 9 output tokens in 0.059 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 48s 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.
outcome
ABSTAINED — Abstained — no grounded answer; closest passages below
abstain rationale
I don't have enough information.
the answerer's own words, verbatim — hostile corpus/LLM text, rendered escaped
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

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.