You asked
How do I score fifteens?
Answered counted as answeredAsked with: Cribbagebg-2398-en-1e
🔧 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 215 ms · ask 14063 ms · total 26807 ms
- single-flight (PR-5)
- queued 12518 ms · generation 14289 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 55, "score": 0.032266, "snippet": "Determine the number of qualifiers (rule 13.2.b). Collect and count scorecards from each table to make sure that all were turned in. Do not write scores in the boxes at the top of scorecards until cross-checking is completed. Initially check the game-points and games-won columns of all scorecards. D", "headingPath": "Method", "sharpsignalDocId": 151}, {"page": 13, "score": 0.031281, "snippet": "Never play a card which will allow the adversary to make a double score, such as a pair and a fifteen, or a sequence and a fifteen at the same time. Such as the following are all bad plays: 9 on 3; 7 on A; 6 on 3, 4, or 5; 5 on 5; 4 on 7; 3 on 9; A on 7. All these expose you to the immediate rejoind", "headingPath": "Q♠ J♣ J♠ 10♣ A♠", "sharpsignalDocId": 223}, {"page": 36, "score": 0.031054, "snippet": "Beginning with the outside track, a player shall record his or her first score by placing a peg in the hole corresponding to that score. Subsequent scores are recorded by advancing the rear peg over the front peg by 'leapfrogging' the number of holes consistent with the score to be recorded. If a ze", "headingPath": "8.1. Recording Score on Board · 8.2. Zero Hand or Crib · 8.3. Pegging Incorrectly to the Player's Disadvantage · 8.4. Pegging Incorrectly to the Player's Advantage", "sharpsignalDocId": 151}, {"page": 56, "score": 0.030579, "snippet": "Resolve scorecard discrepancies by referring to rule 12.2. 18.Write the score in the boxes at the top of scorecard when cross-checking is completed. In the event that a scorecard is disqualified or changes position because of an error, contact that player with the relevant scorecards as evidence. Ga", "headingPath": "Method", "sharpsignalDocId": 151}, {"page": 16, "score": 0.030118, "snippet": "* | | points earned . . . | points earned . . . | | cards | during play | in hand or crib | | Jack turned by dealer as starter card | 2 | - | | Jack in hand or crib of same suit as starter card | - | 1 | | combinations: | | | | • two of a kind (pair) | 2 | 2 | | • three of a kind (triple) | 6 | 6 | ", "headingPath": "1.7. Scoring Chart", "sharpsignalDocId": 151}, {"page": 9, "score": 0.029762, "snippet": "The total score of the dealer is now 10 points, and that of the pone is 15. The cards they held, and the order in which they were played is as follows:-- SHOWING. In order to illustrate the manner of counting the hands, which is called showing, let us suppose the starter to be a Queen, and that the ", "headingPath": "K♠ J♡ 5♠", "sharpsignalDocId": 223}, {"page": 11, "score": 0.02967, "snippet": "If he invites the run, hoping to make it longer himself, he is said to play on. When a player is behind, it is better for him to play on, and to seize every chance to score, especially with sequences. As it is considered an advantage to be ahead on the first deal, most players prefer a forward game ", "headingPath": "Q♠ J♣ J♠ 10♣ A♠", "sharpsignalDocId": 223}, {"page": 33, "score": 0.029469, "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}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 5, "quote": null, "headingPath": "A♣ A♢ 2♣ 3♡ 3♣", "sharpsignalDocId": 223}, {"page": 6, "quote": null, "headingPath": "K♠ J♡ 5♠", "sharpsignalDocId": 223}, {"page": 7, "quote": null, "headingPath": "K♠ J♡ 5♠", "sharpsignalDocId": 223}, {"page": 6, "quote": null, "headingPath": "K♠ J♡ 5♠", "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 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. How much wider that pool was is set gateway-side and is NOT REPORTED for this ruling, and neither are the answerer's final rows — so rulesage has nothing of its own to show beside these.
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 — ACC Tournament Rules (2025) (corpus doc 151) | Method | p.55 | 0.032266 (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 — Foster's Complete Hoyle (1914) (corpus doc 223) | Q♠ J♣ J♠ 10♣ A♠ | p.13 | 0.031281 (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 — ACC Tournament Rules (2025) (corpus doc 151) | 8.1. Recording Score on Board · 8.2. Zero Hand or Crib · 8.3. Pegging Incorrectly to the Player's Disadvantage · 8.4. Pegging Incorrectly to the Player's Advantage | p.36 | 0.031054 (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 — ACC Tournament Rules (2025) (corpus doc 151) | Method | p.56 | 0.030579 (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 — ACC Tournament Rules (2025) (corpus doc 151) | 1.7. Scoring Chart | p.16 | 0.030118 (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 — Foster's Complete Hoyle (1914) (corpus doc 223) | K♠ J♡ 5♠ | p.9 | 0.029762 (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 — Foster's Complete Hoyle (1914) (corpus doc 223) | Q♠ J♣ J♠ 10♣ A♠ | p.11 | 0.02967 (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 — ACC Tournament Rules (2025) (corpus doc 151) | 7.2. Scoring · 7.3. Renege | p.33 | 0.029469 (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.
the passages the answerer read: NOT RECORDED for this ruling. Any of three things leaves this empty, and they are all different from the answerer having had nothing to read: this ask may never have reached a gateway at all; a multi-book ask keeps each book's own context on that book's own page rather than here; or the gateway build that answered may simply not report it. What this NEVER means is that the answerer read nothing — an answer was composed from passages either way, and their absence here is a gap in what we were told, not in what it read.
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 Cribbage — Foster's Complete Hoyle (1914) (corpus doc 223) | A♣ A♢ 2♣ 3♡ 3♣ | p.5 | no quote on the wire |
| [2] | RULEBOOK Cribbage — Foster's Complete Hoyle (1914) (corpus doc 223) | K♠ J♡ 5♠ | p.6 | no quote on the wire |
| [3] | RULEBOOK Cribbage — Foster's Complete Hoyle (1914) (corpus doc 223) | K♠ J♡ 5♠ | p.7 | no quote on the wire |
| [4] | RULEBOOK Cribbage — Foster's Complete Hoyle (1914) (corpus doc 223) | K♠ J♡ 5♠ | p.6 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 215 ms · first delta 10259 ms · total 26807 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 12518 ms · retrieval 215 ms · ask 14063 ms · gateway work 14289 ms · total 26807 ms
- tokens in (the prompt the answerer read)
- 4210
- tokens out (what the answerer generated)
- 537
- tok/sec
- 135.3 tok/sec — 537 output tokens in 3.968 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 57s 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.