Ruling — So Clover!

You asked

How do I play?

Answered counted as answered

Asked with: So Clover!bg-329839-en-1e

1. Give a Clover board and marker to each player.[1]

2. Shuffle the Keyword cards and make a face-down deck within reach of everyone.[1]

3. Everyone draws 4 Keyword cards and randomly places them on the recessed spots on their Clover board, ensuring no one else can see them.[1]

4. Draw 1 new card, remove all Keyword cards from your board, and shuffle the new card with your other 4 Keyword cards.[2]

5. Put your Clover board in front of you and place the 5 cards on top of it in a face-down pile.[2]

6. Choose the first player to be the Spectator; all other players look at their Clover boards while the Spectator cannot communicate in any way.[2]

7. The Spectator places their Clover board and 5 Keyword cards face up in the middle of the table.[2]

8. Using the Clues, the other players work together to figure out the Spectator's Pairs and put the cards back in the correct spaces on the Clover board.[2]

9. If there is a disagreement on placement, the player sitting to the left of the Spectator makes the final decision.[2]

10. When players agree on the placement, the Spectator verifies the Keywords.[2]

11. If all Pairs are placed correctly, gain 1 point per card and an extra 2 points for finding all Keywords on the first try (6 points total).[3]

12. If at least one Pair is placed incorrectly, the Spectator removes the incorrect card(s) and puts them in the middle of the table, then the other players have a second and final attempt.[3]

13. After the second attempt, the Spectator removes any remaining incorrect card(s) and puts them in the middle of the table, then gains 1 point per correct card (0 to 4 possible points).[3]

14. The Spectator writes their points in the middle of their board, discards the 5 Keyword cards used, and the player to their left becomes the next Spectator to begin a new Resolution phase.[3]

15. The game ends after every player has been the Spectator one time.[4]

16. Add up the team's total points and write the score in the Record of Legends.[1][4]

[1] RULEBOOK So Clover! — Rulebook · p.1 · François Romain · SETUP · CONTENTS

[2] RULEBOOK So Clover! — Rulebook · p.4 · Examples · 2. RESOLUTION

[3] RULEBOOK So Clover! — Rulebook · p.5 · Perfect · Second attempt

[4] RULEBOOK So Clover! — Rulebook · p.6 · END OF THE GAME · ADD A CHALLENGE · CREDITS

That settles it — whose turn was it?

🔧 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 200 ms · ask 4912 ms · total 5115 ms
single-flight (PR-5): queued 0 ms · generation 5115 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 2, "score": 0.048916, "snippet": "The game plays over two phases : Choosing Clues: individual phase. Resolution: team phase. Simultaneously, all players picks up their Clover board and secretly looks at the 8 Keywords that are on the outside edges of their cards. Notice there are 2 Keywords that form a Pair below each Clue Zone on y", "headingPath": "GAMEPLAY · 1. CHOOSING CLUES", "sharpsignalDocId": 122}, {"page": 1, "score": 0.047163, "snippet": "So Clover! is a cooperative word-association game. Play as a team to beat your high score! Draw Keyword cards and secretly write their common features on your Clover board; these are your Clues . Then work together to try to figure out each player's Keywords. At the end of the game, add up your scor", "headingPath": "François Romain · SETUP · CONTENTS", "sharpsignalDocId": 122}, {"page": 4, "score": 0.032258, "snippet": "After you write your 4 Clues , remove all of the Keyword cards from your Clover board. Then, without looking at it, draw 1 new card and shuffle it with your other 4 Keyword cards. Put your Clover board down in front of you and put your 5 cards on top of it in a face-down pile. When everyone has fini", "headingPath": "Examples · 2. RESOLUTION", "sharpsignalDocId": 122}, {"page": 6, "score": 0.031746, "snippet": "After every player has been the Spectator one time, the game ends. You can evaluate your team's deduction skills by adding up the points you all gained and writing your score in the Record of Legends. Will you be able to beat your high score? Once you are familiar with the game, you can add a new ch", "headingPath": "END OF THE GAME · ADD A CHALLENGE · CREDITS", "sharpsignalDocId": 122}, {"page": 5, "score": 0.03125, "snippet": "All Pairs are placed on the Clover board correctly : gain 1 point per card and an extra 2 points for having found all the Keywords on the first try! (total 6 points) . At least one Pair is placed on the Clover board incorrectly : the Spectator removes the incorrect card(s) without saying anything an", "headingPath": "Perfect · Second attempt", "sharpsignalDocId": 122}, {"page": 3, "score": 0.030303, "snippet": "Neither one of your Keywords or its translation into another language. Example : Amour cannot be used to connect 'Love' and 'France'. A word in the same family as a Keyword. Example : Prince cannot be used to suggest a Pair with 'Princess' and 'Brother'. Made-up words. Example : Cuppajo cannot be us", "headingPath": "Invalid Clues · Examples", "sharpsignalDocId": 122}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 1, "quote": null, "headingPath": "François Romain · SETUP · CONTENTS", "sharpsignalDocId": 122}, {"page": 4, "quote": null, "headingPath": "Examples · 2. RESOLUTION", "sharpsignalDocId": 122}, {"page": 5, "quote": null, "headingPath": "Perfect · Second attempt", "sharpsignalDocId": 122}, {"page": 6, "quote": null, "headingPath": "END OF THE GAME · ADD A CHALLENGE · CREDITS", "sharpsignalDocId": 122}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 122 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 122 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.91214 of 1639 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 24, 2026 16:19 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 So Clover! — Rulebook (corpus doc 122)	GAMEPLAY · 1. CHOOSING CLUES	p.2	0.048916 (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 So Clover! — Rulebook (corpus doc 122)	François Romain · SETUP · CONTENTS	p.1	0.047163 (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 So Clover! — Rulebook (corpus doc 122)	Examples · 2. RESOLUTION	p.4	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 So Clover! — Rulebook (corpus doc 122)	END OF THE GAME · ADD A CHALLENGE · CREDITS	p.6	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 So Clover! — Rulebook (corpus doc 122)	Perfect · Second attempt	p.5	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
#6	RULEBOOK So Clover! — Rulebook (corpus doc 122)	Invalid Clues · Examples	p.3	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

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 6 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 So Clover! — Rulebook (corpus doc 122)	François Romain · SETUP · CONTENTS	p.1	#2	0.047163 (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 So Clover! — Rulebook (corpus doc 122)	Examples · 2. RESOLUTION	p.4	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK So Clover! — Rulebook (corpus doc 122)	Perfect · Second attempt	p.5	#5	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 So Clover! — Rulebook (corpus doc 122)	Invalid Clues · Examples	p.3	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#5	RULEBOOK So Clover! — Rulebook (corpus doc 122)	END OF THE GAME · ADD A CHALLENGE · CREDITS	p.6	#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
#6	RULEBOOK So Clover! — Rulebook (corpus doc 122)	GAMEPLAY · 1. CHOOSING CLUES	p.2	#1	0.048916 (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 So Clover! — Rulebook (corpus doc 122)	François Romain · SETUP · CONTENTS	p.1	no quote on the wire
[2]	RULEBOOK So Clover! — Rulebook (corpus doc 122)	Examples · 2. RESOLUTION	p.4	no quote on the wire
[3]	RULEBOOK So Clover! — Rulebook (corpus doc 122)	Perfect · Second attempt	p.5	no quote on the wire
[4]	RULEBOOK So Clover! — Rulebook (corpus doc 122)	END OF THE GAME · ADD A CHALLENGE · CREDITS	p.6	no quote on the wire

generation — timing and the path taken

timing split: retrieval 200 ms · first delta 1369 ms · total 5115 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 200 ms · ask 4912 ms · gateway work 5115 ms · total 5115 ms
tokens in (the prompt the answerer read): 1597
tokens out (what the answerer generated): 502
tok/sec: 135.5 tok/sec — 502 output tokens in 3.704 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 56s 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 44), 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.