You asked
How does building work?
Answered counted as answeredAsked with: Casinobg-18121-en-1e
Building involves a player using two cards from their hand to change the value of a card on the table [1]. Specifically, a player may have two cards in their hand where the lower card, if added to a card on the table, builds up its value to that of the higher card still in the player's hand [1][2]. Key rules regarding building include: * **Method:** To build or increase a build, a card must be played from the hand; cards already on the table cannot be used to increase a build [3][4][5]. * **Increasing Builds:** A player can increase an existing build by playing cards from their hand [3][4][5]. For example, if a player holds an Ace and a 10, they could increase a "9" build to a "10" build by putting the Ace on the existing cards and announcing the new total value [6][2]. To increase a build and later take it in, a player must have all the necessary cards in their hand to win both the original and the increased builds [6][2]. * **Double Builds:** When two cards of the same denomination or two builds of the same value are put together as one, they cannot be increased [3][4][6]. * **Interference:** Once a combination is announced and left on the table, it cannot be changed except by adding a card from a player's hand [3][4][7][5]. An opponent's build may be increased using cards from the hand only [8][5]. * **Partnerships:** In four-handed games, partners may make builds that can be won by a card declared in their partner's hand [8][5]. * **Obligations:** A player who makes a build is obligated to either win it on their next turn, win something else, or make another build [3][4][5].
🔧 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 243 ms · ask 7336 ms · total 79800 ms
- single-flight (PR-5)
- queued 72210 ms · generation 7590 ms
- retrieval refs (raw)
- [{"page": 4, "score": 0.032787, "snippet": "The simple rule to be remembered is that no combination of cards once announced, and left on the table, can be changed, except by the addition of a card from the hand of some player. Taking In. Any player who has made a build is obliged either to win it, when it is next his turn to play, or to win s", "headingPath": "", "sharpsignalDocId": 226}, {"page": 3, "score": 0.032258, "snippet": "Building. A player may have in his hand two cards, the lower of which, if added to a card on the table, would build up its value to that of the higher card still in the player's hand. For instance: A player holds a 9 and 2, and there is a 7 on the table. He may place the 2 on the 7, announcing the t", "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 4, "score": 0.031746, "snippet": "If any player can legitimately make or increase a build, all may do so, provided they have the proper cards. Double Builds. When two cards of the same denomination, or two builds of the same value are put together as one, they cannot be increased. For instance: A player holds 7 and 3, and there are ", "headingPath": "", "sharpsignalDocId": 226}, {"page": 3, "score": 0.03125, "snippet": "He cannot use the deuce on the table to increase the build from 5 to 7, nor the 4 to increase it to 9; because that would not be building from his hand; but if he held the 4 and 9 in his hand, he could build on the 5. The simple rule to be remembered is that no combination of cards once announced, a", "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 3, "score": 0.030769, "snippet": "Some players imagine that a player cannot increase his own build in this manner, even if he has both the cards for the first and last build; but there is no reason why a player should be denied a privilege which is freely granted to his adversary. If any player can legitimately make or increase a bu", "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 4, "score": 0.030303, "snippet": "Casino — Foster's Complete Hoyle (1914) 4 total value; “Nine,” which will notify other players that those two cards cannot be separated; but he cannot take them in until it again comes round to his turn to play, because he is allowed to play only one card at a time, and he has played his card in mak", "headingPath": "", "sharpsignalDocId": 226}, {"page": 5, "score": 0.029851, "snippet": "Casino — Foster's Complete Hoyle (1914) 5 opponent’s build may be increased by cards from the hand only. In the four-handed game, partners may take in one another’s builds, or may make builds which can be won by the card declared in the partner’s hand. For instance; One player builds an 8, and his p", "headingPath": "", "sharpsignalDocId": 226}, {"page": 3, "score": 0.029412, "snippet": "If the combination was his own build, it must be broken up; if an adversary's, it must be restored, and left as it was. If a player takes in a build with a wrong card, or takes in a wrong combination, or gathers cards to which he is not entitled, the error must be challenged and proved before the ne", "headingPath": "CASSINO.", "sharpsignalDocId": 226}]
- citations (raw)
- [{"page": 3, "quote": null, "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 3, "quote": null, "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 226}, {"page": 3, "quote": null, "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 3, "quote": null, "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 226}, {"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 226}, {"page": 5, "quote": null, "headingPath": "", "sharpsignalDocId": 226}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 226 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 226 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 2, 2026 20:25
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 Casino — Rulebook (corpus doc 226) | p.4 | 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 Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | 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 Casino — Rulebook (corpus doc 226) | 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 Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | 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 Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | 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 Casino — Rulebook (corpus doc 226) | p.4 | 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 Casino — Rulebook (corpus doc 226) | p.5 | 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 Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | 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 Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | no quote on the wire |
| [2] | RULEBOOK Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | no quote on the wire |
| [3] | RULEBOOK Casino — Rulebook (corpus doc 226) | p.4 | no quote on the wire | |
| [4] | RULEBOOK Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | no quote on the wire |
| [5] | RULEBOOK Casino — Rulebook (corpus doc 226) | CASSINO. | p.3 | no quote on the wire |
| [6] | RULEBOOK Casino — Rulebook (corpus doc 226) | p.4 | no quote on the wire | |
| [7] | RULEBOOK Casino — Rulebook (corpus doc 226) | p.4 | no quote on the wire | |
| [8] | RULEBOOK Casino — Rulebook (corpus doc 226) | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 243 ms · first delta 4438 ms · total 79800 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 72210 ms · retrieval 243 ms · ask 7336 ms · gateway work 7590 ms · total 79800 ms
- tokens in (the prompt the answerer read)
- 4405
- tokens out (what the answerer generated)
- 420
- tok/sec
- 136.3 tok/sec — 420 output tokens in 3.082 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 52s 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 152), 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.