Ruling — Ankh: Gods of Egypt

← Ankh: Gods of Egypt

You asked

How do I play?

Answered counted as answered

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

Ankh is played in turns.[1]

Turn Sequence

1. Choose your first action.[2]

2. Advance its Action marker 1 space to the right on its track.[3]

3. Perform that action in its entirety.[3]

4. If the action triggers an event (the Action marker reaches the rightmost space of its track):

- Resolve the player action that triggered the event.[3]

- Advance the Event marker 1 space to the right on the Event track.[3]

- Resolve the event itself.[3]

- Your turn ends.[1][3][2]

5. If no event was triggered:

- You must choose a second action.[3][2]

- The second action must be in a lower line of the central dashboard than the first chosen action.[3][2]

- Advance the second action's marker 1 space to the right.[3]

- Perform the second action in its entirety.[3]

- If this second action triggers an event:

- Resolve the player action.[3]

- Advance the Event marker 1 space to the right on the Event track.[3]

- Resolve the event.[3]

- Your turn ends.[1][3][2]

- If no event was triggered:

- Your turn ends.[1][2]

6. After resolving an event, return the Action marker to its starting position on its Action track (the space that matches the number of players in the game at the start of the game).[3]

7. The next player in clockwise order takes their turn.[1]

Possible Actions

* Move Figures: Move each of your figures on the board 1, 2, or 3 spaces.[4] Figures can move across spaces occupied by any player, Monuments, or other tokens, and across Water, Rivers, and Camel Caravans, but must end in an empty space that is not a Water space.[4]

* Summon Figure: Choose 1 figure from your pool (Warrior or Guardian) and place it on the board in an empty, non-Water space adjacent to one of your figures or a Monument you control.[5] (Note: The figure must be in the same region to be considered adjacent [5]).

* Gain Followers: Gain 1 Follower for each Monument (yours or neutral) that you have any figures adjacent to.[2]

* Unlock Ankh Power: Sacrifice Followers equal to the level of the next Ankh power you can unlock.[2] You may gain control of a Guardian figure of the same level if its symbol is revealed.[2]

Winning the Game

There are 3 ways to win:

1. A player wins immediately when their Ankh token reaches the top space of the Devotion track.[1][6]

2. A player wins immediately if they are the only god left in play after the 4th Conflict event.[1][6]

3. If neither previous condition is met, the player with the most Devotion wins after the last Event on the track is resolved.[1]

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

[2] RULEBOOK Ankh: Gods of Egypt — Rulebook · p.32 · TURN SEQUENCE · Move Figures: · Summon Figure: · Gain Followers : · Unlock Ankh Power: · GODS CAN NEVER BE KILLED · …

[3] RULEBOOK Ankh: Gods of Egypt — Rulebook · p.14 · BATTLE CARDS

[4] RULEBOOK Ankh: Gods of Egypt — Rulebook · p.15 · MOVE FIGURES

[5] RULEBOOK Ankh: Gods of Egypt — Rulebook · p.16 · SUMMON FIGURE

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

Rule found, game on.

🔧 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 185 ms · ask 9979 ms · total 10165 ms
single-flight (PR-5): queued 0 ms · generation 10165 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 13, "score": 0.047131, "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.046696, "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": 32, "score": 0.045541, "snippet": "The player who triggered the event takes the Battle Tiebreaker token. Then, check each region in order: Domination (One Player): Gain 1 Devotion for each Monument majority you have. Then, gain 1 Devotion for dominating the region. Battle (Multiple Players): Disregard players, figures, and Monuments ", "headingPath": "Conflict:", "sharpsignalDocId": 358}, {"page": 16, "score": 0.032787, "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": 15, "score": 0.032258, "snippet": "Positioning your figures correctly is vital if you are going to take full advantage of each region. Many situations in the game require figures to be adjacent to another figure or Monument. Other times, it can be very advantageous to simply occupy a space so that your opponents may not do so. When p", "headingPath": "MOVE FIGURES", "sharpsignalDocId": 358}, {"page": 14, "score": 0.03125, "snippet": "There are 4 possible actions a player can take during their turn: Move Figures Summon Figure Gain Followers Unlock Ankh Power Each action is displayed as a track on the central dashboard. To choose an action, the player slides the corresponding Action marker 1 space to the right on its track, then p", "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}, {"page": 9, "score": 0.030769, "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": 19, "score": 0.029851, "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}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 13, "quote": null, "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}, {"page": 32, "quote": null, "headingPath": "TURN SEQUENCE · Move Figures: · Summon Figure: · Gain Followers : · Unlock Ankh Power: · GODS CAN NEVER BE KILLED · …", "sharpsignalDocId": 358}, {"page": 14, "quote": null, "headingPath": "BATTLE CARDS", "sharpsignalDocId": 358}, {"page": 15, "quote": null, "headingPath": "MOVE FIGURES", "sharpsignalDocId": 358}, {"page": 16, "quote": null, "headingPath": "SUMMON FIGURE", "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)
answer fence: passed — letter density 0.87700 of 2065 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 25, 2026 20:41 UTC

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)	BATTLE CARDS	p.13	0.047131 (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.046696 (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)	Conflict:	p.32	0.045541 (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.032787 (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)	MOVE FIGURES	p.15	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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.14	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
#7	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	CENTRAL DASHBOARD	p.9	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
#8	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	Controlling Guardians	p.19	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

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	#2	0.046696 (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)	MOVE FIGURES	p.15	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.14	#6	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 Ankh: Gods of Egypt — Rulebook (corpus doc 358)		p.2	#28	0.011905 (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)	Conflict:	p.32	#3	0.045541 (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 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	#18	0.014085 (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
#7	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	SUMMON FIGURE	p.16	#4	0.032787 (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
#8	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.13	#1	0.047131 (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

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)	TURN SEQUENCE · Move Figures: · Summon Figure: · Gain Followers : · Unlock Ankh Power: · GODS CAN NEVER BE KILLED · …	p.32	no quote on the wire
[3]	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	BATTLE CARDS	p.14	no quote on the wire
[4]	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	MOVE FIGURES	p.15	no quote on the wire
[5]	RULEBOOK Ankh: Gods of Egypt — Rulebook (corpus doc 358)	SUMMON FIGURE	p.16	no quote on the wire
[6]	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 185 ms · first delta 4964 ms · total 10165 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 185 ms · ask 9979 ms · gateway work 10165 ms · total 10165 ms
tokens in (the prompt the answerer read): 3142
tokens out (what the answerer generated): 684
tok/sec: 132.9 tok/sec — 684 output tokens in 5.145 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 47s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 5s 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.

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 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.