Ruling — Everdell Duo

You asked

How do I play?

Answered counted as answered

Asked with: Everdell Duobg-425005-en-1e

To play Everdell Duo, follow these steps:

Setup

1. For competitive play, place the game board on the table with the side showing 'Journey' in the top right; for cooperative or solo play, use the side showing numbers on some spaces.[1]

2. Place the Sun and Moon tokens on the center path, on the first space to the left.[1]

3. Place the resources, point tokens, and Occupied tokens near the board to form a general supply.[1]

4. Shuffle the Critter and Construction cards together and form a face down deck near the left of the board.[1]

5. Place 1 card face up on each spot on the board in the Meadow, filling from left to right, starting with the top row.[1]

6. Shuffle the River tiles and form a face down stack, then place the top 2 tiles face up onto the River spaces on the board.[1]

7. Place the 4 Season tiles on the right side of the board face up in order: winter, spring, summer, autumn.[1]

8. Shuffle each set of lettered Event tiles individually, randomly choose 1 from each set, combine these 5 tiles with the 'Faire' tile, shuffle these 6 tiles, and randomly place 1 at each Event spot on the top of the board, face up.[1]

9. Place the Journey Event tile at its space on the far right.[1]

10. Give the 3 Hare workers to the player who most recently took a nap and the 3 Tortoise workers to the other player.[1]

11. Each player draws 2 cards from the deck.[1]

12. Resolve the steps shown on the Winter season tile.[1]

Gameplay

1. Players alternate taking turns, starting with the player shown first on the current Season tile.[2]

2. To play a card, you must have the necessary resources in your personal supply.[3]

3. You may play cards from three locations: your hand, Meadow cards by the Sun Token, or Meadow cards by the Moon Token.[4]

4. When playing a green Production card or a tan Traveler card, you activate that card for yourself.[3]

5. If a blue Governance card activates as a result of your turn, you gain any benefit from it.[3]

6. After performing an action, move either the Sun or Moon token as in the competitive rules; if a skunk is in the way, skip that spot and place the token in the next available spot.[2]

7. You may place a worker on any Event for which you meet the listed requirements, immediately gaining the reward and placing the Event tile near your city.[4]

8. You may place a worker on any location, provided it is not occupied by a skunk or the other player (unless using a card ability that allows it) and there are still spaces for the Sun to move.[2]

9. At the start of each season, move the skunk workers to new locations by rolling the die for each skunk.[3]

10. Players alternate being the start player between each season, as shown on the season tile.[3]

Scoring and Ending the Game

1. Event tiles are worth their listed points at the end of the game.[4]

2. The Journey tile is a unique bonus given to the player who has the most cards in their hand plus their city at the end of the game, provided their total is more than their opponent's.[4]

[1] RULEBOOK Everdell Duo — Rulebook · p.3 · Ways to Play

[2] RULEBOOK Everdell Duo — Rulebook · p.9 · Sun and Moon · Placing Workers

[3] RULEBOOK Everdell Duo — Rulebook · p.10 · Playing Cards · Events · Seasons

[4] RULEBOOK Everdell Duo — Rulebook · p.5 · Events · Journey · PLAY A CARD

Settled. Play 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 97 ms · ask 5334 ms · total 26329 ms
single-flight (PR-5): queued 20897 ms · generation 5432 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 3, "score": 0.046676, "snippet": "1: When playing competitively, place the game board on the table with the side showing 'Journey' in the top right. For cooperative or solo play, use the side of the board showing numbers on some of the spaces. 2: Place the Sun and Moon tokens on the center path, on the first space to the left. Place", "headingPath": "Ways to Play", "sharpsignalDocId": 1040}, {"page": 11, "score": 0.045957, "snippet": "At the end of the game, add up your score and check to see if you have accomplished all of the required goals. If so, you have won that chapter! If playing a campaign, record your winning score on the campaign scoresheet. If you lost, you have the option to replay the chapter one time. Mark the Repl", "headingPath": "GAME END · D IFFICULTY · Normal: · Hard: · RECORDING PROGRESS", "sharpsignalDocId": 1040}, {"page": 10, "score": 0.045475, "snippet": "You will be working together to create one shared city. Play your cards into the same area on the table. You do not need to keep track of who played which card. To play a card, you must have the necessary resources in your personal supply. You may not use resources from your partner's supply. (But s", "headingPath": "Playing Cards · Events · Seasons", "sharpsignalDocId": 1040}, {"page": 15, "score": 0.045235, "snippet": "Peddler: When played and when activated, you may pay 1 resource to gain 2 of any kind(s). They may be the same or different. Postal Pigeon: When played, draw 2 cards from the deck. You may then play 1 of those cards for 2 fewer resources. Discard the other card. Spelunker: When played and when activ", "headingPath": "Critters", "sharpsignalDocId": 1040}, {"page": 5, "score": 0.045228, "snippet": "You may place a worker on any Event for which you meet the listed requirements. You only need to meet the requirements at the time that you achieve the Event. Immediately gain the reward shown on the board beneath the Event, and place the Event tile near your city. They are worth their listed points", "headingPath": "Events · Journey · PLAY A CARD", "sharpsignalDocId": 1040}, {"page": 8, "score": 0.045037, "snippet": "Everdell Duo may be played cooperatively, either in a single game or as a campaign series, where both players will work together to complete the challenges in each of the 15 chapters of the campaign. The rules for playing cooperatively are the same as the competitive rules, with the following additi", "headingPath": "Cooperative/Campaign · SETUP", "sharpsignalDocId": 1040}, {"page": 2, "score": 0.044733, "snippet": "There are four ways to play Everdell Duo: Competitive: Two players Head to head matches where one player wins. Cooperative: Two players Build a single city for both players, using one of the Campaign chapters for unique goals and restrictions. Campaign: One or Two players cooperatively A 15-Chapter ", "headingPath": "Ways to Play", "sharpsignalDocId": 1040}, {"page": 10, "score": 0.043445, "snippet": "The game ends immediately when both the Sun and Moon tokens reach the last unoccupied spot of the path in autumn. Each chapter will have specific goals that must be accomplished in order to win. Use the seal tokens to mark goals that are accomplished during your game. Take note of which goals must b", "headingPath": "GAME END", "sharpsignalDocId": 1040}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 3, "quote": null, "headingPath": "Ways to Play", "sharpsignalDocId": 1040}, {"page": 9, "quote": null, "headingPath": "Sun and Moon · Placing Workers", "sharpsignalDocId": 1040}, {"page": 10, "quote": null, "headingPath": "Playing Cards · Events · Seasons", "sharpsignalDocId": 1040}, {"page": 5, "quote": null, "headingPath": "Events · Journey · PLAY A CARD", "sharpsignalDocId": 1040}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 1040 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1040 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.91358 of 2453 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Sep 7, 2026 02:58 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 Everdell Duo — Rulebook (corpus doc 1040)	Ways to Play	p.3	0.046676 (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 Everdell Duo — Rulebook (corpus doc 1040)	GAME END · D IFFICULTY · Normal: · Hard: · RECORDING PROGRESS	p.11	0.045957 (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 Everdell Duo — Rulebook (corpus doc 1040)	Playing Cards · Events · Seasons	p.10	0.045475 (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 Everdell Duo — Rulebook (corpus doc 1040)	Critters	p.15	0.045235 (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 Everdell Duo — Rulebook (corpus doc 1040)	Events · Journey · PLAY A CARD	p.5	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
#6	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Cooperative/Campaign · SETUP	p.8	0.045037 (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 Everdell Duo — Rulebook (corpus doc 1040)	Ways to Play	p.2	0.044733 (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 Everdell Duo — Rulebook (corpus doc 1040)	GAME END	p.10	0.043445 (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 26 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 Everdell Duo — Rulebook (corpus doc 1040)	Ways to Play	p.3	#1	0.046676 (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 Everdell Duo — Rulebook (corpus doc 1040)	Playing Cards · Events · Seasons	p.10	#3	0.045475 (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 Everdell Duo — Rulebook (corpus doc 1040)	Events · Journey · PLAY A CARD	p.5	#5	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
#4	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Occupied Tokens:	p.5	#14	0.027242 (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
#5	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Sun and Moon · Placing Workers	p.9	#19	0.025992 (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
#6	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Constructions	p.14	#9	0.02885 (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 Everdell Duo — Rulebook (corpus doc 1040)	Ways to Play	p.2	#7	0.044733 (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 Everdell Duo — Rulebook (corpus doc 1040)	Critters	p.15	#4	0.045235 (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 Everdell Duo — Rulebook (corpus doc 1040)	Ways to Play	p.3	no quote on the wire
[2]	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Sun and Moon · Placing Workers	p.9	no quote on the wire
[3]	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Playing Cards · Events · Seasons	p.10	no quote on the wire
[4]	RULEBOOK Everdell Duo — Rulebook (corpus doc 1040)	Events · Journey · PLAY A CARD	p.5	no quote on the wire

generation — timing and the path taken

timing split: retrieval 97 ms · first delta 1644 ms · total 26329 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 20897 ms · retrieval 97 ms · ask 5334 ms · gateway work 5432 ms · total 26329 ms
tokens in (the prompt the answerer read): 2701
tokens out (what the answerer generated): 753
tok/sec: 202.1 tok/sec — 753 output tokens in 3.725 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 31s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 1s 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 970), 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.