Ruling — Ready Set Bet

You asked

How do I play?

Answered counted as answered

Asked with: Ready Set Betbg-351040-en-1e

Ready Set Bet is played over 4 rounds.[1] Each round consists of players betting on a single horse race while the action is happening.[1]

Setup

1. Place the Bet Board in the center of the table.[2]

2. Shuffle the Prop Bet Cards and place the deck face-down on the Prop Bets space at the top of the Bet Board, then draw the top 5 cards and place them face-up on the blank spaces to the right.[2]

3. Shuffle the Exotic Finish Cards and place the deck face-down on the Exotic Finish space at the bottom left of the Bet Board, then draw the top card and place it face-up on the Race 1 space to the right of the deck.[2]

4. Shuffle the VIP Cards and place the deck face-down on the VIP space at the bottom right of the Bet Board.[2]

5. Place the Money Chips and the black and white Bonus Bet Tokens in a supply near the Bet Board.[2]

6. Select a House player to run the races and place the Race Track Board near them.[2]

7. Give the House player 2 Dice and 9 Horse Meeples, placing the horses on the green starting gate spots on the left side of the Race Track Board.[2]

8. Each non-House player takes a set of 5 Player Bet Tokens in their color (if there are 7 or 8 non-House players, each player returns one of their number 3 tokens to the box).[2]

9. Place the 6 Win, Place, and Show Tokens near the Bet Board.[2]

10. If the House player wishes to compete, give them 6 House Bet Tokens.[2]

A Race

1. The House player begins the race by exclaiming, "And they're $\text{off!}$".[3]

2. The House rolls the 2 dice together, announces the sum, and moves the corresponding Horse Meeple 1 space to the right, plus any Bonus Moves.[3]

3. While the race is in progress and before "No more bets!" is called or a horse reaches the finish line, players may place their Bet Tokens onto any open Bet Spot on the Bet Board.[4]

4. Bets are placed simultaneously and are first come, first served; players may not place a token where another player's token is already placed.[4]

5. A Bonus Move is triggered when the same number is rolled twice in a row.[3]

6. At the end of the race, players resolve their bets.[3]

7. To resolve winning bets, players collect their winning Bet Tokens from the Bet Board and collect payouts from the supply equal to the Bet Token's value multiplied by the number printed in front of the "X" on the Bet Spot.[4][5]

8. To resolve losing bets, players collect their losing Bet Tokens and pay the amount indicated by the negative number in the red circle on the Bet Spot to the supply (if no red circle exists, the player pays nothing).[4][5]

9. After the race, players clean up by taking care of all cards and resetting the race track.[3]

Winning the Game

1. After 4 rounds, players count up all their money.[6]

2. The player with the most money wins; in the case of a tie, all tied players share the victory.[1][6]

[1] RULEBOOK Ready Set Bet — Rulebook · p.2 · You're off to the races in Ready Set Bet! · Ready Set Bet App: · Gameplay Overview

[2] RULEBOOK Ready Set Bet — Rulebook · p.3 · Setup

[3] RULEBOOK Ready Set Bet — Rulebook · p.4 · Round Overview · Running a Race · Bonus Moves

[4] RULEBOOK Ready Set Bet — Rulebook · p.5

[5] RULEBOOK Ready Set Bet — Rulebook · p.5 · Resolving Bets

[6] RULEBOOK Ready Set Bet — Rulebook · p.7 · Bonus Bet Tokens · Game End

The book has spoken.

🔧 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 94 ms · ask 5696 ms · total 5792 ms
single-flight (PR-5): queued 0 ms · generation 5792 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.04918, "snippet": "Do you bet early to lock in the best odds or do you wait and see how the race develops and bet in the last few seconds? The choice is yours in this game of real-time horse race betting. alderac.com/ready-set-bet/ Everything you need to play Ready Set Bet is already in the box, but there is an app av", "headingPath": "You're off to the races in Ready Set Bet! · Ready Set Bet App: · Gameplay Overview", "sharpsignalDocId": 493}, {"page": 3, "score": 0.046875, "snippet": "1 Place the Bet Board in the center of the table. 2 Shuffle the Prop Bet Cards and place the deck face-down on the Prop Bets space at the top of the Bet Board. Then draw the top 5 cards from the deck and place them face-up on the blank spaces to the right. 3 Shuffle the Exotic Finish Cards and place", "headingPath": "Setup", "sharpsignalDocId": 493}, {"page": 4, "score": 0.032258, "snippet": "Running a Race · The House player begins the horse race. Placing Bets · Players place bets during the race. Resolving Bets · At the end of the race, players resolve their bets. Cleanup · Take care of all cards and reset the race track. The player acting as the House can simply facilitate the game by", "headingPath": "Round Overview · Running a Race · Bonus Moves", "sharpsignalDocId": 493}, {"page": 5, "score": 0.031746, "snippet": "Each non-House player has a set of Bet Tokens numbered 2, 3, 3, 4, and 5, which they can use to place bets in each race. (In a 7-player or 8-player game, each non-House player has one fewer 3 Bet Token.) While a race is in progress-and BEFORE 'No more bets!' is called or a horse reaches the finish l", "headingPath": "Placing Bets", "sharpsignalDocId": 493}, {"page": 5, "score": 0.030769, "snippet": "The violet player may NOT place multiple tokens on the same spot. The violet player may NOT place a token where another player’s token is already placed. 5 The violet player collects their 5 Bet Token. If the 2/3 horse won: They collect $45 (9 x 5) in money chips from the supply. If the 2/3 horse di", "headingPath": "", "sharpsignalDocId": 493}, {"page": 2, "score": 0.030415, "snippet": "Risky Gambler Risky Gambler For each winning bet you placed, gain $2 from the supply. For each losing bet you placed, pay $1 to the supply. PROP BET S PROP BET S 2/3 8 -34x SHOW PLACE2nd SHOW PLACE WIN 1st READY SETBETREADY SETBET • JOHN D CLAIR •• JOHN D CLAIR • TMTM 1 2 3 4 5 6 7 8 9 10 11 12 13 1", "headingPath": "", "sharpsignalDocId": 493}, {"page": 5, "score": 0.030303, "snippet": "At the end of a race, all players gain or lose money for their winning or losing bets. Players should first collect all their winning Bet Tokens from the Bet Board along with the corresponding payouts from the supply of money chips. Then players should collect all their losing Bet Tokens and pay the", "headingPath": "Resolving Bets", "sharpsignalDocId": 493}, {"page": 6, "score": 0.029851, "snippet": "8 9 Players can bet on horses to Win, Place, or Show by placing a Bet Token on the corresponding Bet Spot. The rows correspond to the different horse numbers, while the columns correspond to the different bets of Show, Place, or Win: WIN is a bet that a horse will finish in 1st place . There are thr", "headingPath": "Resolving Bets · Win, Place, and Show Bets", "sharpsignalDocId": 493}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "You're off to the races in Ready Set Bet! · Ready Set Bet App: · Gameplay Overview", "sharpsignalDocId": 493}, {"page": 3, "quote": null, "headingPath": "Setup", "sharpsignalDocId": 493}, {"page": 4, "quote": null, "headingPath": "Round Overview · Running a Race · Bonus Moves", "sharpsignalDocId": 493}, {"page": 5, "quote": null, "headingPath": "", "sharpsignalDocId": 493}, {"page": 5, "quote": null, "headingPath": "Resolving Bets", "sharpsignalDocId": 493}, {"page": 7, "quote": null, "headingPath": "Bonus Bet Tokens · Game End", "sharpsignalDocId": 493}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 493 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 493 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.90515 of 2309 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 28, 2026 11:53 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 Ready Set Bet — Rulebook (corpus doc 493)	You're off to the races in Ready Set Bet! · Ready Set Bet App: · Gameplay Overview	p.2	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Setup	p.3	0.046875 (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 Ready Set Bet — Rulebook (corpus doc 493)	Round Overview · Running a Race · Bonus Moves	p.4	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
#4	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Placing Bets	p.5	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
#5	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)		p.5	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
#6	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)		p.2	0.030415 (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 Ready Set Bet — Rulebook (corpus doc 493)	Resolving Bets	p.5	0.030303 (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 Ready Set Bet — Rulebook (corpus doc 493)	Resolving Bets · Win, Place, and Show Bets	p.6	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 18 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 Ready Set Bet — Rulebook (corpus doc 493)	Setup	p.3	#2	0.046875 (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 Ready Set Bet — Rulebook (corpus doc 493)	You're off to the races in Ready Set Bet! · Ready Set Bet App: · Gameplay Overview	p.2	#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
#3	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Bonus Bet Tokens · Game End	p.7	#13	0.013889 (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
#4	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)		p.5	#5	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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Resolving Bets · Win, Place, and Show Bets	p.6	#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
#6	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	House Bets Variant · App Variant · Credits · House Rotation Variant	p.8	#10	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 Ready Set Bet — Rulebook (corpus doc 493)	Round Overview · Running a Race · Bonus Moves	p.4	#3	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
#8	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Resolving Bets	p.5	#7	0.030303 (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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	You're off to the races in Ready Set Bet! · Ready Set Bet App: · Gameplay Overview	p.2	no quote on the wire
[2]	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Setup	p.3	no quote on the wire
[3]	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Round Overview · Running a Race · Bonus Moves	p.4	no quote on the wire
[4]	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)		p.5	no quote on the wire
[5]	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Resolving Bets	p.5	no quote on the wire
[6]	RULEBOOK Ready Set Bet — Rulebook (corpus doc 493)	Bonus Bet Tokens · Game End	p.7	no quote on the wire

generation — timing and the path taken

timing split: retrieval 94 ms · first delta 2066 ms · total 5792 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 94 ms · ask 5696 ms · gateway work 5792 ms · total 5792 ms
tokens in (the prompt the answerer read): 3755
tokens out (what the answerer generated): 734
tok/sec: 199.8 tok/sec — 734 output tokens in 3.674 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 7s ago)
answerer host (measured by rulesage): reachable (for 22h, 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 424), 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.