You asked
How do I setup the game?
Answered counted as answered1. Place the game board in the middle of the table [1]. 2. Sort the betting tickets by color (5 colors in total) [1]. 3. Stack the 4 tickets of each color by placing both 1-Pound tickets on the bottom, the 2-Pound ticket on top of them, and the 3-Pound ticket on the very top [1]. 4. Place each stack onto its matching ticket tent on the game board [1]. 5. Place the 5 pyramid tickets as a stack onto their space on the game and board [1]. 6. Sort the Egyptian Pound coins by value and place them as a supply next to the game board (the "bank") [1]. 7. Give each player 3 Egyptian Pounds to place in front of them [1]. 8. Give each player the 5 finish cards of one character and their character's spectator tile [1]. 9. Each player keeps their hand of five cards hidden from other players and places their spectator tile in front of them [1]. 10. In games with 6 or more players, give each player his character's partnership card and place it in front of him with its “available” side face up; return any spare partnership cards to the box [1]. (In games with fewer than 6 players, leave the partnership cards in the box) [1]. 11. To determine the starting positions of the 5 racing camels, roll the 5 racing dice together once and place each racing camel onto the race track as indicated by the dice [1][2]. 12. Stack all camels standing on the same space (in any order) and ensure they all face clockwise [1][2]. 13. To determine the starting positions of the 2 crazy camels (black and white), roll the grey die [1]. 14. Take either of the two crazy camels and place it onto the track as indicated by the number rolled: 1 = space 16, 2 = space 15, or 3 = space 14 [2]. 15. Roll the grey die again and place the second crazy camel in the same way; if it lands on the same space as the first, put the second camel on top of the first [2]. 16. Ensure the crazy camels face counterclockwise [2]. 17. Give the starting player marker to the youngest player [2].
🔧 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 203 ms · ask 12142 ms · total 12355 ms
- single-flight (PR-5)
- queued 0 ms · generation 12355 ms
- retrieval refs (raw)
- [{"page": 1, "score": 0.016393, "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": 1, "score": 0.016129, "snippet": "Then place each racing camel onto the race track as indicated by the dice: Finally, stack all camels standing on the same space (in any order) and make sure they all face clockwise (as this is the direction the race is run). 8.8. Now determine the starting positions of the 2 crazy camels (black and ", "headingPath": "", "sharpsignalDocId": 181}, {"page": 3, "score": 0.015873, "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": 4, "score": 0.015625, "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": 2, "score": 0.015385, "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": 5, "score": 0.015152, "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": 4, "score": 0.014925, "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": 4, "score": 0.014706, "snippet": "Now, each player gains or loses Egyptian Pounds according to the tickets in front of him, by adding up his total and then taking it from (or paying it to) the bank accordingly. 8 5 3 2 1 -1 For each betting ticket of the leading racing camel, the player gains the number of Egyptian Pounds printed in", "headingPath": "remember: The crazy camels are entirely ignored for the ranking.", "sharpsignalDocId": 181}]
- citations (raw)
- [{"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 181}, {"page": 1, "quote": null, "headingPath": "", "sharpsignalDocId": 181}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
- 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 1, 2026 05:44
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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) | p.1 | 0.016393 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 | |
| #2 | RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) | p.1 | 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 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.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #4 | 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.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #5 | RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) | take 1 Betting ticket · the legs · IMPORTANT: · end of the game · money | p.2 | 0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #6 | 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.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #7 | RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) | end of the game · Example: | p.4 | 0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #8 | RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) | remember: The crazy camels are entirely ignored for the ranking. | p.4 | 0.014706 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
chosen chunks — what the answer actually cited
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.
| # | document | heading | page | quote chars |
|---|---|---|---|---|
| [1] | RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) | p.1 | no quote on the wire | |
| [2] | RULEBOOK Camel Up (Second Edition) — Rulebook (corpus doc 181) | p.1 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 203 ms · first delta 8524 ms · total 12355 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 203 ms · ask 12142 ms · gateway work 12355 ms · total 12355 ms
- tokens in (the prompt the answerer read)
- 4549
- tokens out (what the answerer generated)
- 519
- tok/sec
- 136.9 tok/sec — 519 output tokens in 3.792 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 10s 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
- NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
- pattern that matched
- SETUP — "setup" / "set up"
- matched words (in the normalized question)
-
setup
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.