Ruling — Sushi Go Party!

You asked

How do I play?

Answered counted as answered

Asked with: Sushi Go Party!bg-192291-en-1e

Setup

1. Before each round, shuffle a group of face-down dessert cards into the main deck based on the number of players.[1][2]

2. Deal cards face-down to each player based on the number of players: 10 cards for 2-3 players, 9 cards for 4-5 players, 8 cards for 6-7 players, and 7 cards for 8 players.[1][2]

3. Place the remaining cards in a face-down deck beside the game board.[1][2]

4. Take your cards into your hand, secret from other players.[1][2]

Playing a Turn

1. Turns happen simultaneously.[1][2]

2. Each player chooses 1 card in their hand they would like to keep and places it face-down in front of them.[1][2]

3. All players reveal their chosen cards by turning them face-up.[1][2]

4. After revealing cards, pass your remaining hand face-down to the player on your left, moving clockwise around the table.[1][2]

5. Pick up this new hand to begin the next turn.[1][2]

6. Bonus actions (using cards like Chopsticks or Spoon) are called out as all players are revealing their cards; these actions take effect after all players have played their chosen cards but before players pick up the hand from their neighbor.[3]

7. If multiple bonus actions, menus, or takeout boxes are played in the same turn, use the small number in the lower-right corner of the card to determine the order (lowest number goes first).[4][3]

Ending a Round

1. A round is over when all cards have been played and everyone's hand is empty.[3]

2. Place any dessert cards off to your side; these are kept until the end of the game.[3]

3. Score all other cards played this round according to their specific rules.[3]

4. Move your pawn along the score track on the game board to show points scored in the round.[3]

5. Collect and re-shuffle all cards (except dessert cards) together, adding a new set of dessert cards for the next round.[3]

Ending the Game

1. The game ends after 3 rounds.[3]

2. Score your dessert cards as described in the Card Guide.[3]

3. The winner is whoever has the most points; if there is a tie, the player with the most dessert cards wins.[3]

[1] RULEBOOK Sushi Go Party! — Rulebook · p.3 · CUTTHROAT COMBO Interactive and in your face! · STARTING A ROUND · 6-8 PLAYERS · PLAYING A TURN

[2] RULEBOOK Sushi Go Party! — Rulebook · p.3

[3] RULEBOOK Sushi Go Party! — Rulebook · p.4 · PLAYING A TURN · SPECIAL CARD ACTIONS · ENDING A ROUND · ENDING THE GAME

[4] RULEBOOK Sushi Go Party! — Rulebook · p.7 · EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU

The table has its answer — dice up.

🔧 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 114 ms · ask 4685 ms · total 4801 ms
single-flight (PR-5): queued 0 ms · generation 4801 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 4, "score": 0.04918, "snippet": "8 Most cards score at the end of a round, but there are a few that have special rules that may affect the current turn: See the 'Card Guide' in the back for more details about how each card works. Chopsticks and spoon cards allow you to perform a bonus action on any turn after the turn in which the ", "headingPath": "PLAYING A TURN · SPECIAL CARD ACTIONS · ENDING A ROUND · ENDING THE GAME", "sharpsignalDocId": 178}, {"page": 7, "score": 0.047883, "snippet": "Use chopsticks to grab those two dishes you really need at the same time. Chopsticks let you take 2 cards on a future turn . Nothing happens on the turn when you initially play chopsticks. However, you may use it on a future turn to take a bonus action. When you want to use it, call out 'chopsticks!", "headingPath": "CHOPSTICKS", "sharpsignalDocId": 178}, {"page": 7, "score": 0.047619, "snippet": "These three cards allow you to play another card during a turn. Here are some rules clarifications based on which extra card you play: NIGIRI: If you already have a wasabi card with no nigiri on it, you must play this nigiri on top of your wasabi. MISO SOUP: If a previous miso soup card has already ", "headingPath": "EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU", "sharpsignalDocId": 178}, {"page": 7, "score": 0.047379, "snippet": "Soy sauce makes every dish taste better. It's the perfect addition to a varied meal. At the end of a round in which soy sauce is played, all players compare how many different colored backgrounds they have among the cards they have played. If a player has the most (or tied for the most) different co", "headingPath": "SOY SAUCE", "sharpsignalDocId": 178}, {"page": 3, "score": 0.044388, "snippet": "BIG BANQUET Works well with 6-8 players. DINNER FOR TWO Works well with 2 players. CREATE YOUR OWN MENU Pick your own card combination to play with! You can play with any combination of cards you like. Just make sure your game is made up of the following: Nigiri cards are used in every game. 1 type ", "headingPath": "CUTTHROAT COMBO Interactive and in your face! · STARTING A ROUND · 6-8 PLAYERS · PLAYING A TURN", "sharpsignalDocId": 178}, {"page": 3, "score": 0.044283, "snippet": "(In this way, each hand will move clockwise around the table.) Pick up this new hand and the next turn begins. (Y ou will have a smaller hand to choose from.) Note: Face-up cards remain with you until the end of the round, when they are scored. As you accumulate cards, group them together in columns", "headingPath": "", "sharpsignalDocId": 178}, {"page": 8, "score": 0.043697, "snippet": "SPECIAL ORDER (only use in 2-6 player games) Enjoyed a dish you've already eaten and want more of it? Ask the chef for a special order! A special order card copies any other card you previously played in the current round . When you choose to play special order from your hand, place it face-down on ", "headingPath": "EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU", "sharpsignalDocId": 178}, {"page": 3, "score": 0.043184, "snippet": "CUTTHROA T COMBO Interactive and in your face! BIG BANQUET Works well with 6–8 players. DINNER FOR TWO Works well with 2 players. CREA TE YOUR OWN MENU Pick your own card combination to play with! Y ou can play with any combination of cards you like. Just make sure your game is made up of the follow", "headingPath": "", "sharpsignalDocId": 178}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 3, "quote": null, "headingPath": "CUTTHROAT COMBO Interactive and in your face! · STARTING A ROUND · 6-8 PLAYERS · PLAYING A TURN", "sharpsignalDocId": 178}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 178}, {"page": 4, "quote": null, "headingPath": "PLAYING A TURN · SPECIAL CARD ACTIONS · ENDING A ROUND · ENDING THE GAME", "sharpsignalDocId": 178}, {"page": 7, "quote": null, "headingPath": "EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU", "sharpsignalDocId": 178}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 178 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 178 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.87801 of 1705 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 26, 2026 07:05 UTC

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	heading	page	fused RRF score	snippet chars
#1	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	PLAYING A TURN · SPECIAL CARD ACTIONS · ENDING A ROUND · ENDING THE GAME	p.4	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	CHOPSTICKS	p.7	0.047883 (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 Sushi Go Party! — Rulebook (corpus doc 178)	EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU	p.7	0.047619 (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 Sushi Go Party! — Rulebook (corpus doc 178)	SOY SAUCE	p.7	0.047379 (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 Sushi Go Party! — Rulebook (corpus doc 178)	CUTTHROAT COMBO Interactive and in your face! · STARTING A ROUND · 6-8 PLAYERS · PLAYING A TURN	p.3	0.044388 (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 Sushi Go Party! — Rulebook (corpus doc 178)		p.3	0.044283 (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 Sushi Go Party! — Rulebook (corpus doc 178)	EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU	p.8	0.043697 (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 Sushi Go Party! — Rulebook (corpus doc 178)		p.3	0.043184 (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 27 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	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	CHOPSTICKS	p.7	#2	0.047883 (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 Sushi Go Party! — Rulebook (corpus doc 178)	EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU	p.7	#3	0.047619 (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
#3	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	TAKEOUT BOX · TEA · WASABI	p.8	#13	0.027151 (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 re-ranker chose it
#4	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	CUTTHROAT COMBO Interactive and in your face! · STARTING A ROUND · 6-8 PLAYERS · PLAYING A TURN	p.3	#5	0.044388 (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 Sushi Go Party! — Rulebook (corpus doc 178)		p.3	#8	0.043184 (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 Sushi Go Party! — Rulebook (corpus doc 178)	PLAYING A TURN · SPECIAL CARD ACTIONS · ENDING A ROUND · ENDING THE GAME	p.4	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)		p.3	#6	0.044283 (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 Sushi Go Party! — Rulebook (corpus doc 178)	EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU	p.8	#7	0.043697 (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	heading	page	quote chars
[1]	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	CUTTHROAT COMBO Interactive and in your face! · STARTING A ROUND · 6-8 PLAYERS · PLAYING A TURN	p.3	no quote on the wire
[2]	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)		p.3	no quote on the wire
[3]	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	PLAYING A TURN · SPECIAL CARD ACTIONS · ENDING A ROUND · ENDING THE GAME	p.4	no quote on the wire
[4]	RULEBOOK Sushi Go Party! — Rulebook (corpus doc 178)	EXTRA RULES FOR USING CHOPSTICKS, SPOON OR MENU	p.7	no quote on the wire

generation — timing and the path taken

timing split: retrieval 114 ms · first delta 1955 ms · total 4801 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 114 ms · ask 4685 ms · gateway work 4801 ms · total 4801 ms
tokens in (the prompt the answerer read): 3661
tokens out (what the answerer generated): 554
tok/sec: 198.6 tok/sec — 554 output tokens in 2.790 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 56s ago)
answerer host (measured by rulesage): reachable (for 23h, checked 7s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
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 96), 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.