You asked
Before anyone takes a turn, how is everything laid out on the table?
Answered counted as answeredAsked with: Akropolisbg-357563-en-1e
1. Take the City tiles that correspond to the number of players [1]. 2. Create 11 equal stacks of tiles, placed face down [1]. 3. Place the rest of the tiles face up in the center of the table, forming a line called the 'Construction Site' [2]. 4. Each player (Architect) takes a starting tile and places it in front of them [2]. 5. The Architect who most recently climbed a hill takes the Chief Architect marker [2]. 6. Working around clockwise from the first player, each Architect takes a specific number of Stones: 1st player (2), 2nd player (2), 3rd player (2), or 4th player (2) [2]. 7. Place the remaining Stones nearby [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 297 ms · ask 3589 ms · total 3896 ms
- single-flight (PR-5)
- queued 0 ms · generation 3896 ms
- retrieval refs (raw)
- [{"page": 3, "score": 0.032787, "snippet": "Place the rest of the tiles face up in the center of the table, forming a line . This line of tiles will be called the 'Construction Site' from now on. 2 Each player, known as an Architect, takes a starting tile and places it in front of them . 3 The Architect who most recently climbed a hill takes ", "headingPath": "", "sharpsignalDocId": 476}, {"page": 4, "score": 0.032258, "snippet": "Play continues in a clockwise direction, starting with the Chief Architect. The Architects take turns until there is only one City tile left in the Construction Site (see: Supplying the Construction Site , p.7). Important: The last tile in the Construction Site is not played. Starting with the Chief", "headingPath": "PLAYING THE GAME", "sharpsignalDocId": 476}, {"page": 2, "score": 0.031746, "snippet": "· 61 City tiles 1 scorepad 4 starting tiles 4 Player aids 40 Stone cubes Take the City tiles that correspond to the number of players (refer to the backs of the tiles). Create 11 equal stacks of tiles, placed face down (see on the right). 1 4 players 2+ / 3+ / 4 3 players 2+ / 3+ 2 players 2+ Note: ", "headingPath": "", "sharpsignalDocId": 476}, {"page": 8, "score": 0.03125, "snippet": "IIf you wish to increase the difficulty level, you can play the variants below. The setup and gameplay remain unchanged. Each variant adds an additional placement condition to a type of District. If your District meets this additional condition, its points are doubled; if it does not, then it scores", "headingPath": "VARIANTS", "sharpsignalDocId": 476}, {"page": 7, "score": 0.030769, "snippet": "When there is only one tile left in the Construction Site, complete the following steps: Place the remaining tile in the first position, then take one stack of tiles and place the tiles face up next to each other, to replenish the Construction Site. · The Chief Architect marker passes to the player ", "headingPath": "supplying The consTrucTion siTe · End of the game · C alculaTing vicTory poinTs", "sharpsignalDocId": 476}, {"page": 5, "score": 0.030303, "snippet": "The selected tile must be added to your City. You can place it either on the 1st level or a higher level. A tile placed on the 1st level must border another of your City tiles along at least one edge. A tile placed on a higher level must be constructed on top of 3 hexes (it cannot be placed above an", "headingPath": "add The Tile To Their ciTy · Quarries · Plazas", "sharpsignalDocId": 476}, {"page": 6, "score": 0.029851, "snippet": "There are 5 different types of District. A District can be constructed freely but to gain points, each one must meet two conditions : The placement condition for its type; At least one Plaza of that color in your City (see: Plazas , p. 5). The citizens of your city like to live together in one large", "headingPath": "Plazas · Houses · Markets · Barracks · Temples · Gardens · …", "sharpsignalDocId": 476}, {"page": 1, "score": 0.029412, "snippet": "At the heart of the Mediterranean, rival cities seek wealth and glory. The most talented architects in ancient Greece stand ready to achieve this goal. Build housing, temples, markets, gardens and barracks, so you can grow your city and ensure it triumphs over the others. Raise its prestige with har", "headingPath": "", "sharpsignalDocId": 476}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "", "sharpsignalDocId": 476}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 476}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 476 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 476 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 7, 2026 05:52
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 Akropolis — Rulebook (corpus doc 476) | p.3 | 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)) | 300 | |
| #2 | RULEBOOK Akropolis — Rulebook (corpus doc 476) | PLAYING THE GAME | p.4 | 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 Akropolis — Rulebook (corpus doc 476) | p.2 | 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 Akropolis — Rulebook (corpus doc 476) | VARIANTS | p.8 | 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 Akropolis — Rulebook (corpus doc 476) | supplying The consTrucTion siTe · End of the game · C alculaTing vicTory poinTs | p.7 | 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 Akropolis — Rulebook (corpus doc 476) | add The Tile To Their ciTy · Quarries · Plazas | p.5 | 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 Akropolis — Rulebook (corpus doc 476) | Plazas · Houses · Markets · Barracks · Temples · Gardens · … | p.6 | 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 Akropolis — Rulebook (corpus doc 476) | p.1 | 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)) | 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 Akropolis — Rulebook (corpus doc 476) | p.2 | no quote on the wire | |
| [2] | RULEBOOK Akropolis — Rulebook (corpus doc 476) | p.3 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 297 ms · first delta 2680 ms · total 3896 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 297 ms · ask 3589 ms · gateway work 3896 ms · total 3896 ms
- tokens in (the prompt the answerer read)
- 2466
- tokens out (what the answerer generated)
- 169
- tok/sec
- 147.5 tok/sec — 169 output tokens in 1.146 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 51s 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 407), 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.