Ruling — Ankh: Gods of Egypt

You asked

How do I setup the game?

Answered counted as answered

Asked with: Ankh: Gods of Egyptbg-285967-en-1e

1. Randomly determine a first player or assign it to the player who owns the most cats.[1]

2. Other players follow in clockwise seating order around the table.[1]

3. In reverse player order, starting with the last player, each player places their plastic Ankh token on the bottom space of the Devotion track, forming a stack so that the first player's Ankh token is on top.[1]

4. Place the 4 Action markers on the Action tracks of the central dashboard in the starting spaces matching the number of players in the game.[1]

5. Place the Event marker on the first space of the Events track.[1]

6. Choose a scenario from the scenario book (either agreed upon by all players or picked randomly) and ensure it is possible with the number of players.[1]

7. Place Monuments (Pyramids, Temples, and Obelisks), Conflict Order tokens, and Camels on the board as shown in the scenario setup diagram (not all scenarios require camels).[1]

8. Set the remaining Monuments, Conflict Order tokens, Battle Tiebreaker token, and Camels aside in the general supply.[1]

9. Place your figures and Ankh tokens (on your controlled Monuments) on the board as shown in the scenario setup, where the first player is player #1, the player to their left is player #2, and so on.[1]

10. Choose one Level 1, one Level 2, and one Level 3 Guardian card and place them near the game board.[1]

11. Place a number of Guardian figures next to the cards according to the number of players: 1 or 2 players use 1 figure of each type; 3 players use 2 figures of each type; 4 or 5 players use all available figures of each type (3 for small-base and 2 for large-base).[1]

12. Follow any Additional Setup Rules as dictated in the scenario book.[2][1]

[1] RULEBOOK Ankh: Gods of Egypt — Rulebook · p.13 · BATTLE CARDS

[2] RULEBOOK Ankh: Gods of Egypt — Rulebook · p.13 · BATTLE CARDS

🔧 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 218 ms · ask 13143 ms · total 13371 ms
single-flight (PR-5): queued 0 ms · generation 13371 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 9, "score": 0.048652, "snippet": "During the game, players take turns performing actions including moving their figures on the board to seize control of key territory, summoning Warriors and Guardians to battle their opponents, gaining new Followers, and unlocking new Ankh powers. The 4 possible actions are depicted on the top half ", "headingPath": "CENTRAL DASHBOARD", "sharpsignalDocId": 358}, {"page": 13, "score": 0.047938, "snippet": "Randomly determine a first player (or assign it to the player who owns the most cats). Other players will follow in clockwise seating order around the table. 4 In reverse player order, starting with the last player, each player places their plastic Ankh token on the bottom space of the Devotion trac", "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}, {"page": 13, "score": 0.045228, "snippet": "Follow any Additional Setup Rules as dictated in the scenario book. 12 You are ready to play! There are 3 ways to become the only God of Egypt and win the game: A player wins immediately when their Ankh token reaches the top space of the Devotion track. A player wins immediately if they are the only", "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}, {"page": 16, "score": 0.031746, "snippet": "The gods wield immense power, but even they need support from Warriors and Guardians to spread their domain across the land. The Summon Figure action allows a player to choose 1 figure from their pool (Warrior or Guardian) and place it on the game board. This figure must be placed in an empty, non-W", "headingPath": "SUMMON FIGURE", "sharpsignalDocId": 358}, {"page": 19, "score": 0.03125, "snippet": "As the struggle between the gods unfolds, momentous events mark the passage of time. Monuments are erected, caravans divide the land, and violent conflicts change the balance of power. All of these events are represented on the Event track, which serves as the game's timeline. When an Action marker ", "headingPath": "Controlling Guardians", "sharpsignalDocId": 358}, {"page": 25, "score": 0.030769, "snippet": "Only in a game with 3 or more players , at the end of the 3 rd Conflict, the 2 gods with the least Devotion (the ones in the bottom 2 positions in the Devotion track) are at risk of being forgotten by the people of Egypt. To avoid that fate, those 2 gods merge into a single divine entity. The player", "headingPath": "MERGING GODS", "sharpsignalDocId": 358}, {"page": 21, "score": 0.029851, "snippet": "By deploying grand caravans of camels, the gods are able to redraw the borders that divide the land. The Camel Caravan event allows a player to split a region into 2 new smaller regions, shifting the balance of power and disrupting their opponents' plans. The player that triggered the Camel Caravan ", "headingPath": "CAMEL CARAVAN", "sharpsignalDocId": 358}, {"page": 30, "score": 0.029412, "snippet": "The Osiris player starts with 3 Underworld tokens next to their God dashboard. Whenever the Osiris player loses a Battle, they can place (if out of the board) or relocate (if already on the game board) 1 Underworld token into any empty nonWater space in the same region where the Battle occurred. Whe", "headingPath": "OSIRIS Gateway to the Underworld · RA Radiance", "sharpsignalDocId": 358}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 13, "quote": null, "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}, {"page": 13, "quote": null, "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 358 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 358 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 11, 2026 00:54

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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	CENTRAL DASHBOARD	p.9	0.048652 (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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	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
#3	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	0.045228 (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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	SUMMON FIGURE	p.16	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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	Controlling Guardians	p.19	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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	MERGING GODS	p.25	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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	CAMEL CARAVAN	p.21	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
#8	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	OSIRIS Gateway to the Underworld · RA Radiance	p.30	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 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 50 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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	#3	0.045228 (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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	#2	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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	TURN SEQUENCE · Move Figures: · Summon Figure: · Gain Followers : · Unlock Ankh Power: · GODS CAN NEVER BE KILLED · …	p.32	#24	0.012346 (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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)		p.2	#40	0.01 (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
#5	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	MOVE FIGURES	p.15	#18	0.013699 (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
#6	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	Controlling Guardians	p.19	#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
#7	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)		p.2	#10	0.027921 (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
#8	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	GAME BOARD	p.7	#9	0.029116 (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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	no quote on the wire
[2]	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	no quote on the wire

generation — timing and the path taken

timing split: retrieval 218 ms · first delta 10264 ms · total 13371 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 218 ms · ask 13143 ms · gateway work 13371 ms · total 13371 ms
tokens in (the prompt the answerer read): 2672
tokens out (what the answerer generated): 427
tok/sec: 140.5 tok/sec — 427 output tokens in 3.040 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 36s 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 287), 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.