You asked
How does the game end, and how is the final score worked out?
Answered counted as answeredAsked with: Kingdom Builderbg-107529-en-1e
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live,vps
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 104 ms · ask 2817 ms · total 2923 ms
- single-flight (PR-5)
- queued 0 ms · generation 2923 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 3, "score": 0.032787, "snippet": "Put any game components not used in this game back into the game box. Players take their turns in clockwise direction, beginning with the start player. The game lasts for several rounds. Each player performs their turn the following way: The active player plays their terrain card face up in front of", "headingPath": "Setup · Sequence of play", "sharpsignalDocId": 663}, {"page": 5, "score": 0.032258, "snippet": "1. Exactly one settlement may be built on any one eligible terrain space. 2. Settlements may be built only on hexes of these terrain types: Grass, canyon, desert, flower field, and forest. Exception: If the rare case should occur that there is no eligible hex at the beginning of a player's turn or d", "headingPath": "Building rules - These rules apply to each single settlement (of three) built as mandatory action and as extra action · End of the game and final scoring", "sharpsignalDocId": 663}, {"page": 4, "score": 0.031746, "snippet": "During their turn, the player must build 3 settlements from their personal supply on unoccupied hexes of the same terrain type as their played card, strictly obeying the building rules (see page 4). In the course of the game players will collect location tiles. Location tiles grant extra actions and", "headingPath": "Mandatory action · Extra action · Location hex and location tile · Castle hex", "sharpsignalDocId": 663}, {"page": 2, "score": 0.03125, "snippet": "A game by Donald X. Vaccarino for 2 - 4 players aged 8 years and up 8 different game board sections Front: Landscape composed of 100 terrain hexes. Back: Gold score track for final evaluation. There are 9 different terrain types on each front side: 5 terrain types suitable for building Grass Canyon ", "headingPath": "Game components · Object of the game", "sharpsignalDocId": 663}, {"page": 1, "score": 0.030769, "snippet": "A game for 2 - 4 players aged 8 years and ups For your first game, we recommend our suggested setup on page 8 of these rules. 1", "headingPath": "", "sharpsignalDocId": 663}, {"page": 3, "score": 0.030303, "snippet": "3 2. Summary of location tiles 5. Kingdom Builder cards 4. Terrain cards 1. Game board pieces 1. Select any 4 of the 8 game board sections and assemble them to a rectangular game board as shown in the example below. 2. Place four summaries of location tiles next to the game board pieces matching the", "headingPath": "", "sharpsignalDocId": 663}, {"page": 6, "score": 0.029851, "snippet": "1 gold Note - Extra harbor action: The 'Fishermen' card does not generate gold for settlements on water hexes. 4 gold 0 gold 4 gold 1 gold Note: Settlement area = cluster of adjacent settlements belonging to one player. Note: Settlement area = cluster of adjacent settlements belonging to one player.", "headingPath": "Kingdom Builder cards · 1 gold · 0 gold · Horizontal line · Separate Evaluation for each player:", "sharpsignalDocId": 663}, {"page": 7, "score": 0.029412, "snippet": "Oracle Build one settlement on a hex of the same terrain type as your played terrain card. Build adjacent if possible. Farm Build one settlement on a grass hex. Build adjacent if possible. Skip this action if there is not a single unoccupied grass hex on the game board. Build one settlement on a des", "headingPath": "Extra action: Build one additional settlement from your personal supply. · Oasis · Barn · Paddock", "sharpsignalDocId": 663}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 5, "quote": null, "headingPath": "Building rules - These rules apply to each single settlement (of three) built as mandatory action and as extra action · End of the game and final scoring", "sharpsignalDocId": 663}, {"page": 4, "quote": null, "headingPath": "Mandatory action · Extra action · Location hex and location tile · Castle hex", "sharpsignalDocId": 663}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 663 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 663 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)
- answer fence
- passed — letter density 0.93704 of 683 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row retained until
- Nov 13, 2026 12:16
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. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.
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 Kingdom Builder — Rulebook (corpus doc 663) | Setup · Sequence of play | 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 Kingdom Builder — Rulebook (corpus doc 663) | Building rules - These rules apply to each single settlement (of three) built as mandatory action and as extra action · End of the game and final scoring | p.5 | 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 Kingdom Builder — Rulebook (corpus doc 663) | Mandatory action · Extra action · Location hex and location tile · Castle hex | p.4 | 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 Kingdom Builder — Rulebook (corpus doc 663) | Game components · Object of the game | p.2 | 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 Kingdom Builder — Rulebook (corpus doc 663) | p.1 | 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)) | 127 | |
| #6 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | p.3 | 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 Kingdom Builder — Rulebook (corpus doc 663) | Kingdom Builder cards · 1 gold · 0 gold · Horizontal line · Separate Evaluation for each player: | 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 Kingdom Builder — Rulebook (corpus doc 663) | Extra action: Build one additional settlement from your personal supply. · Oasis · Barn · Paddock | p.7 | 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.
candidate pool: the answering read scored 9 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.
floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.
arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.
| read at | document | heading | page | fused rank | fused RRF score | carried by | how it got its slot |
|---|---|---|---|---|---|---|---|
| #1 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Building rules - These rules apply to each single settlement (of three) built as mandatory action and as extra action · End of the game and final scoring | p.5 | #2 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #2 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Setup · Sequence of play | p.3 | #1 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #3 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | p.1 | #5 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it | |
| #4 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Extra action: Build one additional settlement from your personal supply. · Oasis · Barn · Paddock | p.7 | #8 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #5 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Suggested set-up for your first game · Some hints for your first settlements | p.8 | #9 | 0.014493 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one)) | vector | the re-ranker chose it |
| #6 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Mandatory action · Extra action · Location hex and location tile · Castle hex | p.4 | #3 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
| #7 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | p.3 | #6 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it | |
| #8 | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Game components · Object of the game | p.2 | #4 | 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)) | vector + the doc-priority boost arm | the re-ranker chose it |
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 Kingdom Builder — Rulebook (corpus doc 663) | Building rules - These rules apply to each single settlement (of three) built as mandatory action and as extra action · End of the game and final scoring | p.5 | no quote on the wire |
| [2] | RULEBOOK Kingdom Builder — Rulebook (corpus doc 663) | Mandatory action · Extra action · Location hex and location tile · Castle hex | p.4 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 104 ms · first delta 1490 ms · total 2923 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 104 ms · ask 2817 ms · gateway work 2923 ms · total 2923 ms
- tokens in (the prompt the answerer read)
- 2765
- tokens out (what the answerer generated)
- 193
- tok/sec
- 137.9 tok/sec — 193 output tokens in 1.400 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 6s 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 596), 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.