You asked
How do I take my turn?
Answered counted as answeredOn your turn, you must pick tiles in one of the following ways: 1. Pick all tiles of the same color from any one Factory display and then move the remaining tiles from this Factory display to the center of the table [1]. 2. OR Pick all tiles of the same color from the center of the table [1]. If you are the first player in the round to pick tiles from the center of the table, you also take the starting player marker and place it onto the leftmost free space of your floor line [1]. After picking tiles, you must: 1. Add the tiles you picked to one of the 5 pattern lines on your player board [1]. 2. Place the tiles, one by one, from right to left in your chosen pattern line [1]. 3. If the pattern line already holds tiles, you may only add tiles of the same color to it [1]. (In later rounds, you are not allowed to place tiles of a certain color in a pattern line whose corresponding line of your wall already holds a tile of that color [2]). 4. If you have picked up more tiles than you can place in your chosen pattern line, you must place the excess tiles in your floor line [1]. 5. When placing tiles in your floor line, fill its spaces from left to right [3].
🔧 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 226 ms · ask 4762 ms · total 4999 ms
- single-flight (PR-5)
- queued 0 ms · generation 4999 ms
- retrieval refs (raw)
- [{"page": 3, "score": 0.032522, "snippet": "The starting player places the starting player marker in the center of the table and then takes the first turn. Play then continues clockwise. On your turn, you must pick tiles in one of the following ways: EITHER Pick all tiles of the same color from any one Factory display and then move the remain", "headingPath": "A. Factory offer", "sharpsignalDocId": 95}, {"page": 3, "score": 0.032522, "snippet": "On his turn, Peter picks the 2 black tiles from a Factory display and places the remaining tiles in the center of the table. Martin picks the yellow tile from a Factory display and places the remaining 3 red tiles in the center of the table. Then, Andrea picks these 3 red tiles from the center of th", "headingPath": "First turns example", "sharpsignalDocId": 95}, {"page": 5, "score": 0.015873, "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.015625, "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": 4, "score": 0.015385, "snippet": "In all later rounds, you must also comply with the following rule: You are not allowed to place tiles of a certain color in a pattern line whose corresponding line of your wall already holds a tile of that color.", "headingPath": "First turns example", "sharpsignalDocId": 95}, {"page": 3, "score": 0.015152, "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": 5, "score": 0.014925, "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}, {"page": 4, "score": 0.014706, "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}]
- citations (raw)
- [{"page": 3, "quote": null, "headingPath": "A. Factory offer", "sharpsignalDocId": 95}, {"page": 4, "quote": null, "headingPath": "First turns example", "sharpsignalDocId": 95}, {"page": 4, "quote": null, "headingPath": "Floor line", "sharpsignalDocId": 95}]
- 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 31, 2026 02:24
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 Azul — Rulebook (corpus doc 95) | A. Factory offer | p.3 | 0.032522 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #2 | RULEBOOK Azul — Rulebook (corpus doc 95) | First turns example | p.3 | 0.032522 (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 Azul — Rulebook (corpus doc 95) | C. Preparing the next round | p.5 | 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 Azul — Rulebook (corpus doc 95) | B. Wall-tiling | p.4 | 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 Azul — Rulebook (corpus doc 95) | First turns example | p.4 | 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) | 212 |
| #6 | RULEBOOK Azul — Rulebook (corpus doc 95) | Gameplay | p.3 | 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) | 134 |
| #7 | RULEBOOK Azul — Rulebook (corpus doc 95) | Scoring | p.5 | 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 Azul — Rulebook (corpus doc 95) | Floor line | 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 Azul — Rulebook (corpus doc 95) | A. Factory offer | p.3 | no quote on the wire |
| [2] | RULEBOOK Azul — Rulebook (corpus doc 95) | First turns example | p.4 | no quote on the wire |
| [3] | RULEBOOK Azul — Rulebook (corpus doc 95) | Floor line | p.4 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 226 ms · first delta n/a · total 4999 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 226 ms · ask 4762 ms · gateway work 4999 ms · total 4999 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 16s 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 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.