You asked
How do workers get placed and recalled?
Answered counted as answeredWorkers can be placed in several ways depending on the specific location or card: * **Events:** You may place 1 worker on any remaining basic Event or special Event to achieve it, provided you meet all requirements and pay the necessary resources [1]. * **Cemetery:** A worker can be placed here to reveal and play cards; however, workers placed here stay permanently [2]. * **Chapel:** You may place a worker here to receive point tokens and draw cards [2]. * **Post Office:** You may place a worker here if you are able to give 2 cards from your hand to an opponent [3]. * **Storehouse:** This functions as a location where you can place a worker to take the resources listed on the card [3]. * **University:** You may place a worker here to discard a Construction or Critter and receive its resource costs back [3]. * **Haven:** This is a shared space with no limit on how many workers of any color can be placed there [4]. * **Destination Cards:** You may place a worker on a Destination card in your own city or on one in another city that has an OPEN symbol [5]. Workers are recalled/brought back during the **Prepare for Season** action. When you perform this action (which occurs when all workers are deployed and you cannot play more cards, or as part of the transition to the next season), you bring back all of your deployed workers [6]. Additionally: * Workers placed on certain events are returned "like normal" the next season [1]. * If a worker is moved to the University because its original card was discarded, it cannot be used again until you Prepare for Season [3]. * In specific scenarios (Rugwort's action), a worker may be removed from the game rather than being returned normally [7].
Strategy guides → — community tips, kept separate from rulings
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- unset-dev (corpus lane freezes the deploy value)
- timings
- search 96 ms · ask 6303 ms · total 6400 ms
- single-flight (PR-5)
- queued 0 ms · generation 6400 ms
- retrieval refs (raw)
- [{"page": 8, "score": 0.016393, "snippet": "Your workers are necessary for the expansion and success of your city. You will be deploying them to various locations in Everdell in order to gather resources, draw more cards, host events, or perhaps to embark on a journey. There are two types of locations: exclusive and shared (portrayed with an ", "headingPath": "PLACE A WORKER", "sharpsignalDocId": 63}, {"page": 9, "score": 0.016129, "snippet": "In autumn only, you may send a worker on a Journey. You must discard cards equal to the listed points of the Journey location you choose. The 5-point, 4-point, and 3-point locations are exclusive, and the 2-point location is shared. The deployed worker is worth the listed points at the end of the ga", "headingPath": "JOURNEY", "sharpsignalDocId": 63}, {"page": 9, "score": 0.015873, "snippet": "You may place a worker on any Destination card in your city, or on a Destination card in another city that has an OPEN symbol, in which case the owner of the Destination gains 1 point token from the supply.", "headingPath": "dESTINATION CAROS", "sharpsignalDocId": 63}, {"page": 3, "score": 0.015625, "snippet": "In Everdell, you will be deploying workers to various locations on the board in order to gather resources, which you will use to play cards faceup in front of you, forming your own woodland city. Each turn you will perform only one of three possible actions: Place a Worker Play a Card Prepare for Se", "headingPath": "OVERVIEW", "sharpsignalDocId": 63}, {"page": 13, "score": 0.015385, "snippet": "When preparing for the next season, new workers from the Ever Tree join your growing city. Gain the corresponding worker(s) and activate the next season's listed bonus. In spring, you gain 1 new worker and activate all green Production cards in your city in any order you choose.", "headingPath": "PREPARE FOR SEASON", "sharpsignalDocId": 63}, {"page": 21, "score": 0.015152, "snippet": "If you discard a card with a worker deployed onto it that is not there permanently, place that worker also on the University (you cannot use it again until you Prepare for Season). If they were there permanently, they are lost with the discarded card. WITHIN THIS TOMB LN THE RCMAINS OF CORRIN EVERTA", "headingPath": "CONSTRUCTIONS", "sharpsignalDocId": 63}, {"page": 8, "score": 0.014925, "snippet": "Example: Placing a worker on th is location lets you draw2 cards from the deck and gain Ipointtoken.", "headingPath": "LOCATIONS TO VISIT INCLUOE", "sharpsignalDocId": 63}, {"page": 9, "score": 0.014706, "snippet": "Grand Tour requires your city to contain 3 Destination cards. You may also place 1 of your workers on any remaining basic Event or special Event to achieve it. To achieve the Event, you must meet all the listed requirements on the Event, and must pay any required resources at the time you place your", "headingPath": "EVENTS", "sharpsignalDocId": 63}]
- citations (raw)
- [{"page": 9, "quote": null, "headingPath": "EVENTS", "sharpsignalDocId": 63}, {"page": 20, "quote": null, "headingPath": "CONSTRUCTIONS", "sharpsignalDocId": 63}, {"page": 21, "quote": null, "headingPath": "CONSTRUCTIONS", "sharpsignalDocId": 63}, {"page": 9, "quote": null, "headingPath": "HAVEN", "sharpsignalDocId": 63}, {"page": 9, "quote": null, "headingPath": "dESTINATION CAROS", "sharpsignalDocId": 63}, {"page": 12, "quote": null, "headingPath": "PREPARE FOR SEASON", "sharpsignalDocId": 63}, {"page": 17, "quote": null, "headingPath": "YEAR 3: \"RUGWORT THE RAPSCALLION\"", "sharpsignalDocId": 63}]
- boost provenance — errata + base rulebook (E2/E3)
- gate not evaluated for this ruling (boost, supersedence, and wrench all off at ask time), and the base-rulebook arm went unrecorded for the same reason — the wrench that would have stored it was off; rulesage.errata.boost-enabled=false, rulesage.errata.supersedence-enabled=false
- 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
- Oct 7, 2026 20:42
retrieval — what the search arm returned
score = the fused retrieval score (reciprocal-rank fusion over the search arms) — NOT a cosine similarity. How many arms fused this ruling was NOT RECORDED (it predates the boost trail, ran on the path that stored none, or stored one that could not be read), and the ceiling depends on that count (ceiling = arms/(k+1) at k=60): 2 arms top out at 0.03279; 3 arms top out at 0.04918. So a score above 0.03279 here is not an anomaly: it is arithmetic proof a boost arm voted, and the measured band 0.016–0.033 (taken on two-arm asks) is what does not apply. 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 — Rulebook (corpus doc 63) | PLACE A WORKER | p.8 | 0.016393 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #2 | RULEBOOK Everdell — Rulebook (corpus doc 63) | JOURNEY | p.9 | 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #3 | RULEBOOK Everdell — Rulebook (corpus doc 63) | dESTINATION CAROS | p.9 | 0.015873 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 206 |
| #4 | RULEBOOK Everdell — Rulebook (corpus doc 63) | OVERVIEW | p.3 | 0.015625 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #5 | RULEBOOK Everdell — Rulebook (corpus doc 63) | PREPARE FOR SEASON | p.13 | 0.015385 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 279 |
| #6 | RULEBOOK Everdell — Rulebook (corpus doc 63) | CONSTRUCTIONS | p.21 | 0.015152 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
| #7 | RULEBOOK Everdell — Rulebook (corpus doc 63) | LOCATIONS TO VISIT INCLUOE | p.8 | 0.014925 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 100 |
| #8 | RULEBOOK Everdell — Rulebook (corpus doc 63) | EVENTS | p.9 | 0.014706 (below the measured healthy band (< 0.016) — a weak fuse on a two-arm ask, and this ruling's arm count was never recorded) | 300 |
chosen chunks — what the answer actually cited
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.
| # | document | heading | page | quote chars |
|---|---|---|---|---|
| [1] | RULEBOOK Everdell — Rulebook (corpus doc 63) | EVENTS | p.9 | no quote on the wire |
| [2] | RULEBOOK Everdell — Rulebook (corpus doc 63) | CONSTRUCTIONS | p.20 | no quote on the wire |
| [3] | RULEBOOK Everdell — Rulebook (corpus doc 63) | CONSTRUCTIONS | p.21 | no quote on the wire |
| [4] | RULEBOOK Everdell — Rulebook (corpus doc 63) | HAVEN | p.9 | no quote on the wire |
| [5] | RULEBOOK Everdell — Rulebook (corpus doc 63) | dESTINATION CAROS | p.9 | no quote on the wire |
| [6] | RULEBOOK Everdell — Rulebook (corpus doc 63) | PREPARE FOR SEASON | p.12 | no quote on the wire |
| [7] | RULEBOOK Everdell — Rulebook (corpus doc 63) | YEAR 3: "RUGWORT THE RAPSCALLION" | p.17 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 96 ms · first delta n/a · total 6400 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 96 ms · ask 6303 ms · gateway work 6400 ms · total 6400 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 52s ago)
- stream path
- not recorded — this ruling predates the stream-path column (V41)
- 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 10), 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.