You asked
When does the game end?
Answered counted as answeredThe game ends in the following ways: 1. At the end of the 7th year [1][2]. 2. When any player reaches or exceeds 20 victory points, the game finishes at the end of the current year (after year-end steps) [3][4][5].
🔧 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 200 ms · ask 7047 ms · total 7255 ms
- single-flight (PR-5)
- queued 0 ms · generation 7255 ms
- retrieval refs (raw)
- [{"page": 18, "score": 0.032787, "snippet": "The game ends at the end of the 7th year. You win if your VP marker is ahead of the Automa VP marker. If they're on the same space, the game is a draw, and if the Automa is ahead, you lose.", "headingPath": "GamE End & WinninG/ losinG", "sharpsignalDocId": 90}, {"page": 6, "score": 0.031754, "snippet": "Players age their grape and wine tokens, return workers to their vineyard mats, collect residual payments, remove rooster tokens from the wake-up chart, and rotate the first-player token counterclockwise. When any player reaches or exceeds 20 victory points, the game will finish at the end of the cu", "headingPath": "Year End", "sharpsignalDocId": 90}, {"page": 18, "score": 0.031498, "snippet": "Have more victory points (VPs) than the Automa at the end of the game, which consists of 7 years.", "headingPath": "Goal", "sharpsignalDocId": 90}, {"page": 17, "score": 0.031258, "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": 19, "score": 0.029644, "snippet": "If you want to add tenseness to the game you can let the Automa score victory points each year, and if you're not ahead of it at the end of a year, you lose immediately. This \"aggressive variant\" can be played at easy, normal, and hard difficulty levels. At the beginning of each year place the Autom", "headingPath": "aGGrEssiVE Variant", "sharpsignalDocId": 90}, {"page": 19, "score": 0.029462, "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": 16, "score": 0.027864, "snippet": "Players keep track of residual payments from wine orders on the residual payment tracker. All players begin the game with their wine bottle tokens on the lira symbol in the middle of the residual payment tracker. When a player fills a wine order, that player moves their residual token up on the trac", "headingPath": "rEsidual paymEnts", "sharpsignalDocId": 90}, {"page": 8, "score": 0.026553, "snippet": "Spring Choose wake-up positions Summer Worker Placement 2 players 3-4 players 5-6 players Produces a 1-value red grape Fall Draw 1 Visitor card Winter Worker Placement 2 players 3-4 players 5-6 players Collect residual payments Discard down to 7 cards Summertime in the game is the time to build your", "headingPath": "summEr actions", "sharpsignalDocId": 90}]
- citations (raw)
- [{"page": 18, "quote": null, "headingPath": "GamE End & WinninG/ losinG", "sharpsignalDocId": 90}, {"page": 18, "quote": null, "headingPath": "Goal", "sharpsignalDocId": 90}, {"page": 17, "quote": null, "headingPath": "End GamE Goal and tiEbrEakErs", "sharpsignalDocId": 90}, {"page": 1, "quote": null, "headingPath": "Goal", "sharpsignalDocId": 90}, {"page": 6, "quote": null, "headingPath": "Year End", "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 30, 2026 02:51
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) | GamE End & WinninG/ losinG | p.18 | 0.032787 (at the 2-arm ceiling (0.03279) — the top of a 2-arm fuse; whether more arms ran here was never recorded) | 189 |
| #2 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Year End | p.6 | 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) | Goal | p.18 | 0.031498 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 97 |
| #4 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | End GamE Goal and tiEbrEakErs | p.17 | 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) | aGGrEssiVE Variant | p.19 | 0.029644 (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) | campaiGn play | p.19 | 0.029462 (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) | rEsidual paymEnts | p.16 | 0.027864 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #8 | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | summEr actions | p.8 | 0.026553 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; 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) | GamE End & WinninG/ losinG | p.18 | no quote on the wire |
| [2] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Goal | p.18 | no quote on the wire |
| [3] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | End GamE Goal and tiEbrEakErs | p.17 | no quote on the wire |
| [4] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Goal | p.1 | no quote on the wire |
| [5] | RULEBOOK Viticulture Essential Edition — Rulebook (corpus doc 90) | Year End | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 200 ms · first delta n/a · total 7255 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 200 ms · ask 7047 ms · gateway work 7255 ms · total 7255 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 30s 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
- 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.