You asked
How do I set up the game?
Answered counted as answeredAsked with: Flip 7bg-420087-en-1e
1. Shuffle the deck THOROUGHLY [1]. 2. Choose a player to be the Dealer for the round [1]. 3. In turn order, the Dealer deals one card face up to each player including themself [1]. 4. If an Action card comes up in dealing, pause dealing immediately to resolve it [1]. 5. Once any Action cards are resolved, continue dealing until everyone's been dealt a card [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 300 ms · ask 2556 ms · total 2183154 ms
- single-flight (PR-5)
- queued 2180293 ms · generation 2861 ms
- retrieval refs (raw)
- [{"page": 1, "score": 0.048916, "snippet": "It has twelve 12's, eleven 11's, ten 10's… until you get to one 1; there is even one 0. There are also a few Action and Modifier cards: Flip Three, Freeze, Second Chance, and Score Modifiers. When playing the game, it is important to keep the card count in mind. x8 x3 2 x1 ACTION CARDS Have a pen an", "headingPath": "THIS IS A SPECIAL DECK OF CARDS. IMPORTANT · SCORE MODIFIER CARDS · HOW TO PLAY · IMPORTANT! · * See Action and Modifier cards on pages 6-8. · REMEMBER · …", "sharpsignalDocId": 200}, {"page": 2, "score": 0.048139, "snippet": "Modifiers are not Number cards and do not count toward achieving a Flip 7 . You cannot bust on Modifier cards. You can end your turn with just a Modifier card and no number cards, and you would still score those points, unless it's a x2 card. Add the amount shown to the sum of your Number cards. Dou", "headingPath": "THE MODIFIER CARDS · +2 TO +10 CARDS · x2 CARD · See how to calculate scores on pages 10-11. · END OF A ROUND · CALCULATE SCORES AS FOLLOWS: · …", "sharpsignalDocId": 200}, {"page": 1, "score": 0.032258, "snippet": "The player receiving this card, banks all the points they have collected and is out of the round. The player who receives this card must accept the next three cards, flipping them one at a time. Regardless of how many cards remain to flip, stop if the player can Flip 7 number cards, or the player bu", "headingPath": "FREEZE! · FLIP THREE!", "sharpsignalDocId": 200}]
- citations (raw)
- [{"page": 1, "quote": null, "headingPath": "THIS IS A SPECIAL DECK OF CARDS. IMPORTANT · SCORE MODIFIER CARDS · HOW TO PLAY · IMPORTANT! · * See Action and Modifier cards on pages 6-8. · REMEMBER · …", "sharpsignalDocId": 200}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 200 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 200 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:47
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 Flip 7 — Rulebook (corpus doc 200) | THIS IS A SPECIAL DECK OF CARDS. IMPORTANT · SCORE MODIFIER CARDS · HOW TO PLAY · IMPORTANT! · * See Action and Modifier cards on pages 6-8. · REMEMBER · … | p.1 | 0.048916 (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 Flip 7 — Rulebook (corpus doc 200) | THE MODIFIER CARDS · +2 TO +10 CARDS · x2 CARD · See how to calculate scores on pages 10-11. · END OF A ROUND · CALCULATE SCORES AS FOLLOWS: · … | p.2 | 0.048139 (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 Flip 7 — Rulebook (corpus doc 200) | FREEZE! · FLIP THREE! | p.1 | 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 |
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 Flip 7 — Rulebook (corpus doc 200) | THIS IS A SPECIAL DECK OF CARDS. IMPORTANT · SCORE MODIFIER CARDS · HOW TO PLAY · IMPORTANT! · * See Action and Modifier cards on pages 6-8. · REMEMBER · … | p.1 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 300 ms · first delta 2103 ms · total 2183154 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 2180293 ms · retrieval 300 ms · ask 2556 ms · gateway work 2861 ms · total 2183154 ms
- tokens in (the prompt the answerer read)
- 1731
- tokens out (what the answerer generated)
- 95
- tok/sec
- 137.1 tok/sec — 95 output tokens in 0.693 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 47s 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 125), 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.