You asked
Who goes first?
Answered counted as answeredAsked with: Viticulture Essential Editionbg-183394-en-1e
1. Take all rooster tokens claimed by players, shake them in your hand, and randomly pick one; the player with that color is the first player and receives the first player token [1]. 2. In the spring, players place their roosters on an open row of the wake-up chart, starting with the player who has the first player token and proceeding clockwise [2]. 3. The placement on the wake-up chart determines the player order for the rest of the year [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 662 ms · ask 7841 ms · total 8526 ms
- single-flight (PR-5)
- queued 0 ms · generation 8526 ms
- retrieval refs (raw)
- [{"page": 6, "score": 0.032787, "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": 6, "score": 0.032258, "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": 6, "score": 0.031746, "snippet": "Wake-up chart : Starting with the player holding the first-player token and moving clockwise, each player places their rooster on an unoccupied wake-up row. The number represents how early that player wants their workers to wake up in the coming year. 1 is the earliest time and 7 is the latest. The ", "headingPath": "sprinG actions", "sharpsignalDocId": 90}, {"page": 6, "score": 0.03125, "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": 17, "score": 0.030769, "snippet": "When any player reaches or exceeds 20 victory points, the game will finish at the end of the current year (after year-end steps). The player with the most points wins. In the case of a tie, tiebreakers are (in order): Most lira Total value of wine in the cellar Total value of grapes on the crush pad", "headingPath": "End GamE Goal and tiEbrEakErs", "sharpsignalDocId": 90}, {"page": 20, "score": 0.030303, "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": 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": 18, "score": 0.029412, "snippet": "Place your rooster token as usual except that you can only place it on a space where there is a glass token. Remove the glass token and place it to the side of your player mat. This becomes a bonus action token. Note: The \"Organizer\" summer visitor card action can not move your rooster to row 7.", "headingPath": "Wake-Up Chart", "sharpsignalDocId": 90}]
- citations (raw)
- [{"page": 4, "quote": null, "headingPath": "GamE board sEtup", "sharpsignalDocId": 90}, {"page": 6, "quote": null, "headingPath": "Spring", "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 3, 2026 03:56
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) | Spring | p.6 | 0.032787 (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 |
| #2 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Summer | p.6 | 0.032258 (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) | sprinG actions | p.6 | 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 |
| #4 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Winter | p.6 | 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 |
| #5 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | End GamE Goal and tiEbrEakErs | p.17 | 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 |
| #6 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Glossary | p.20 | 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)) | 300 |
| #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) | Wake-Up Chart | p.18 | 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)) | 296 |
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) | GamE board sEtup | p.4 | no quote on the wire |
| [2] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Spring | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 662 ms · first delta 7725 ms · total 8526 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 662 ms · ask 7841 ms · gateway work 8526 ms · total 8526 ms
- tokens in (the prompt the answerer read)
- 1939
- tokens out (what the answerer generated)
- 103
- tok/sec
- 138.1 tok/sec — 103 output tokens in 0.746 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 57s 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
- NOT_SETUP_SHAPED — no setup-shape pattern matched this question
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.