You asked
Before anyone takes a turn, how is everything laid out on the table?
Answered counted as answeredAsked with: Life of the Amazoniabg-368305-en-1e
🔧 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 11359 ms · total 11596 ms
- single-flight (PR-5)
- queued 0 ms · generation 11596 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 6, "score": 0.032787, "snippet": "Players take turns in a clockwise direction until the 'End of the Game' conditions are met (see page 14). Each turn consists of an Action Phase and Clean-up Phase. Action Phase (See page 7~13): Pay the required amount of Resource Tokens to perfom the desired Actions. There are a total of 8 Actions t", "headingPath": "GAME STRUCTURE", "sharpsignalDocId": 515}, {"page": 14, "score": 0.032258, "snippet": "If a Player has no more Actions they would like to perform, or no Actions they can perform, the Player then ends the Action Phase and begins the Clean-up Phase in the following order. Store unused Resource Tokens in the Play Area. 1 If all the tokens in the Play Area are not used or cannot be used i", "headingPath": "CALCULATING YOUR SCORE", "sharpsignalDocId": 515}, {"page": 15, "score": 0.031746, "snippet": "A Grouping is a combination of specific Lives placed in certain formations as indicated by the card. Some Base Animals provide points based on the shape of the Grouping. Groupings on Animal Cards are represented with Green Colored borders. The shape of a Grouping refers to the line connecting the ed", "headingPath": "GROUPING", "sharpsignalDocId": 515}, {"page": 19, "score": 0.03125, "snippet": "When the Player Marker placed on the Automa Card reaches its last space (marked with a bell shape), the game ends immediately and no additional turns follow. Unlike a 2~4 player game, the Solo mode does not end when 5 Base Animal Cards are depleted. Also, the additionally awarded 5 points for the Pl", "headingPath": "END OF THE GAME", "sharpsignalDocId": 515}, {"page": 22, "score": 0.030769, "snippet": "The direction of the Macaw and the order of the Lives placed do not matter. The Grouping must consist of 1 Macaw with Plant(s). Therefore, a Grouping can consist of a Macaw and Trees or a Macaw and Flowers, or all 3. Groupings , , and are all recognized as the 3rd shape and collect 10 points each. a", "headingPath": "MACAW B", "sharpsignalDocId": 515}, {"page": 5, "score": 0.030303, "snippet": "q As the game progresses, additional Terrain Tiles will connect to the Starting Terrain Tile. Therefore, make sure each Player has plenty of space to spread out. Resource Bag: Each Player chooses a color, takes a Resource Bag and places it in front of them. All Players start the game with 10 Resourc", "headingPath": "I. INTRODUCTION I. INTRODUCTION", "sharpsignalDocId": 515}, {"page": 27, "score": 0.029851, "snippet": "Flora: Score points based on the number of Flowers placed in the Jungle. The example will collect no points for this card as there are only 2 Flowers.", "headingPath": "V. APPENDIX V. APPENDIX", "sharpsignalDocId": 515}, {"page": 19, "score": 0.029412, "snippet": "2 Discard the Nature Card that corresponds to the depiction on the back of the Automa Token. When discarding a card, the card indicated by the Automa Token is chosen by the place in line the card stands when counting from the left. In this example, discard the Scenery Card that is 2nd in line from t", "headingPath": "IV. VARIANT MODES IV. VARIANT MODES", "sharpsignalDocId": 515}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 5, "quote": null, "headingPath": "I. INTRODUCTION I. INTRODUCTION", "sharpsignalDocId": 515}, {"page": 5, "quote": null, "headingPath": "I. INTRODUCTION I. INTRODUCTION", "sharpsignalDocId": 515}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 515 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 515 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 06:02
retrieval — what the passage search returned
what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.
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 Life of the Amazonia — Rulebook (corpus doc 515) | GAME STRUCTURE | p.6 | 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 Life of the Amazonia — Rulebook (corpus doc 515) | CALCULATING YOUR SCORE | p.14 | 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 Life of the Amazonia — Rulebook (corpus doc 515) | GROUPING | p.15 | 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 Life of the Amazonia — Rulebook (corpus doc 515) | END OF THE GAME | p.19 | 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 Life of the Amazonia — Rulebook (corpus doc 515) | MACAW B | p.22 | 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 Life of the Amazonia — Rulebook (corpus doc 515) | I. INTRODUCTION I. INTRODUCTION | 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 Life of the Amazonia — Rulebook (corpus doc 515) | V. APPENDIX V. APPENDIX | p.27 | 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)) | 150 |
| #8 | RULEBOOK Life of the Amazonia — Rulebook (corpus doc 515) | IV. VARIANT MODES IV. VARIANT MODES | p.19 | 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 |
what the answerer read — the passages it actually had in front of it
what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.
the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.
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 Life of the Amazonia — Rulebook (corpus doc 515) | I. INTRODUCTION I. INTRODUCTION | p.5 | no quote on the wire |
| [2] | RULEBOOK Life of the Amazonia — Rulebook (corpus doc 515) | I. INTRODUCTION I. INTRODUCTION | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 226 ms · first delta 8707 ms · total 11596 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 11359 ms · gateway work 11596 ms · total 11596 ms
- tokens in (the prompt the answerer read)
- 4245
- tokens out (what the answerer generated)
- 386
- tok/sec
- 136.2 tok/sec — 386 output tokens in 2.835 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 45s 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
- NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
- pattern that matched
- BEFORE_FIRST_PLAY — "before the first turn" / "before we begin"
- matched words (in the normalized question)
-
before anyone
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 447), 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.