RuleSage cited table rulings
← Sabika

You asked

How do I play?

Answered counted as answered

Asked with: Sabikabg-360265-en-1e

A game of Sabika takes place over 5 rounds, consisting of an Actions Phase and an End of Round Phase.[1] The game follows all usual phases (Actions, End of Round, and End of Game).[2]
Actions Phase
1. Starting with the player who holds the Starting Player Token and proceeding clockwise, each player plays their turn.[3]
2. Choose one active Worker (a Worker is active when standing) from either a Rondel or your Workshop.[3]
3. Decide whether the chosen Worker will Work or Rest.[3]
4. If the Worker is to Work:
* Move the chosen Worker in a clockwise direction around its corresponding Rondel, ending on a square.[4]
* If the Worker is in your Workshop, you may place them directly on a square in the corresponding Rondel for free.[4]
* Moving 1 or 2 steps is free, but each additional step after the second costs 1 Dinar.[4]
* You may pay 1 Dinar for each Worker of another player (including Sultan's Workers in 1-3 player games) present on the destination square.[4]
* Lay the Worker down to indicate they are now inactive.[4]
* Carry out the Main Action and/or a Secondary Action of the square where the Worker is located (you must be able to carry out at least one).[4]
5. If the Worker is to Rest:
* Place the chosen Worker on the corresponding space in your Workshop and lay them down to indicate they are inactive.[4]
* Earn 3 Dinars and lose 1 PP.[4]
* Note: You must Rest if you cannot carry out any action.[4]
6. Once the chosen action is completed, play passes to the next player in clockwise order.[3][4]
7. The Action Phase ends when a player has no active Workers remaining (all are lying down).[3]
End of Round Phase
The play passes to the End of Round Phase.[4]
[1] RULEBOOK Sabika — Rulebook · p.8 · Prestige points · How to play · Phase 1. Actions
[2] RULEBOOK Sabika — Rulebook · p.19 · The events · Game setup · Main board setup · Each player · Finally: · How to play
[3] RULEBOOK Sabika — Rulebook · p.9 · Phase 1. Actions
[4] RULEBOOK Sabika — Rulebook · p.9 · Work · Rest

One rule clearer, zero feelings hurt.

🔧 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 106 ms · ask 4818 ms · total 7342 ms
single-flight (PR-5)
queued 2416 ms · generation 4926 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
[{"page": 19, "score": 0.047938, "snippet": "Take on the automa Yusuf, another Nasrid nobleman who will compete against you for prestige and prominence in the history of the Kingdom of Granada. Setup a game as if for 2 players, with the following exceptions: Before placing the major Poems on the board, remove Card F1 from the game. Yusuf takes", "headingPath": "The events · Game setup · Main board setup · Each player · Finally: · How to play", "sharpsignalDocId": 1030}, {"page": 9, "score": 0.047619, "snippet": "Outer Rondel: Focuses on the construction of the Alhambra. Each player has 2 Workers in this Rondel, called Master Builders. Middle Rondel: Focuses on the procurement and processing of Raw Materials for export as Goods to the Cities on the Map. Each player has 1 Worker in this Rondel, called a Merch", "headingPath": "Phase 1. Actions", "sharpsignalDocId": 1030}, {"page": 16, "score": 0.045335, "snippet": "The Sultan's Wishes in the game are as follows: All players stand their workers back up, including those in their Workshop, thus restoring them to their active state. Then move all the Sultan's Workers 1 step clockwise (these Workers are always standing). In a 4-player game there are no Sultan's Wor", "headingPath": "The Sultan's Wishes · Reactivating workers · Maintenance · Starting player · Era change · End of game", "sharpsignalDocId": 1030}, {"page": 19, "score": 0.044776, "snippet": "When it is his turn to play, Yusuf must reveal the top Worker Tile of his pile: this Tile will show which of his Workers to activate. Revealed Tiles remain face up until the End of Round, at which point the Draw Pile is reformed. Next, Yusuf reveals the top Card of the corresponding Worker Deck show", "headingPath": "Phase 1. Action · Movement · Special cases:", "sharpsignalDocId": 1030}, {"page": 5, "score": 0.032258, "snippet": "Therefore, in a 4-player game there will be 5 Minor Poems available. K. Shuffle the Major Poem Cards and draw 2 for each player in the game (4/6/8 Major Poems for 2/3/4 players), keeping in mind that each Major Poem must have a different letter. If you draw a letter which you already have, discard i", "headingPath": "Main board setup", "sharpsignalDocId": 1030}, {"page": 5, "score": 0.030769, "snippet": "E. Place the Narrator Token on the first space of the Round T rack. F. Shuffle the Sultan's Wishes Tiles face down, choose 3 Tiles, one Tile of each letter (A, B and C), and randomly place one Tile on each of the spaces of the Round Track outlined by the dotted lines. Remove the remaining Sultan's W", "headingPath": "Main board setup", "sharpsignalDocId": 1030}, {"page": 5, "score": 0.030303, "snippet": "Each player must choose a colour and take: N. 1 Workshop, 4 Starting Storehouses (placed on the corresponding spaces of the Workshop) and one randomly selected Architectural Balance Card (placed above the Workshop). O. The 4 Workers of their colour: 2 Master Builders, 1 Merchant and 1 Poet which are", "headingPath": "Player setup · Overview and objective", "sharpsignalDocId": 1030}, {"page": 9, "score": 0.030118, "snippet": "Complete the following steps in order: Move the chosen Worker, always in a clockwise direction , around its corresponding Rondel , ending its movement on a square. You may then carry out a Main and/or Secondary Action. In the case of the Outer Rondel, your 2 Master Builders can never occupy the same", "headingPath": "Work · Rest", "sharpsignalDocId": 1030}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
[{"page": 8, "quote": null, "headingPath": "Prestige points · How to play · Phase 1. Actions", "sharpsignalDocId": 1030}, {"page": 19, "quote": null, "headingPath": "The events · Game setup · Main board setup · Each player · Finally: · How to play", "sharpsignalDocId": 1030}, {"page": 9, "quote": null, "headingPath": "Phase 1. Actions", "sharpsignalDocId": 1030}, {"page": 9, "quote": null, "headingPath": "Work · Rest", "sharpsignalDocId": 1030}]
boost provenance — errata + base rulebook (E2/E3)
no registered errata card matched this query; base rulebook doc 1030 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1030 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.89727 of 1392 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded
Sep 7, 2026 02:58 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 Sabika — Rulebook (corpus doc 1030) The events · Game setup · Main board setup · Each player · Finally: · How to play p.19 0.047938 (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 Sabika — Rulebook (corpus doc 1030) Phase 1. Actions p.9 0.047619 (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 Sabika — Rulebook (corpus doc 1030) The Sultan's Wishes · Reactivating workers · Maintenance · Starting player · Era change · End of game p.16 0.045335 (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 Sabika — Rulebook (corpus doc 1030) Phase 1. Action · Movement · Special cases: p.19 0.044776 (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 Sabika — Rulebook (corpus doc 1030) Main board setup p.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)) 300
#6 RULEBOOK Sabika — Rulebook (corpus doc 1030) Main board setup 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 Sabika — Rulebook (corpus doc 1030) Player setup · Overview and objective 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 Sabika — Rulebook (corpus doc 1030) Work · Rest p.9 0.030118 (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 46 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 Sabika — Rulebook (corpus doc 1030) Rondel setup p.5 #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
#2 RULEBOOK Sabika — Rulebook (corpus doc 1030) The events · Game setup · Main board setup · Each player · Finally: · How to play p.19 #1 0.047938 (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
#3 RULEBOOK Sabika — Rulebook (corpus doc 1030) Prestige points · How to play · Phase 1. Actions p.8 #12 0.028571 (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
#4 RULEBOOK Sabika — Rulebook (corpus doc 1030) Main board setup 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 Sabika — Rulebook (corpus doc 1030) Phase 1. Actions p.9 #2 0.047619 (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
#6 RULEBOOK Sabika — Rulebook (corpus doc 1030) Videotutorials p.24 #13 0.028405 (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
#7 RULEBOOK Sabika — Rulebook (corpus doc 1030) Phase 1. Action · Movement · Special cases: p.19 #4 0.044776 (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 Sabika — Rulebook (corpus doc 1030) Work · Rest p.9 #8 0.030118 (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

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 Sabika — Rulebook (corpus doc 1030) Prestige points · How to play · Phase 1. Actions p.8 no quote on the wire
[2] RULEBOOK Sabika — Rulebook (corpus doc 1030) The events · Game setup · Main board setup · Each player · Finally: · How to play p.19 no quote on the wire
[3] RULEBOOK Sabika — Rulebook (corpus doc 1030) Phase 1. Actions p.9 no quote on the wire
[4] RULEBOOK Sabika — Rulebook (corpus doc 1030) Work · Rest p.9 no quote on the wire
timing split
retrieval 106 ms · first delta 2664 ms · total 7342 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown
queued 2416 ms · retrieval 106 ms · ask 4818 ms · gateway work 4926 ms · total 7342 ms
tokens in (the prompt the answerer read)
3077
tokens out (what the answerer generated)
442
tok/sec
201.2 tok/sec — 442 output tokens in 2.197 s of generation
live seat (read from the running child)
answering — gemma4:26b think:false · num_ctx 32768 (live-verified 49s ago)
answerer host (measured by rulesage)
reachable (for 22h, checked 0s 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 960), 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.