You asked
How do I setup the game?
Answered counted as answered1. Each player chooses a player board in one player color and places it in front of them, face up with the colored stars side [1]. 2. Place the Factory displays in a circle around the center of the table (5 for 2-player, 7 for 3-player, or 9 for 4-player) [1]. 3. Place the scoring board next to the Factory displays [1]. 4. Put the round counter on the space for round 1 [1]. 5. Each player takes a scoring marker in their color and places it on the 5th space of the scoring track [1]. 6. Fill the bag with 132 tiles [1]. 7. Draw 10 tiles blindly from the bag and lay them out at random on the supply spaces shown in the center of the scoring board [1]. 8. Fill each Factory display with exactly 4 tiles drawn randomly from the bag [1]. 9. Put the bag aside [1]. 10. Place the start player token in the center of the table [1]. 11. Place the tower between the Factory displays and the scoring board [1]. 12. Put the point tokens aside [1].
🔧 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 235 ms · ask 5095 ms · total 5339 ms
- single-flight (PR-5)
- queued 0 ms · generation 5339 ms
- retrieval refs (raw)
- [{"page": 1, "score": 0.016393, "snippet": "The starting player begins. When it's your turn, first check that you have the right number of tiles in the needed color next to your player board to play in a space. If you have enough tiles, then place exactly one of these tiles on to the corresponding space of your player board. Discard the other", "headingPath": "Phase 2: Playing and Scoring Tiles", "sharpsignalDocId": 97}, {"page": 2, "score": 0.016129, "snippet": "This task is performed by the start player. If you have not yet reached round 6, advance the round counter on to the next round, in which you will start. If you are already in round 6, then move directly to the end of the game ( see next page ). Fill up the Factory displays with exactly 4 new tiles ", "headingPath": "Phase 3: Preparation for the Next Round", "sharpsignalDocId": 97}, {"page": 1, "score": 0.015873, "snippet": "A Each player chooses a player board (A) in one player color (as indicated by the colored circle between the red and orange stars) and places it in front of them, so that the side with the colored stars is face up. Place the Factory displays (B) in a circle around the center of the table: In a 2-pla", "headingPath": "GAME SETUP", "sharpsignalDocId": 97}, {"page": 1, "score": 0.015625, "snippet": "The player who has the start player token will be the first player to place their tiles on their board in Phase 2; and they will start the following round. This gives them the advantage of choosing tiles from the Factory displays first, according to the normal rules. After placing the tiles you have", "headingPath": "The start player token", "sharpsignalDocId": 97}, {"page": 1, "score": 0.015385, "snippet": "On your turn, you must pick tiles. To do so you have two choices: OR Pick all tiles of the same color, which is not the wild color this round, from any one Factory display and place them next to your player board. Move the remaining tiles from this Factory display to the center of the table. Pick al", "headingPath": "Phase 1: Acquire Tiles", "sharpsignalDocId": 97}, {"page": 1, "score": 0.015152, "snippet": "You may only place tiles from those which are next to your own player board. Tiles may only be placed on the diamond-shaped spaces on your player board. Do not place tiles on pillars, statues or windows. You may only place tiles on empty spaces. The spaces are arranged in a star shape. The color of ", "headingPath": "Rules for Placement of Tiles:", "sharpsignalDocId": 97}, {"page": 1, "score": 0.014925, "snippet": "For each tile that you place on your player board, you receive one point. Move your scoring marker one space forward on the scoring track. If you place a tile next to one or more connected tiles , you receive one point for each of these tiles ( see examples B-E on page 5 ). Only spaces that are next", "headingPath": "Scoring", "sharpsignalDocId": 97}, {"page": 2, "score": 0.014706, "snippet": "If you do not wish to or cannot place tiles on your turn, you must pass. You may choose up to 4 tiles from those next to your player board to keep into the next round. Place these on the four spaces in the corners of your player board. They do not score points. Any other tiles you have left must be ", "headingPath": "Passing", "sharpsignalDocId": 97}]
- citations (raw)
- [{"page": 1, "quote": null, "headingPath": "GAME SETUP", "sharpsignalDocId": 97}]
- 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 23, 2026 20:47
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: Summer Pavilion — Rulebook (corpus doc 97) | Phase 2: Playing and Scoring Tiles | p.1 | 0.016393 (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: Summer Pavilion — Rulebook (corpus doc 97) | Phase 3: Preparation for the Next Round | p.2 | 0.016129 (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: Summer Pavilion — Rulebook (corpus doc 97) | GAME SETUP | p.1 | 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: Summer Pavilion — Rulebook (corpus doc 97) | The start player token | p.1 | 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: Summer Pavilion — Rulebook (corpus doc 97) | Phase 1: Acquire Tiles | p.1 | 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) | 300 |
| #6 | RULEBOOK Azul: Summer Pavilion — Rulebook (corpus doc 97) | Rules for Placement of Tiles: | p.1 | 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) | 300 |
| #7 | RULEBOOK Azul: Summer Pavilion — Rulebook (corpus doc 97) | Scoring | p.1 | 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: Summer Pavilion — Rulebook (corpus doc 97) | Passing | p.2 | 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: Summer Pavilion — Rulebook (corpus doc 97) | GAME SETUP | p.1 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 235 ms · first delta n/a · total 5339 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 235 ms · ask 5095 ms · gateway work 5339 ms · total 5339 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 40s 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
- 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
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 28), 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.