You asked
How do I set up the game?
Answered counted as answeredAsked with: Casinobg-18121-en-1e
To set up the game, follow these steps: 1. Shuffle the cards properly [1]. 2. Present the cards to the pone to be cut, ensuring at least four cards are left in each packet [1]. 3. The dealer distributes four cards to each player in two rounds of two at a time, giving two cards to the table just before helping themselves in each round [1]. 4. Leave the remainder of the pack face downward on the dealer's left [1]. 5. Turn the four cards dealt to the table face up [1].
🔧 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 304 ms · ask 5694 ms · total 2120754 ms
- single-flight (PR-5)
- queued 2114747 ms · generation 6007 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": "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}, {"page": 6, "score": 0.031746, "snippet": "This game is usually marked with counters, or pegged on a cribbage board. Nothing is scored until the end of the hand, when each side reckons and claims its points. In order to avoid disputes there should be a previous understanding as to what points go out first in a close game. In the absence of a", "headingPath": "TWENTY-ONE POINT CASSINO.", "sharpsignalDocId": 226}, {"page": 5, "score": 0.03125, "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.030769, "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": 2, "score": 0.030303, "snippet": "If points are played for, the lower score is usually deducted from the higher, and the difference is the value of the game. It is sometimes agreed that if the winner has twice as many points as his adversary, he shall be paid for a double game. Dealing. After the cards have been properly shuffled th", "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 3, "score": 0.029851, "snippet": "These conditions are: that he can match or pair a card or cards on the table; that he can combine two or more cards on the table so as to make their total pip value equal to that of the card he plays; or that he can build a card in his hand upon one on the table, so as to make their total pip value ", "headingPath": "CASSINO.", "sharpsignalDocId": 226}, {"page": 7, "score": 0.029412, "snippet": "The game is scored on a cribbage board, every point being pegged immediately; that is, every spade, every Ace, the Cassinos and the sweeps. There is nothing to count at the end of the hand but the cards. Sixty-one points is game, once round the board and into the game hole. In this variation, no mor", "headingPath": "SPADE CASSINO. · DRAW CASSINO.", "sharpsignalDocId": 226}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "CASSINO.", "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 6, 2026 14:46
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) | TWENTY-ONE POINT CASSINO. | p.6 | 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) | p.5 | 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) | CASSINO. | p.2 | 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) | CASSINO. | p.3 | 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) | SPADE CASSINO. · DRAW CASSINO. | 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 |
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.2 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 304 ms · first delta 5067 ms · total 2120754 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 2114747 ms · retrieval 304 ms · ask 5694 ms · gateway work 6007 ms · total 2120754 ms
- tokens in (the prompt the answerer read)
- 4189
- tokens out (what the answerer generated)
- 119
- tok/sec
- 136.6 tok/sec — 119 output tokens in 0.871 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 20s 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
- SETUP — "setup" / "set up"
- matched words (in the normalized question)
-
set up
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.