You asked
When does the game end?
Answered counted as answeredAsked with: Azulbg-230802-en-1e
The game ends right after the Wall-tiling phase in which at least one player has completed at least one horizontal line of 5 consecutive tiles on her wall [1]. The game also ends after the round in which at least one player has completed a horizontal line of 5 consecutive tiles on her wall [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 206 ms · ask 2866 ms · total 3081 ms
- single-flight (PR-5)
- queued 0 ms · generation 3081 ms
- retrieval refs (raw)
- [{"page": 6, "score": 0.04918, "snippet": "The game ends right after the Wall-tiling phase in which at least one player has completed at least one horizontal line of 5 consecutive tiles on her wall. Once the game has ended, score additional points if you have achieved the following goals: · Gain 2 points for each complete horizontal line of ", "headingPath": "End of the game", "sharpsignalDocId": 95}, {"page": 3, "score": 0.048387, "snippet": "To be the player with the most points at the end of the game. The game ends after the round in which at least one player has completed a horizontal line of 5 consecutive tiles on her wall.", "headingPath": "Object of the game", "sharpsignalDocId": 95}, {"page": 5, "score": 0.047619, "snippet": "If nobody has completed a horizontal line of 5 consecutive tiles on her wall yet (see End of the game), prepare the next round. The player with the starting player marker refills each of the Factory displays with 4 tiles from the bag as in the setup. If the bag is empty, refill it with all the tiles", "headingPath": "C. Preparing the next round", "sharpsignalDocId": 95}, {"page": 4, "score": 0.046394, "snippet": "Any tiles you have picked that you cannot or do not want to place according to the rules, you must place in your floor line , filling its spaces from left to right . These tiles are considered as having fallen on the floor and give minus points in the Wall-tiling phase. If all spaces of your floor l", "headingPath": "Floor line", "sharpsignalDocId": 95}, {"page": 3, "score": 0.03125, "snippet": "The game is played over multiple rounds, each of which is composed of three phases: Factory offer Wall-tiling Preparing the next round", "headingPath": "Gameplay", "sharpsignalDocId": 95}, {"page": 4, "score": 0.030303, "snippet": "This phase can be carried out by all players simultaneously, as they move tiles from their complete pattern lines over to their walls. Go through your pattern lines from top to bottom . Move the rightmost tile of each complete line to the space of the same color in the corresponding line of your wal", "headingPath": "B. Wall-tiling", "sharpsignalDocId": 95}, {"page": 2, "score": 0.029851, "snippet": "Give each player a player board (A) . Flip your board to the side with the colored wall. (See Variant Play to play with the gray side of the player board). Each player must use the same side. Take 1 scoring marker (B) and place it on space '0' of your score track. Place the Factory displays (C) in a", "headingPath": "Game Setup", "sharpsignalDocId": 95}, {"page": 5, "score": 0.029469, "snippet": "Each tile you move over to your wall is always placed on the space matching its color and immediately scores as follows: If there are no tiles directly adjacent (vertically or horizontally) to the newly placed tile, gain 1 point on the score track. If there are any tiles adjacent, however, do the fo", "headingPath": "Scoring", "sharpsignalDocId": 95}]
- citations (raw)
- [{"page": 6, "quote": null, "headingPath": "End of the game", "sharpsignalDocId": 95}, {"page": 3, "quote": null, "headingPath": "Object of the game", "sharpsignalDocId": 95}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 95 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 95 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 05:51
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 Azul — Rulebook (corpus doc 95) | End of the game | p.6 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | 300 |
| #2 | RULEBOOK Azul — Rulebook (corpus doc 95) | Object of the game | p.3 | 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)) | 188 |
| #3 | RULEBOOK Azul — Rulebook (corpus doc 95) | C. Preparing the next round | p.5 | 0.047619 (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 Azul — Rulebook (corpus doc 95) | Floor line | p.4 | 0.046394 (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 Azul — Rulebook (corpus doc 95) | Gameplay | p.3 | 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)) | 134 |
| #6 | RULEBOOK Azul — Rulebook (corpus doc 95) | B. Wall-tiling | p.4 | 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 Azul — Rulebook (corpus doc 95) | Game Setup | p.2 | 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 Azul — Rulebook (corpus doc 95) | Scoring | p.5 | 0.029469 (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 |
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 Azul — Rulebook (corpus doc 95) | End of the game | p.6 | no quote on the wire |
| [2] | RULEBOOK Azul — Rulebook (corpus doc 95) | Object of the game | p.3 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 206 ms · first delta 2568 ms · total 3081 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 206 ms · ask 2866 ms · gateway work 3081 ms · total 3081 ms
- tokens in (the prompt the answerer read)
- 1542
- tokens out (what the answerer generated)
- 65
- tok/sec
- 140.7 tok/sec — 65 output tokens in 0.462 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 52s 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 26), 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.