You asked
How does end-of-round goal scoring on the green side of the goal board work?
Answered counted as answeredThe end-of-round goal scoring on the green side of the goal board works by counting the quantity of the targeted item (such as birds or eggs) in a given habitat or nest type at the end of the round. Players then place an action cube on the goal board to indicate their score, even if they score 0 points. The green side uses a method where players compare their results and place their action cubes based on their rank order. If players tie, both cubes are placed on the tied place, and the next place is not awarded. At game end, the points for that place and the next place(s) are added and divided by the number of players who tied, then rounded down (4th place scores 0 points). Players must have at least one of the targeted items to score points for a goal. If a player finishes in 4th or 5th place, they must still place an action cube on the goal board in the space marked 0. [1], [2], [3], [4] Note: While [1], [2], [3], and [4] describe the green side's scoring method, [1] and [5] state that green is the default side, and [2] and [3] describe the ranking-based method, which is consistent with the green side. Therefore, the description in [1], [2], [3], and [4] collectively provide the explicit answer to the question. [1] and [5] confirm the green side is used and that action cubes are placed regardless of score. [2] and [3] describe the ranking and tie-breaking rules. [4] confirms the scoring method with maximum 5 points and the 0-point requirement. Thus, the full answer is supported by these sources. Final Answer: [1], [2], [3], [4]
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 109 ms · ask 11490 ms · total 11600 ms
- single-flight (PR-5)
- queued 0 ms · generation 11600 ms
- retrieval refs (raw)
- [{"page": 11, "score": 0.016393, "snippet": "The end-of-round goals are based on how many birds or eggs you have in a given habitat or nest type. To indicate the points you score from that goal, each player must place an action cube on the goal board (even if you score 0 points). The board has 2 sides, each using a different scoring method. Gr", "headingPath": "Scoring End-of-Round Goals", "sharpsignalDocId": 45}, {"page": 15, "score": 0.016129, "snippet": "The base game includes a double-sided goal mat and a set of goal tiles. End-of-round goals are based on how many birds or eggs you have in a given habitat or nest type. To indicate the points you score from that goal, each player must place an action cube on the goal board (even if you score 0 point", "headingPath": "Scoring End-of-Round Goals (Original Rules for Base Game)", "sharpsignalDocId": 49}, {"page": 11, "score": 0.015873, "snippet": "This method uses the side of the goal board that has spaces labeled 5-4-3-2-1-0 next to the space for each goal. For example, when using the goal that scores 5, 2, or 1 points, if two players tie for 1st place, each gets 3 points (5 + 2 divided by 2 players, rounded down). Do not award 2nd place to ", "headingPath": "Blue: One point per targeted item", "sharpsignalDocId": 45}, {"page": 15, "score": 0.015625, "snippet": "This method uses the side of the goal board that has rankings 5-4-3-2-1-0 next to the space for each goal. For example, when using the goal that scores 5, 2, or 1 points, if two players tie for 1st place, each gets 3 points (5 + 2 divided by 2 players, rounded down). Do not award 2nd place to anothe", "headingPath": "Blue: One point per targeted item", "sharpsignalDocId": 49}, {"page": 15, "score": 0.015385, "snippet": "This method uses the side of the goal board that has spaces for first, second, and third place. At the end of the round, count your quantity of the targeted item. Players compare their results and WS_GoalMat_r2.indd 1 8/2/18 6:50 PM place their action cubes based on their rank order. If players tie,", "headingPath": "Green: Majority of the targeted item", "sharpsignalDocId": 49}, {"page": 11, "score": 0.015152, "snippet": "This method uses the side of the goal board that has spaces for 1st, 2nd, and 3rd place. At the end of the round, count your quantity of the targeted item. Players compare their results and place their action cubes based on their rank order. WS_GoalMat_r2.indd 1 8/2/18 6:50 PM If players tie, place ", "headingPath": "Green: Majority of the targeted item", "sharpsignalDocId": 45}, {"page": 2, "score": 0.014925, "snippet": "The only change to the setup for a game of Wingspan is to place the reference tile near the goal mat. We recommend using the green side of the goal mat with this expansion, as some of the new goals do not work well with the blue side. As a reminder, all action cubes should stay in the row used until", "headingPath": "Setup Changes", "sharpsignalDocId": 47}, {"page": 4, "score": 0.014706, "snippet": "When all players have placed all of their action cubes, the round is over. Follow these steps in order: Use 1 of your action cubes to mark your score on the end-of-round goal. As a result, you will have 1 fewer action cube to use each round: Use round-end bird powers for birds on your player mat. Sc", "headingPath": "Round Structure", "sharpsignalDocId": 49}]
- citations (raw)
- [{"page": 11, "quote": null, "headingPath": "Scoring End-of-Round Goals", "sharpsignalDocId": 45}, {"page": 15, "quote": null, "headingPath": "Green: Majority of the targeted item", "sharpsignalDocId": 49}, {"page": 11, "quote": null, "headingPath": "Green: Majority of the targeted item", "sharpsignalDocId": 45}, {"page": 11, "quote": null, "headingPath": "Blue: One point per targeted item", "sharpsignalDocId": 45}, {"page": 15, "quote": null, "headingPath": "Scoring End-of-Round Goals (Original Rules for Base Game)", "sharpsignalDocId": 49}]
- 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 15:59
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 Wingspan — Rulebook (corpus doc 45) | Scoring End-of-Round Goals | p.11 | 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 Wingspan — Asia Rulebook (corpus doc 49) | Scoring End-of-Round Goals (Original Rules for Base Game) | p.15 | 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 Wingspan — Rulebook (corpus doc 45) | Blue: One point per targeted item | p.11 | 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) | 300 |
| #4 | RULEBOOK Wingspan — Asia Rulebook (corpus doc 49) | Blue: One point per targeted item | p.15 | 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 Wingspan — Asia Rulebook (corpus doc 49) | Green: Majority of the targeted item | p.15 | 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) | 300 |
| #6 | RULEBOOK Wingspan — Rulebook (corpus doc 45) | Green: Majority of the targeted item | p.11 | 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 Wingspan — European Expansion (corpus doc 47) | Setup Changes | p.2 | 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) | 300 |
| #8 | RULEBOOK Wingspan — Asia Rulebook (corpus doc 49) | Round Structure | p.4 | 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 Wingspan — Rulebook (corpus doc 45) | Scoring End-of-Round Goals | p.11 | no quote on the wire |
| [2] | RULEBOOK Wingspan — Asia Rulebook (corpus doc 49) | Green: Majority of the targeted item | p.15 | no quote on the wire |
| [3] | RULEBOOK Wingspan — Rulebook (corpus doc 45) | Green: Majority of the targeted item | p.11 | no quote on the wire |
| [4] | RULEBOOK Wingspan — Rulebook (corpus doc 45) | Blue: One point per targeted item | p.11 | no quote on the wire |
| [5] | RULEBOOK Wingspan — Asia Rulebook (corpus doc 49) | Scoring End-of-Round Goals (Original Rules for Base Game) | p.15 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 109 ms · first delta n/a · total 11600 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 109 ms · ask 11490 ms · gateway work 11600 ms · total 11600 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 37s 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
6 errata cards registered for edition 3 — these are what the gate above had to match against
- anatomist · HEADING_EXTRACTED · Wingspan — Update Pack (Corrected Bonus Cards) · corpus doc 66 · p.2
- belted kingfisher · HAND_PINNED · Wingspan — Update Pack (Corrected Bird Cards) · corpus doc 65 · p.17
- ecologist · HEADING_EXTRACTED · Wingspan — Update Pack (Corrected Bonus Cards) · corpus doc 66 · p.5
- oologist · HEADING_EXTRACTED · Wingspan — Update Pack (Corrected Bonus Cards) · corpus doc 66 · p.1
- photographer · HEADING_EXTRACTED · Wingspan — Update Pack (Corrected Bonus Cards) · corpus doc 66 · p.3
- rodentologist · HEADING_EXTRACTED · Wingspan — Update Pack (Corrected Bonus Cards) · corpus doc 66 · p.4
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.