Ruling — Camel Up (Second Edition)

You asked

How do I take my turn?

Answered counted as answered

Asked with: Camel Up (Second Edition)bg-260605-en-1e

When it is your turn, you must choose and perform 1 of 4 possible actions [1]: 1. Take the top betting ticket from any stack on the game board to back the camel of that color [2][1]. 2. Take 1 pyramid ticket and use the pyramid to move a camel [2]. 3. Bet on the overall winner or the overall loser by placing 1 of your finish cards face down onto the appropriate betting space [2][3]. 4. Place your spectator tile onto an empty space of the race track (that has no camels or spectator tile on it), provided it is not adjacent to another spectator tile and not on space 1 [4]. If your spectator tile is already on the board, you may use this action to move it to a different space [4]. In games with 6 or more players, a 5th possible action is available: * Enter into a betting partnership: If your partnership card is face up with the "available" side, you can choose another player who also has their card "available." You exchange cards so that both cards are placed in front of you with the "partnership" side face up [5]. Play proceeds continuously in a clockwise direction, starting with the player holding the starting player marker [1].

[1] RULEBOOK Camel Up (Second Edition) — Rulebook · p.2 · OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME

[2] RULEBOOK Camel Up (Second Edition) — Rulebook · p.2 · take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money

[3] RULEBOOK Camel Up (Second Edition) — Rulebook · p.4 · spectator tiles · Bet on the overall winner or the overall loser · end of a leg

[4] RULEBOOK Camel Up (Second Edition) — Rulebook · p.3 · place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:

[5] RULEBOOK Camel Up (Second Edition) — Rulebook · p.5 · ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 374 ms · ask 5752 ms · total 6136 ms
single-flight (PR-5): queued 0 ms · generation 6136 ms
retrieval refs (raw): [{"page": 4, "score": 0.04918, "snippet": "8 5 3 2 1 -1 8 5 3 2 5 3 2 As your action, you can bet on the overall winner. This means you secretly back the racing camel that you believe will be in the lead at the end of the game. To do this, secretly choose 1 of your finish cards (in the color of the camel you think will win) and put it face d", "headingPath": "spectator tiles · Bet on the overall winner or the overall loser · end of a leg", "sharpsignalDocId": 181}, {"page": 5, "score": 0.047883, "snippet": "In games with 6 or more players, each player also has a partnership card in front of him. On his turn, a player can now choose to perform a 5 th possible action called 'Enter into a betting partnership'. You can only perform this action if you have your partnership card with the 'available' side fac", "headingPath": "ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5", "sharpsignalDocId": 181}, {"page": 3, "score": 0.047123, "snippet": "Place your spectator tile onto an empty space of the race track (that has no camels or spectator tile on it). However, you are not allowed to place it onto a space that is adjacent to a space containing a spectator tile. Also, you may never place it onto space 1 of the race track. If your spectator ", "headingPath": "place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:", "sharpsignalDocId": 181}, {"page": 2, "score": 0.031746, "snippet": "Take the top betting ticket from any stack on the game board and place it in front of you. By doing this, you back the camel of that color (which means that you hope it will be in the lead at the end of the leg). There is no limit to the number of betting tickets you may collect throughout the leg. ", "headingPath": "take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money", "sharpsignalDocId": 181}, {"page": 4, "score": 0.030769, "snippet": "As soon as any camel unit crosses the fi nish line , the race ends immediately (even if a crazy camel crosses the finish line in a counterclockwise direction). Now, carry out one more leg scoring round (as described on the left). Next, the end of game scoring round for the overall winner and overall", "headingPath": "end of the game · Example:", "sharpsignalDocId": 181}, {"page": 2, "score": 0.030415, "snippet": "8 8 5 3 5 3 8 8 This overview describes important basics of the game. Detailed rules will follow in the section 'Playing the game'. 2 1 8 5 5 3 5 3 -1 3 2 1 -1 3 2 1 -1 2 1 2 1 -1 The 5 racing camels do not belong to any player. Instead each player can bet on any of them throughout the race by acqui", "headingPath": "OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME", "sharpsignalDocId": 181}, {"page": 1, "score": 0.030303, "snippet": "8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 1.1. Place the game board in the middle of the table. 2.2. Sort the betting tickets by color (5 colors in total). Then stack the 4 tickets of each color in the following manner: Place both -Pound ", "headingPath": "", "sharpsignalDocId": 181}, {"page": 3, "score": 0.029851, "snippet": "1 -1 8 5 3 2 1 -1 8 5 3 2 1 -1 8 5 If a camel unit ends its movement on a space with a spectator tile, the owner of that tile immediately receives 1 Egyptian Pound from the bank. Also (depending on which side of the tile is facing up) the camel unit must immediately move 1 additional space forward o", "headingPath": "spectator tiles", "sharpsignalDocId": 181}]
citations (raw): [{"page": 2, "quote": null, "headingPath": "OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME", "sharpsignalDocId": 181}, {"page": 2, "quote": null, "headingPath": "take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money", "sharpsignalDocId": 181}, {"page": 4, "quote": null, "headingPath": "spectator tiles · Bet on the overall winner or the overall loser · end of a leg", "sharpsignalDocId": 181}, {"page": 3, "quote": null, "headingPath": "place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:", "sharpsignalDocId": 181}, {"page": 5, "quote": null, "headingPath": "ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5", "sharpsignalDocId": 181}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 181 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 181 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)
debug row retained until: Nov 2, 2026 08:48

retrieval — what the search arm returned

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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	spectator tiles · Bet on the overall winner or the overall loser · end of a leg	p.4	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5	p.5	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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:	p.3	0.047123 (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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money	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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	end of the game · Example:	p.4	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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME	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 Camel Up (Second Edition) — Rulebook (corpus doc 181)		p.1	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 Camel Up (Second Edition) — Rulebook (corpus doc 181)	spectator tiles	p.3	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	OVERVIEW · 8 5 the racing camels · Camel stack: · Camel unit: · the crazy camels · PLAYING THE GAME	p.2	no quote on the wire
[2]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money	p.2	no quote on the wire
[3]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	spectator tiles · Bet on the overall winner or the overall loser · end of a leg	p.4	no quote on the wire
[4]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	place your spectator tile 2 · take 1 pyramid ticket 3 · how to use the pyramid · Example:	p.3	no quote on the wire
[5]	RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181)	ADDITIONAL RULES IN GAMES WITH 6 OR MORE PLAYERS · enter into a Betting partnership 5	p.5	no quote on the wire

generation — timing and the path taken

timing split: retrieval 374 ms · first delta 4092 ms · total 6136 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 374 ms · ask 5752 ms · gateway work 6136 ms · total 6136 ms
tokens in (the prompt the answerer read): 4549
tokens out (what the answerer generated): 270
tok/sec: 136.2 tok/sec — 270 output tokens in 1.983 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 13s 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 99), 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.