Ruling — Red7 — RuleSage

← Red7

You asked

How do I play?

Answered counted as answered

Asked with: Red7bg-161417-en-1e

**First Turn Setup**

1. Deal a seven-card hand to each player.[1][2]

2. Deal one more card faceup in front of each player to start their Palette.[1][2]

3. Start the Canvas (discard pile) with the "You are Playing Red" card.[3]

4. The player to the left of the player with the highest card on their Palette goes first.[3]

**On Your Turn**

You must take one of the following actions:

1. Play a card faceup from your hand to your Palette.[4]

2. Discard a card from your hand to the Canvas to change the game to the rule of the discarded card’s color, provided you are winning the new game after doing this.[4]

3. Play a card from your hand to your Palette AND THEN discard a card to the Canvas, provided you are winning the game after doing this.[4]

4. Do nothing, and lose.[4] (Note: You might do this intentionally in Advanced Red7 to limit an opponent's score, and you must do this if your hand is empty).[4]

**Winning and Losing**

* You are currently winning a game if your Palette contains more cards that meet the current game’s rule than any other player.[4]

* To break a tie, look at each tied player’s highest card that follows the rule, checking its value, then its color if necessary.[4]

* If you have no cards (for Green or Violet) that follow the rule, you are not winning.[4]

* If you are not winning the game at the end of your turn, you lose and are out of the round.[4][2][5]

* If your hand is empty at the start of your turn, you lose because you are unable to do anything to win by the end of your turn.[4]

* If you are ever the last player in the game, you win the round.[4]

**Scoring and Ending the Game**

* If you win a round, take all the cards from your Palette that meet the current rule and place them under your reference card.[6]

* Cards are worth their face value in points.[6]

* The next hand is dealt without those cards, as they are now your score pile.[6]

* The game ends if there are not enough cards to deal out a new hand to each player, and the player with the highest score wins.[6]

* Point thresholds for winning: 2 players: 40 points; 3 players: 35 points; 4 players: 30 points.[6]

[1] RULEBOOK Red7 — Rulebook · p.2

[2] RULEBOOK Red7 — Rulebook · p.2

[3] RULEBOOK Red7 — Rulebook · p.3

[4] RULEBOOK Red7 — Rulebook · p.4

[5] RULEBOOK Red7 — Rulebook · p.1

[6] RULEBOOK Red7 — Rulebook · p.6

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 79 ms · ask 4060 ms · total 4141 ms
single-flight (PR-5): queued 0 ms · generation 4141 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 4, "score": 0.048916, "snippet": "4 asmadigames.com On your turn, you must take one of the following actions: 1. Play a card faceup from your hand to your Palette. 2. Discard a card from your hand to the Canvas to change the game to the rule of the discarded card’s color. You must be winning the new game after you do this. (see righ", "headingPath": "", "sharpsignalDocId": 791}, {"page": 7, "score": 0.048131, "snippet": "The four odd-numbered cards have icons in their corners. These represent an optional rule for actions, meant for experienced Red7 players. They can be mixed with either Basic or Advanced Red7 . By these rules, when you play a 1, 3, 5, or 7 to your Palette, you MUST perform that card's action if you ", "headingPath": "", "sharpsignalDocId": 791}, {"page": 1, "score": 0.046635, "snippet": "RULEBOOK v1.2 @AsmadiGames facebook.com/AsmadiGames The rule for winning at Red is simple: Have the best card! But will you still be playing the same game when your turn ends? If you're not winning by the current game's rule at the end of your turn, you're out, and the last person standing wins the ", "headingPath": "", "sharpsignalDocId": 791}, {"page": 2, "score": 0.046394, "snippet": "2 asmadigames.com The rule for winning at Red is simple: Have the best card! But will you still be playing the same game when your turn ends? If you’re not winning by the current game’s rule at the end of your turn, you’re out, and the last person standing wins the round. The deck consists of 49 car", "headingPath": "", "sharpsignalDocId": 791}, {"page": 3, "score": 0.045805, "snippet": "3 @AsmadiGames facebook.com/AsmadiGames your hand opponent’s hand your palette opponent’s palette canvas (discard pile) draw deck YOU ARE CURRENTLY PLAYING RED. HIGHEST CARD WINS. YOU ARE CURRENTLY PLAYING RED. HIGHEST CARD WINS. 7 7 7 Blue: Most diFFerent colors Blue: Most diFFerent colors 6 6 6 or", "headingPath": "", "sharpsignalDocId": 791}, {"page": 5, "score": 0.045455, "snippet": "5 @AsmadiGames facebook.com/AsmadiGames GAME RED ORANGE YELLOW GREEN BLUE INDIGO VIOLET CANVAS RULE HIGHEST CARD CARDS OF ONE NUMBER CARDS OF ONE COLOR EVEN CARDS CARDS OF ALL DIFFERENT COLORS CARDS THAT FORM A RUN (I.E. 4 5 6) CARDS BELOW 4 > > > > > > > EXAMPLE Once you’ve played Red7 a few times,", "headingPath": "", "sharpsignalDocId": 791}, {"page": 6, "score": 0.031746, "snippet": "If you win a round, take all the cards from your Palette that meet the current rule and place them under your reference card. For example, if you won Blue by having the most differently colored cards on your Palette, take the highest card of each color from your Palette and place them under your ref", "headingPath": "", "sharpsignalDocId": 791}, {"page": 2, "score": 0.029851, "snippet": "The deck consists of 49 cards numbered 1-7 , in each of the seven rainbow colors. A 7 is always higher than a 6, but a Red 6 is higher than an Orange 6, and so on down the color spectrum (Red, Orange, Yellow, Green, Blue, Indigo, Violet). When comparing two cards, compare value first, then color. To", "headingPath": "", "sharpsignalDocId": 791}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "", "sharpsignalDocId": 791}, {"page": 2, "quote": null, "headingPath": "", "sharpsignalDocId": 791}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 791}, {"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 791}, {"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 791}, {"page": 6, "quote": null, "headingPath": "", "sharpsignalDocId": 791}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 791 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 791 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)
answer fence: passed — letter density 0.89529 of 1719 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 15, 2026 05:05

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. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

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	page	fused RRF score	snippet chars
#1	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.4	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 Red7 — Rulebook (corpus doc 791)	p.7	0.048131 (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 Red7 — Rulebook (corpus doc 791)	p.1	0.046635 (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 Red7 — Rulebook (corpus doc 791)	p.2	0.046394 (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 Red7 — Rulebook (corpus doc 791)	p.3	0.045805 (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 Red7 — Rulebook (corpus doc 791)	p.5	0.045455 (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 Red7 — Rulebook (corpus doc 791)	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
#8	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.2	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

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.

candidate pool: the answering read scored 9 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.4	#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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.6	#7	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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.2	#8	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))	vector + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.3	#5	0.045805 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.5	#6	0.045455 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#6	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.2	#4	0.046394 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.1	#3	0.046635 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#8	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.7	#2	0.048131 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	page	quote chars
[1]	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.2	no quote on the wire
[2]	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.2	no quote on the wire
[3]	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.3	no quote on the wire
[4]	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.4	no quote on the wire
[5]	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.1	no quote on the wire
[6]	RULEBOOK Red7 — Rulebook (corpus doc 791)	p.6	no quote on the wire

generation — timing and the path taken

timing split: retrieval 79 ms · first delta 1307 ms · total 4141 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 0 ms · retrieval 79 ms · ask 4060 ms · gateway work 4141 ms · total 4141 ms
tokens in (the prompt the answerer read): 2232
tokens out (what the answerer generated): 577
tok/sec: 206.3 tok/sec — 577 output tokens in 2.797 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 17s 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 726), 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.