Ruling — Cribbage

You asked

When does the game end?

Answered counted as answered

Asked with: Cribbagebg-2398-en-1e

The end of the game depends on the specific variety being played: * **Six-card Cribbage:** The game is 61 points [1]. * **Solitaire Cribbage:** The game is usually 91 points [2]. In a competition with two or more players, the winner is the player who gets the greatest number of points in going through the pack once; if neither side reaches 91 before the pack runs out, the player that comes nearer to it wins [2].

[1] RULEBOOK Cribbage — Rulebook · p.2 · CRIBBAGE.

[2] RULEBOOK Cribbage — Rulebook · p.15 · SOLITAIRE CRIBBAGE.

🔧 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 236 ms · ask 10835 ms · total 18862 ms
single-flight (PR-5): queued 7779 ms · generation 11083 ms
retrieval refs (raw): [{"page": 35, "score": 0.032787, "snippet": "Play continues, and all cards in both hands and crib are counted, including those declared dead during pegging. Exception: if a player calls 'go' and their opponent then pegs out, the game is over. It is not a renege if that player had cards that could have been played. If a player announces an inco", "headingPath": "7.3. Renege · 7.4. Incorrect Announcements", "sharpsignalDocId": 151}, {"page": 32, "score": 0.032258, "snippet": "Each played card shall be positioned so as to overlap that player's previously played cards while keeping the identity of all cards visible. Played cards shall not be turned over before all cards of both players are played and the hands counted and pegged. A single card released by the fingers is co", "headingPath": "7.1. The Order of Play · 7.2. Scoring", "sharpsignalDocId": 151}, {"page": 41, "score": 0.031746, "snippet": "In all ACC events except match play, a player must peg out; if the player does not peg out, the opponent must remind them to do so (this rule does not apply in muggins tournaments). If the player refuses to peg out, judges must be called. Judges will confirm the player's refusal to peg out and rule ", "headingPath": "8.10. Failure to Place Peg in Game (Out) Hole · 9.1. Exposure While Counting · 9.2. Order of Counting", "sharpsignalDocId": 151}, {"page": 34, "score": 0.03101, "snippet": "A player may correct a 'go' call before either player plays a card or pegs a point. Thereafter, in the case of a single renege, when any reneged card is played, the opponent may claim a renege up to the time they play their next card or announces the count of their hand. In the case of a double or t", "headingPath": "7.3. Renege", "sharpsignalDocId": 151}, {"page": 13, "score": 0.03009, "snippet": "count sequence. 'Go' should be called verbally, not gestured. Points are scored during this play of the cards (see scoring chart in rule 1.7). When both players have played all their cards, the pone's hand is counted and pegged by the pone (see scoring chart). The dealer then does the same for the d", "headingPath": "1.5. Outline of Playing Sequence", "sharpsignalDocId": 151}, {"page": 33, "score": 0.029644, "snippet": "three of a kind four of a kind straights of three or more cards, in any sequence a cumulative count of 15 the last card before player calls 'go' (i.e., cannot play a card that would not make the count exceed 31) a cumulative count of 31 the final card played, not making a cumulative count of 31 A pl", "headingPath": "7.2. Scoring · 7.3. Renege", "sharpsignalDocId": 151}, {"page": 40, "score": 0.029211, "snippet": "If a player picks up an opponent's peg to record a score (forward or backward), the peg shall be returned to its former place. The nonoffender receives two points. The offending player may then record the proper score using his or her own back peg. If a player records an otherwise correct score but ", "headingPath": "8.7. Pegging with Opponent's Pegs · 8.8. Recording Score in Wrong Track · 8.9. Pegging a 'Go' before Announcement", "sharpsignalDocId": 151}, {"page": 25, "score": 0.02879, "snippet": "the pack. Play continues, and both hands and the crib are counted. Pegging and play continue. All of the pone's pegging points count. Any points pegged by the dealer before or after discovery do not count. The pone's hand is counted; the dealer's hand is dead. The crib is counted if it is correct or", "headingPath": "d. Actions:", "sharpsignalDocId": 151}]
citations (raw): [{"page": 2, "quote": null, "headingPath": "CRIBBAGE.", "sharpsignalDocId": 223}, {"page": 15, "quote": null, "headingPath": "SOLITAIRE CRIBBAGE.", "sharpsignalDocId": 223}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 151 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 151 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:17

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 Cribbage — Rulebook (corpus doc 151)	7.3. Renege · 7.4. Incorrect Announcements	p.35	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 Cribbage — Rulebook (corpus doc 151)	7.1. The Order of Play · 7.2. Scoring	p.32	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 Cribbage — Rulebook (corpus doc 151)	8.10. Failure to Place Peg in Game (Out) Hole · 9.1. Exposure While Counting · 9.2. Order of Counting	p.41	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 Cribbage — Rulebook (corpus doc 151)	7.3. Renege	p.34	0.03101 (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 Cribbage — Rulebook (corpus doc 151)	1.5. Outline of Playing Sequence	p.13	0.03009 (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 Cribbage — Rulebook (corpus doc 151)	7.2. Scoring · 7.3. Renege	p.33	0.029644 (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 Cribbage — Rulebook (corpus doc 151)	8.7. Pegging with Opponent's Pegs · 8.8. Recording Score in Wrong Track · 8.9. Pegging a 'Go' before Announcement	p.40	0.029211 (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 Cribbage — Rulebook (corpus doc 151)	d. Actions:	p.25	0.02879 (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

#	document	heading	page	quote chars
[1]	RULEBOOK Cribbage — Rulebook (corpus doc 223)	CRIBBAGE.	p.2	no quote on the wire
[2]	RULEBOOK Cribbage — Rulebook (corpus doc 223)	SOLITAIRE CRIBBAGE.	p.15	no quote on the wire

generation — timing and the path taken

timing split: retrieval 236 ms · first delta 10257 ms · total 18862 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 7779 ms · retrieval 236 ms · ask 10835 ms · gateway work 11083 ms · total 18862 ms
tokens in (the prompt the answerer read): 4070
tokens out (what the answerer generated): 106
tok/sec: 134.5 tok/sec — 106 output tokens in 0.788 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: 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 73), 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.