Ruling — Project: ELITE

You asked

How do I play?

Answered counted as answered

Asked with: Project: ELITEbg-256999-en-1e

Project: ELITE is a cooperative board game for 1 to 6 players where players act as an ELITE squad attempting to fulfill missions before time runs out.[1][2] While the game controls the aliens and their activations, players engage in real-time dice rolling to move, search for weapons and items, and fight the alien swarm.[1][2]

**Action Phase**

The Action Phase occurs in real-time, controlled by an electronic timer or app, typically lasting 2 minutes.[3]

1. The Timekeeper sets the timer (to 2 minutes standard) and all players ensure they have their Action and Hit dice.[3]

2. Once players are ready, the Timekeeper starts the timer and players begin rolling their Action dice.[3]

3. Players take some or all of their Action dice and roll them.[3]

4. Players may reroll any number of Action dice any number of times, but any results must be resolved before rerolling or performing other Actions.[3]

5. Players choose 1 or more rolled dice to resolve by either spending the die (setting it aside to resolve its effect) or allocating it in an Action slot.[3]

6. Once an Action die is resolved, it becomes available to use again, unless it was placed in a Locking slot.[3]

**Actions and Mechanics**

* **Move Action:** By spending a Move result, a Hero may move their figure 1 Space in any direction (orthogonally or diagonally); multiple results allow moving multiple Spaces.[3] Heroes cannot move through Walls or diagonally across a Wall's corner.[3]

* **Attacking:** To attack an Alien, a Hero must have Line of Sight (LOS) to it, and the Alien must be within the Weapon's Range.[4] LOS is established by an imaginary line between the centers of two figures that is not interrupted by a blocking element.[4]

* **Exploration:** A Hero adjacent to an Exploration token may spend 1 die to flip the token to its backside.[5] A Hero adjacent to an Exploration token may spend 1 die to reveal it, activating its effect, after which the token is removed from the Map.[5]

* **Recon Tokens:** A Hero adjacent to a Recon token may allocate dice to it to move the token to an adjacent space.[6] Heroes can also allocate 1 die to a Recon token adjacent to a Target token to replace the Target token with the Recon token.[6]

[1] RULEBOOK Project: ELITE — Rulebook · p.2 · GAME OVERVIEW

[2] RULEBOOK Project: ELITE — Rulebook · p.2

[3] RULEBOOK Project: ELITE — Rulebook · p.14 · 3. ACTION PHASE · Rolling, Spending, and Allocating Action dice · Actions

[4] RULEBOOK Project: ELITE — Rulebook · p.19 · Line of Sight (LOS)

[5] RULEBOOK Project: ELITE — Rulebook · p.25 · EXPLORATION · OBJECTIVE · SPECIAL RULES · Abandoned Lab · Crash Site

[6] RULEBOOK Project: ELITE — Rulebook · p.24 · Crash Site

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 79 ms · ask 5313 ms · total 5392 ms
single-flight (PR-5): queued 0 ms · generation 5392 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 10, "score": 0.047379, "snippet": "9 . Each Event card displays a number in its bottom right corner. Sort the Event cards in different piles according to the rows below and shuffle each pile. Then, take a total of 8 cards according to the chosen difficulty level below. Return the remaining cards to the box. | CARD # | EASY | MEDIUM |", "headingPath": "GAME SETUP · SOLO MODE", "sharpsignalDocId": 647}, {"page": 9, "score": 0.032787, "snippet": "1 . Choose 1 side of the Map board and place it faceup in the center of the table. Given the game's real time aspect, it is very important the Map is within easy reach of all players. 2 . Each player does the following: Choose a Hero and take the corresponding Hero dashboard and figure. Choose a pla", "headingPath": "GAME SETUP", "sharpsignalDocId": 647}, {"page": 3, "score": 0.032258, "snippet": "With music carefully created by Orkestra and with an amazing production by Labirinto Filmes, the Project: ELITE app offers a timer function for the real-time Action Phase, along with custom made soundtracks to transport players to the battlefield, which react and adapt to the amount of time left, es", "headingPath": "IMPROVE YOUR GAME EXPERIENCE!", "sharpsignalDocId": 647}, {"page": 14, "score": 0.031746, "snippet": "The Action Phase takes place in real-time and is controlled by the electronic timer. The standard Action Phase duration is 2 minutes, during which the Heroes repeatedly roll their dice to perform different Actions. At the beginning of each Action Phase, the Timekeeper sets the timer (the electronic ", "headingPath": "3. ACTION PHASE · Rolling, Spending, and Allocating Action dice · Actions", "sharpsignalDocId": 647}, {"page": 24, "score": 0.030769, "snippet": "1 and 2 Players: 4 and 7 3 Players: 1, 7, and 10 4 Players: 1, 6, 9, and 10 5 Players: 1, 4, 7, 9, and 11 6 Players: 2 and 7 to 11 Moving a Recon token . Any Hero adjacent to a Recon token may allocate dice to it. For each die you allocate, move the token to a Space adjacent to where the token itsel", "headingPath": "Crash Site", "sharpsignalDocId": 647}, {"page": 22, "score": 0.030303, "snippet": "Once each Alien has performed its Abilities, all Swarm and Boss figures on the Map move. Each Swarm type and Boss has its own Movement value, which indicates the number of Spaces each figure will move. Heroes may move the Alien figures in any order they wish, but all Alien figures must move their fu", "headingPath": "Alien Movement Step · 5. END OF THE ROUND PHASE · WINNING OR LOSING THE GAME", "sharpsignalDocId": 647}, {"page": 17, "score": 0.029851, "snippet": "A . Name B . Dice slot(s) C . Weapon Effect , if any. D . Range NOTE: If an is shown, this Weapon has unlimited Range. E . Hit dice: The number of Hit dice rolled when attacking. F . To-Hit Value: The minimum dice value needed for a successful Hit. G . Attachment Restriction: Restrictions for adding", "headingPath": "Weapons", "sharpsignalDocId": 647}, {"page": 11, "score": 0.029727, "snippet": "A game of Projet: ELITE is played over a maximum of 8 Game Rounds. Each Game Round is broken up into the following Phases: 1 - Event Phase 2 - Alien Spawning Phase 3 - Action Phase 4 - Alien Activation Phase 5 - End of the Round Phase At the beginning of each Game Round, the Heroes reveal the left-m", "headingPath": "PHASES OF THE GAME · 1. EVENT PHASE · Ongoing Effect: · No Effect · B . Action Slots · C . Event Effect · …", "sharpsignalDocId": 647}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 2, "quote": null, "headingPath": "GAME OVERVIEW", "sharpsignalDocId": 647}, {"page": 2, "quote": null, "headingPath": "", "sharpsignalDocId": 647}, {"page": 14, "quote": null, "headingPath": "3. ACTION PHASE · Rolling, Spending, and Allocating Action dice · Actions", "sharpsignalDocId": 647}, {"page": 19, "quote": null, "headingPath": "Line of Sight (LOS)", "sharpsignalDocId": 647}, {"page": 25, "quote": null, "headingPath": "EXPLORATION · OBJECTIVE · SPECIAL RULES · Abandoned Lab · Crash Site", "sharpsignalDocId": 647}, {"page": 24, "quote": null, "headingPath": "Crash Site", "sharpsignalDocId": 647}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 647 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 647 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.91553 of 1835 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 25, 2026 01:54 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 Project: ELITE — Rulebook (corpus doc 647)	GAME SETUP · SOLO MODE	p.10	0.047379 (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 Project: ELITE — Rulebook (corpus doc 647)	GAME SETUP	p.9	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
#3	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	IMPROVE YOUR GAME EXPERIENCE!	p.3	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
#4	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	3. ACTION PHASE · Rolling, Spending, and Allocating Action dice · Actions	p.14	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 Project: ELITE — Rulebook (corpus doc 647)	Crash Site	p.24	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 Project: ELITE — Rulebook (corpus doc 647)	Alien Movement Step · 5. END OF THE ROUND PHASE · WINNING OR LOSING THE GAME	p.22	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
#7	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	Weapons	p.17	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 Project: ELITE — Rulebook (corpus doc 647)	PHASES OF THE GAME · 1. EVENT PHASE · Ongoing Effect: · No Effect · B . Action Slots · C . Event Effect · …	p.11	0.029727 (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 41 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 Project: ELITE — Rulebook (corpus doc 647)	GAME SETUP	p.9	#2	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
#2	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	GAME OVERVIEW	p.2	#23	0.012048 (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
#3	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	Line of Sight (LOS)	p.19	#14	0.013889 (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 Project: ELITE — Rulebook (corpus doc 647)	3. ACTION PHASE · Rolling, Spending, and Allocating Action dice · Actions	p.14	#4	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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	EXPLORATION · OBJECTIVE · SPECIAL RULES · Abandoned Lab · Crash Site	p.25	#18	0.012821 (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 Project: ELITE — Rulebook (corpus doc 647)	Crash Site	p.24	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)		p.2	#31	0.010989 (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
#8	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	GAME SETUP · SOLO MODE	p.10	#1	0.047379 (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 Project: ELITE — Rulebook (corpus doc 647)	GAME OVERVIEW	p.2	no quote on the wire
[2]	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)		p.2	no quote on the wire
[3]	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	3. ACTION PHASE · Rolling, Spending, and Allocating Action dice · Actions	p.14	no quote on the wire
[4]	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	Line of Sight (LOS)	p.19	no quote on the wire
[5]	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	EXPLORATION · OBJECTIVE · SPECIAL RULES · Abandoned Lab · Crash Site	p.25	no quote on the wire
[6]	RULEBOOK Project: ELITE — Rulebook (corpus doc 647)	Crash Site	p.24	no quote on the wire

generation — timing and the path taken

timing split: retrieval 79 ms · first delta 2744 ms · total 5392 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 79 ms · ask 5313 ms · gateway work 5392 ms · total 5392 ms
tokens in (the prompt the answerer read): 3597
tokens out (what the answerer generated): 525
tok/sec: 201.8 tok/sec — 525 output tokens in 2.602 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 19s ago)
gateway schema (read from the running child): schema head 0042_definer_search_path (live revision not readable by this principal)
answerer host (measured by rulesage): reachable (for 60h, checked 7s 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 580), 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.