RuleSage cited table rulings
← Jaipur

You asked

How do I play?

Answered counted as answered

Asked with: Jaipurbg-54043-en-1e

To play Jaipur, follow these steps:
Setup
1. Sort tokens by goods type into piles in descending order of value, spreading them so both players can see all values.[1]
2. Sort bonus tokens by type, shuffle each type separately, and form 3 piles.[1]
3. Place the camel token next to the bonus tokens.[1]
4. Place 3 camel cards faceup between the players.[2]
5. Shuffle the remaining cards and deal 5 cards to each player.[2]
6. Place the remaining cards facedown as a draw pile (deck).[2]
7. Fill the market to 5 cards by drawing 2 cards from the deck and placing them faceup next to the camels.[2]
8. Players remove any camels from their hands and place them faceup in a stack in front of them to form their herd.[2]
9. Pick a starting player.[1]
Game Turn
On your turn, you must choose one of the following actions, but never both:[1]
Option 1: Take Cards
You must choose one of these three specific options:[3][4]
1. Take 1 single good: Take a single goods card from the market into your hand, then replace it with the top card of the deck.[3]
2. Take several goods (the EXCHANGE option): Take all the goods cards you want into your hand (they can be different types), then exchange the same number of cards.[3][4] The returned cards can be camels, goods, or a combination of the two, but you cannot exchange just 1 card for 1 (2 or more are required) and the same goods type cannot be both taken from and returned to the market.[3][5]
3. Take all the camels: Take all the camels from the market and add them to your herd.[3]
*Note: When taking cards, you may take goods or camels, but never both.[5] Players may never have more than 7 cards in their hands at the end of their turn, though camels do not count toward this limit.[3][5] *
Option 2: Sell Cards
1. Choose one type of goods and discard as many cards of that type as you like into the discard pile.[6]
2. Take one token for each card sold, starting with the highest values first, and stack them in front of you.[6]
3. If you sell 3 or more cards, take the corresponding bonus token.[6]
4. If selling the 3 most expensive goods (silver, diamonds, gold), the sale must include a minimum of 2 cards.[6]
5. You can only sell one goods type each round.[6]
Ending a Round and the Game
1. A round ends when both players have taken an action.[1]
2. The player with the most camels in their herd receives the camel token (worth 5 rupees); if both players have the same number, neither takes it.[7][5]
3. Players flip their tokens over and add them up to determine the richest trader.[7]
4. The richest trader receives a Seal of Excellence; in a tie, the seal goes to the player with the most bonus tokens, or if still tied, the player with the most goods tokens.[7]
5. If neither player has 2 Seals of Excellence, play another round, with the player who lost the previous round starting.[7]
6. The game ends when a player collects 2 Seals of Excellence, making them the winner.[2][7]
[1] RULEBOOK Jaipur — Rulebook · p.3 · SETUP · GAME TURN
[2] RULEBOOK Jaipur — Rulebook · p.2 · INTRODUCTION AND AIM OF THE GAME · SETUP
[3] RULEBOOK Jaipur — Rulebook · p.4
[4] RULEBOOK Jaipur — Rulebook · p.4 · TAKE CARDS · B: Take several goods · IMPORTANT
[5] RULEBOOK Jaipur — Rulebook · p.7 · REMINDERS AND NOTES · NB: It is best to read this after your first game.
[6] RULEBOOK Jaipur — Rulebook · p.5 · SELL CARDS · 2 · Restrictions during a sale
[7] RULEBOOK Jaipur — Rulebook · p.6 · A round ends immediately if: · NEW ROUND · END OF THE GAME

So says the rulebook. So plays the table.

🔧 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 83 ms · ask 5017 ms · total 5102 ms
single-flight (PR-5)
queued 0 ms · generation 5102 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 3, "score": 0.04918, "snippet": "Sort the tokens by goods type. Make a pile for each goods type in descending order of value. Spread each pile, as depicted above, so that both players can see all the token values. Sort the bonus tokens by type ( , , ). Shuffle each type separately, then form 3 piles (not spread out). Place the came", "headingPath": "SETUP · GAME TURN", "sharpsignalDocId": 187}, {"page": 6, "score": 0.04598, "snippet": "The player with the most camels in their herd receives the camel token , which is worth 5 rupees. The players turn over their tokens and add them up to determine who is the richest. NB: We suggest that you make piles of 10 rupees as these are easier for children to count, and quicker for adults, as ", "headingPath": "A round ends immediately if: · NEW ROUND · END OF THE GAME", "sharpsignalDocId": 187}, {"page": 4, "score": 0.032258, "snippet": "If you take cards, you must choose one of the following options: take 1 single good, take several goods (=the EXCHANGE option), take all the camels. These 3 options are shown in detail below. Take all the goods cards that you want into your hand (they can be of different types) , then... Players may", "headingPath": "TAKE CARDS · B: Take several goods · IMPORTANT", "sharpsignalDocId": 187}, {"page": 2, "score": 0.031746, "snippet": "In Jaipur, you are hoping to become the Maharaja's personal trader by amassing more riches than your opponent at the end of each week (round) . To do so, collect and exchange goods (cards) at the market, then sell them for rupees (flip the tokens over) . If you manage to arrange a larger sale (3 car", "headingPath": "INTRODUCTION AND AIM OF THE GAME · SETUP", "sharpsignalDocId": 187}, {"page": 4, "score": 0.03125, "snippet": "Herd If you take cards, you must choose one of the following options: A. take 1 single good, B. take several goods (=the EXCHANGE option), C. take all the camels. Take all the goods cards that you want into your hand (they can be of different types), then... ... exchange the same number of cards. Th", "headingPath": "", "sharpsignalDocId": 187}, {"page": 5, "score": 0.030769, "snippet": "To sell cards, choose one type of goods and discard as many cards of that type as you like into the discard pile. Each sale yields goods tokens and, if the sale is big enough, a bonus. A sale is carried out in 3 steps. Take one token for each card you sold starting with the top of the corresponding ", "headingPath": "SELL CARDS · 2 · Restrictions during a sale", "sharpsignalDocId": 187}, {"page": 7, "score": 0.030303, "snippet": "When you take cards from the market, you either take goods or camels, but never both. If you decide to take camels, you must always take all the camels from the market. When making an exchange: the returned cards can be camels, goods, or a mixture of the two ; the same goods type cannot be both take", "headingPath": "REMINDERS AND NOTES · NB: It is best to read this after your first game.", "sharpsignalDocId": 187}, {"page": 8, "score": 0.029412, "snippet": "My, oh, my, how time flies! The last decade passed in the blink of an eye. I remember the first ideas that led to Jaipur very well: it all started with the desire of a fast barter phase (hence a 'neutral' central market). I eventually kept it to a 2-player game, for it is in such a configuration tha", "headingPath": "Sébastien Pauchon · Vincent Dutrait · CONTACT INFORMATION", "sharpsignalDocId": 187}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 3, "quote": null, "headingPath": "SETUP · GAME TURN", "sharpsignalDocId": 187}, {"page": 2, "quote": null, "headingPath": "INTRODUCTION AND AIM OF THE GAME · SETUP", "sharpsignalDocId": 187}, {"page": 4, "quote": null, "headingPath": "", "sharpsignalDocId": 187}, {"page": 4, "quote": null, "headingPath": "TAKE CARDS · B: Take several goods · IMPORTANT", "sharpsignalDocId": 187}, {"page": 7, "quote": null, "headingPath": "REMINDERS AND NOTES · NB: It is best to read this after your first game.", "sharpsignalDocId": 187}, {"page": 5, "quote": null, "headingPath": "SELL CARDS · 2 · Restrictions during a sale", "sharpsignalDocId": 187}, {"page": 6, "quote": null, "headingPath": "A round ends immediately if: · NEW ROUND · END OF THE GAME", "sharpsignalDocId": 187}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 187 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 187 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.89086 of 2419 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded
Aug 26, 2026 14:32 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 Jaipur — Rulebook (corpus doc 187) SETUP · GAME TURN p.3 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) 300
#2 RULEBOOK Jaipur — Rulebook (corpus doc 187) A round ends immediately if: · NEW ROUND · END OF THE GAME p.6 0.04598 (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 Jaipur — Rulebook (corpus doc 187) TAKE CARDS · B: Take several goods · IMPORTANT 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 Jaipur — Rulebook (corpus doc 187) INTRODUCTION AND AIM OF THE GAME · SETUP p.2 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 Jaipur — Rulebook (corpus doc 187) p.4 0.03125 (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 Jaipur — Rulebook (corpus doc 187) SELL CARDS · 2 · Restrictions during a sale 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
#7 RULEBOOK Jaipur — Rulebook (corpus doc 187) REMINDERS AND NOTES · NB: It is best to read this after your first game. p.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)) 300
#8 RULEBOOK Jaipur — Rulebook (corpus doc 187) Sébastien Pauchon · Vincent Dutrait · CONTACT INFORMATION p.8 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)) 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 8 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 Jaipur — Rulebook (corpus doc 187) SETUP · GAME TURN p.3 #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
#2 RULEBOOK Jaipur — Rulebook (corpus doc 187) INTRODUCTION AND AIM OF THE GAME · SETUP p.2 #4 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 Jaipur — Rulebook (corpus doc 187) p.4 #5 0.03125 (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 Jaipur — Rulebook (corpus doc 187) SELL CARDS · 2 · Restrictions during a sale p.5 #6 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 Jaipur — Rulebook (corpus doc 187) Sébastien Pauchon · Vincent Dutrait · CONTACT INFORMATION p.8 #8 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
#6 RULEBOOK Jaipur — Rulebook (corpus doc 187) REMINDERS AND NOTES · NB: It is best to read this after your first game. p.7 #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
#7 RULEBOOK Jaipur — Rulebook (corpus doc 187) A round ends immediately if: · NEW ROUND · END OF THE GAME p.6 #2 0.04598 (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 Jaipur — Rulebook (corpus doc 187) TAKE CARDS · B: Take several goods · IMPORTANT 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

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 Jaipur — Rulebook (corpus doc 187) SETUP · GAME TURN p.3 no quote on the wire
[2] RULEBOOK Jaipur — Rulebook (corpus doc 187) INTRODUCTION AND AIM OF THE GAME · SETUP p.2 no quote on the wire
[3] RULEBOOK Jaipur — Rulebook (corpus doc 187) p.4 no quote on the wire
[4] RULEBOOK Jaipur — Rulebook (corpus doc 187) TAKE CARDS · B: Take several goods · IMPORTANT p.4 no quote on the wire
[5] RULEBOOK Jaipur — Rulebook (corpus doc 187) REMINDERS AND NOTES · NB: It is best to read this after your first game. p.7 no quote on the wire
[6] RULEBOOK Jaipur — Rulebook (corpus doc 187) SELL CARDS · 2 · Restrictions during a sale p.5 no quote on the wire
[7] RULEBOOK Jaipur — Rulebook (corpus doc 187) A round ends immediately if: · NEW ROUND · END OF THE GAME p.6 no quote on the wire
timing split
retrieval 83 ms · first delta 1266 ms · total 5102 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 83 ms · ask 5017 ms · gateway work 5102 ms · total 5102 ms
tokens in (the prompt the answerer read)
2482
tokens out (what the answerer generated)
770
tok/sec
203.0 tok/sec — 770 output tokens in 3.794 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 15s ago)
answerer host (measured by rulesage)
reachable (for 22h, checked 4s 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 105), 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.