RuleSage cited table rulings
← Critter Kitchen

You asked

How do I play?

Answered counted as answered

Asked with: Critter Kitchenbg-393429-en-1e

The game takes place over 7 rounds, divided into 3 days.[1] Each round consists of 5 steps:[1]
1. Step 1: Start of Round [1]
2. Step 2: Planning [1]
3. Step 3: Running [1]
4. Step 4: Shopping [1]
5. Step 5: End of Round [1]
During the **Start of Round**, the following occurs:[1]
* The maître d’ can guide players through the process by following the Maître d’ Card.[1]
* If the bisque space on the Soup Truck is empty, 1 bisque is placed there from the supply.[1]
* A new challenge is revealed by flipping the leftmost face-down Challenge Card on the Waterfront Board; if a Hold Token is on the current space of the round track, it is placed on the card to cover the rightmost required ingredient.[1]
* Items are restocked by going through each location (skipping the Soup Truck) and filling each item space with a random item from the bag; however, items are not placed on the Midnight Merchant or Chef Academy.[1]
* A new Zous-chef is revealed at the Chef Academy, and its matching Zous-chef Token is placed on the location; the previous round's Zous-chef is removed from the game if it was not picked.[1]
* In the 7th Round only, a new challenge is not revealed, and instead of revealing a new Zous-chef, the Allspice 7th-Round Token is taken from the round track and placed on the Chef Academy.[1]
During **Shopping**, locations are resolved one at a time, starting with the Soup Truck and moving along the row from left to right.[2] When a location is resolved:
* Each chef there collects items in queue order.[2]
* Chefs with a carrying capacity of 1 pick first, then those with a capacity of 2, and finally those with a capacity of 3.[2]
* If only one chef is in a queue, they pick all their items at once before the next queue picks.[2]
* If there are two or more chefs in the same queue, they alternate picking one item at a time in priority track order.[2]
* Once chefs have taken as much as they can carry, the next queue picks.[2]
* If multiple players have chefs in the same queue, ties are broken using their positions on the priority track, with the rightmost Chef Hat indicating who goes first.[2]
* If the chef going first in a tie is the first to pick an item from that location, they must move their Chef Hat to the back of the priority track; otherwise, no one moves their hat.[2]
[1] RULEBOOK Critter Kitchen — Rulebook · p.7
[2] RULEBOOK Critter Kitchen — Rulebook · p.9 · Step 4: Shopping · Resolving a Location · BREAKING TIES DURING SHOPPING · Example

Now you know — make it count.

🔧 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 90 ms · ask 5251 ms · total 5346 ms
single-flight (PR-5)
queued 0 ms · generation 5346 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 20, "score": 0.047371, "snippet": "To win, your restaurant needs to earn more stars than McDogald's. While you follow the same steps as in the multiplayer game, McDogald's plays by their own rules. Follow the same steps as in the multiplayer game, with the following differences: Each round, place your chefs directly on their location", "headingPath": "Goal · Gameplay · Step 2: Planning · Step 3: Running · McDogald's Placement", "sharpsignalDocId": 770}, {"page": 5, "score": 0.047073, "snippet": "Location Cards: Take the 9 Location Cards of your color. Create your hand by keeping the cards matching the locations used in the game and return the remaining cards (including the Break Time Card) to the box. 2 3 Plates: Place a Critic Plate and 3 Challenge Plates anywhere in your player area. Thes", "headingPath": "Game Setup Setup", "sharpsignalDocId": 770}, {"page": 4, "score": 0.046402, "snippet": "Maître d': Nominate a player to be maître d' and give them the Maître d' Card. They will be responsible for guiding players through setup at the beginning of each round. 1 2 Token Bag: Put all Ingredient, Spice, and Rumor Tokens (oblong shape) into the bag and shake it. 3 Waterfront: Place the Water", "headingPath": "Game Setup Setup", "sharpsignalDocId": 770}, {"page": 5, "score": 0.046176, "snippet": "5 5SetupSetup Player SetupPlayer Setup Each player takes the following steps to set up: Components: Pick a color and take the Restaurant Shield, Kitchen Board, Chef Hat, and 3 Chef Figures (mouse, lizard, and boar) in your color. Set up your shield to create your hidden storage next to your Kitchen ", "headingPath": "", "sharpsignalDocId": 770}, {"page": 7, "score": 0.032258, "snippet": "7 GameplayGameplay Step 1:Step 1: Start of RoundStart of Round At the start of each round, the various vendors of Bistro Bay must prepare for the day’s clientele. The maître d’ can guide everyone through this process by following the Maître d’ Card. Restock bisque: If the bisque space on the Soup Tr", "headingPath": "", "sharpsignalDocId": 770}, {"page": 7, "score": 0.030769, "snippet": "The game takes place over 7 rounds, divided into 3 days. Each round has 5 steps: At the start of each round, the various vendors of Bistro Bay must prepare for the day's clientele. The maître d' can guide everyone through this process by following the Maître d' Card. Restock bisque: If the bisque sp", "headingPath": "Gameplay · Step 1: Start of Round", "sharpsignalDocId": 770}, {"page": 19, "score": 0.029877, "snippet": "You are the executive chef, known for the special touch you add to every meal. Restaurateurs provide each player with a special ability they may utilize in the game. Restaurateurs: After the game is set up and ready to play, deal each player 2 Restaurateur Cards. Players pick one and display it face", "headingPath": "Restaurateurs (Optional) · Bonus Scoring · Solo Mode · Critic Card · Player Setup", "sharpsignalDocId": 770}, {"page": 8, "score": 0.029851, "snippet": "Once you've seen what Bistro Bay has to offer, it's time to plan where to send your chefs this round. Each player simultaneously gives secret instructions to their chefs by placing Location Cards face down above their Kitchen Board. You must place 1 Location Card face down in each of your 3 card slo", "headingPath": "Step 2: Planning · Step 3: Running · CARRYING CAPACITY · Example: · ZOUS-CHEF INSTRUCTIONS", "sharpsignalDocId": 770}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 7, "quote": null, "headingPath": "", "sharpsignalDocId": 770}, {"page": 9, "quote": null, "headingPath": "Step 4: Shopping · Resolving a Location · BREAKING TIES DURING SHOPPING · Example", "sharpsignalDocId": 770}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 770 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 770 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.90991 of 1876 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until
Nov 16, 2026 23:53 UTC

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 rankdocumentheadingpage fused RRF scoresnippet chars
#1 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Goal · Gameplay · Step 2: Planning · Step 3: Running · McDogald's Placement p.20 0.047371 (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 Critter Kitchen — Rulebook (corpus doc 770) Game Setup Setup p.5 0.047073 (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 Critter Kitchen — Rulebook (corpus doc 770) Game Setup Setup p.4 0.046402 (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 Critter Kitchen — Rulebook (corpus doc 770) p.5 0.046176 (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 Critter Kitchen — Rulebook (corpus doc 770) p.7 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
#6 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Gameplay · Step 1: Start of Round p.7 0.030769 (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 Critter Kitchen — Rulebook (corpus doc 770) Restaurateurs (Optional) · Bonus Scoring · Solo Mode · Critic Card · Player Setup p.19 0.029877 (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 Critter Kitchen — Rulebook (corpus doc 770) Step 2: Planning · Step 3: Running · CARRYING CAPACITY · Example: · ZOUS-CHEF INSTRUCTIONS p.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)) 300

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 39 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 atdocumentheadingpage fused rankfused RRF scorecarried byhow it got its slot
#1 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Game Setup Setup p.5 #2 0.047073 (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 Critter Kitchen — Rulebook (corpus doc 770) Restaurateurs (Optional) · Bonus Scoring · Solo Mode · Critic Card · Player Setup p.19 #7 0.029877 (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
#3 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Game Setup Setup p.4 #3 0.046402 (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
#4 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) p.7 #5 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)) vector + the doc-priority boost arm the re-ranker chose it
#5 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) ZOUS-CHEF ABILITIES · Example: p.8 #24 0.012658 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one)) vector the re-ranker chose it
#6 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Step 4: Shopping · Resolving a Location · BREAKING TIES DURING SHOPPING · Example p.9 #9 0.029412 (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
#7 RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Goal · Gameplay · Step 2: Planning · Step 3: Running · McDogald's Placement p.20 #1 0.047371 (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 Critter Kitchen — Rulebook (corpus doc 770) p.5 #4 0.046176 (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

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.

#documentheadingpagequote chars
[1] RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) p.7 no quote on the wire
[2] RULEBOOK Critter Kitchen — Rulebook (corpus doc 770) Step 4: Shopping · Resolving a Location · BREAKING TIES DURING SHOPPING · Example p.9 no quote on the wire
timing split
retrieval 90 ms · first delta 2445 ms · total 5346 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 90 ms · ask 5251 ms · gateway work 5346 ms · total 5346 ms
tokens in (the prompt the answerer read)
3126
tokens out (what the answerer generated)
589
tok/sec
205.6 tok/sec — 589 output tokens in 2.865 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 17s ago)
gateway schema (read from the running child)
schema head 0042_definer_search_path (live revision not readable by this principal)
answerer host (measured by rulesage)
reachable (for 60h, checked 5s 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.
outcome
ANSWERED — Answered
abstain rationale (n/a — this ruling answered)
answered — no abstain rationale applies
decision
NOT_SETUP_SHAPED — no setup-shape pattern matched this question

this game registers NO errata cards (edition 704), 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.