You asked
How do I place an adornment on the river?
Abstained — no grounded answer; closest passages below counted as honest abstain 0 of 3 books answeredAsked with: Catanbg-13-en-1e · Catan: Cities & Knightsbg-926-en-1e · Catan: Seafarersbg-325-en-1e
Read together first; no grounded answer, so each book was read on its own.
Catanbg-13-en-1e Abstained — no grounded answer; closest passages below
The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.
Assemble the frame as outlined on pages 2-3. Note: If you want to vary relative harbor locations slightly, just shuffle the order of the frame pieces and do not place the random harbor pieces as outlined below in point 2. Turn the terrain hexes face down. Shuffle the terrain hexes. Randomly place th
Now take the 9 harbor pieces (the small 5-sided pieces with ships on them) and randomly place one on top of each harbor on the frame. See Illustration P .
clockwise toward the center. Skip the desert. Important: Alternatively, you can use a fully random set-up. Place 1 token on each land hex. Start at one corner of the island, and place the number tokens in random order. In such case, the tokens with the red numbers must not be next to each other. You
Place the 18 number tokens as shown in Illustration Q: Sort the number tokens beside the board, letter side face up. Place 1 token on each land hex. Start at a corner of the island. Place the number tokens on the terrain hexes in alphabetical order, proceeding counter-
When a terrain hex borders on the sea (i.e., a frame piece), it is called a 'coast.' You can build a road along a coast. You can build settlements and upgrade settlements to cities on intersections that border on the sea. However, since a site on the coast borders only 1 or 2 terrain hexes, coastal
The answerer's own words:
I don't have enough information.
2 books had nothing to add — expansion rulebooks only speak where they change the rules. show them
Catan: Cities & Knightsbg-926-en-1e Abstained — no grounded answer; closest passages below
Catan: Cities & Knights has nothing to add here — an expansion's rulebook only speaks where it changes the game, so silence on a base-game question is the book working, not failing.
The answerer's own words:
I don't have enough information.
Catan: Seafarersbg-325-en-1e Abstained — no grounded answer; closest passages below
Catan: Seafarers has nothing to add here — an expansion's rulebook only speaks where it changes the game, so silence on a base-game question is the book working, not failing.
The answerer's own words:
I don't have enough information.
Strategy guides → — community tips, kept separate from rulings
🔧 debug — where this ruling came from
- outcome
- ABSTAINED — Abstained — no grounded answer; closest passages below
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search null ms · ask null ms · total 34253 ms
- single-flight (PR-5)
- queued 0 ms · generation 34253 ms
- retrieval refs (raw)
- citations (raw)
- boost provenance — errata + base rulebook (E2/E3)
- gate not evaluated for this ruling (boost, supersedence, and wrench all off at ask time), and the base-rulebook arm went unrecorded for the same reason — the wrench that would have stored it was off; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
- layering — route
- layered — the books were read together first and that read did not answer, so each book was then read on its own
- layering — how this ask was counted
- counted as ABSTAINED — carried by layer 1 (Catan); layer 2 ABSTAINED, layer 3 ABSTAINED; 0 not read; rung: ANSWERED ▸ ABSTAINED ▸ UNATTRIBUTABLE ▸ REFUSED
- layering — books not run
- layer valve: rulesage.table.max-layers = 8 (today's setting, not necessarily the one this ask ran under). A book the valve trims is not read and leaves NO row of its own, so it cannot be listed above or counted in the census — an empty list here means the corpus breaker marked nobody, not that nothing was left out.
- layering — the pooled probe
- ABSTAINED — queued 0 ms · search 297 ms · ask 11910 ms · first delta 12080 ms · gateway work 12216 ms · refs 8
- layering — queued between books
- queued between layers: 0 ms of the 0 ms total queue wait (every wait after the first is a mid-ask wait, because the generation permit is released and re-taken for each book)
- answered-before recall
-
no past answered ruling for this game matched closely enough
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 3, 2026 20:51
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.
no payload was recorded for this ruling (the call never returned one)
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.
no payload was recorded for this ruling (the call never returned one)
generation — timing and the path taken
- timing split
- retrieval n/a · first delta n/a · total 34253 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 n/a ms · ask n/a ms · gateway work 34253 ms · total 34253 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 25s ago)
- stream path
- not requested — no progress token attached (stream-answers off, or a non-streaming caller)
- 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
- ABSTAINED — Abstained — no grounded answer; closest passages below
- abstain rationale
- the answerer offered no rationale text with this refusal (or the ruling predates the abstain_rationale column, V41)
setup-shape — why the checklist band did or didn't render
- decision
- NOT_SETUP_SHAPED — no setup-shape pattern matched this question
layers — one row per book this ask read
| # | book | outcome | timings | refs | cited | stream | arms | row |
|---|---|---|---|---|---|---|---|---|
| probe | every book, read together (bg-13-en-1e) | Abstained — no grounded answer; closest passages below | queued 0 ms · search 297 ms · ask 11910 ms · first delta 12080 ms · gateway work 12216 ms | 8 | 0 | STREAMED | base rulebook doc 43 boosted · no registered errata card matched · keyed on edition 1 | ruling 1583 |
| 1 | Catan (bg-13-en-1e) | Abstained — no grounded answer; closest passages below | queued 0 ms · search 257 ms · ask 7388 ms · first delta 7553 ms · gateway work 7653 ms | 8 | 0 | STREAMED | base rulebook doc 43 boosted · no registered errata card matched · keyed on edition 1 | ruling 1584 |
| 2 | Catan: Cities & Knights (bg-926-en-1e) | Abstained — no grounded answer; closest passages below | queued 0 ms · search 253 ms · ask 6325 ms · first delta 6456 ms · gateway work 6587 ms | 8 | 0 | STREAMED | no base-rulebook boost — this edition registers no ingested rulebook to anchor retrieval to · no registered errata card matched · keyed on edition 119 | ruling 1585 |
| 3 | Catan: Seafarers (bg-325-en-1e) | Abstained — no grounded answer; closest passages below | queued 0 ms · search 281 ms · ask 7507 ms · first delta 7661 ms · gateway work 7797 ms | 8 | 0 | STREAMED | no base-rulebook boost — this edition registers no ingested rulebook to anchor retrieval to · no registered errata card matched · keyed on edition 118 | ruling 1586 |
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 1), so "no registered errata card matched" above could never have matched one
Errata scope: each book this ask READ got its own errata gate, keyed on that book's own edition — so an expansion's registered cards were matched against that expansion's own layer rather than left outside the match. The per-layer table above shows what each one sent, and any book that was not read ran no gate at all.