You asked
How do I setup the game?
Answered counted as answeredAsked with: Floriferousbg-322622-en-1e
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 218 ms · ask 3944 ms · total 4167 ms
- single-flight (PR-5)
- queued 0 ms · generation 4167 ms
- retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read
- [{"page": 20, "score": 0.04918, "snippet": "GAME SETUP REFERENCE See page 3 for detailed 4-player setup 4-PLAYER SETUP 3-PLAYER SETUP 2-PLAYER SETUP 2-PLAYER EXTENDED SETUP For a longer 2-player game, set up seven columns. Everything plays the same, but you will play through more cards each day. The 6th column is set up like the 4th, and the ", "headingPath": "", "sharpsignalDocId": 1113}, {"page": 15, "score": 0.04741, "snippet": "4+ -1 2 3 3 5 3 2 5 3 2 5 3 2 1. Before setting up the garden, remove the 5 Sculpture Cards from the Garden Deck and return them to the game box. They are not used in the solo game. 2. Choose a Gardener Pawn to use. Return the three other Gardener Pawns to the game box. Find the Crow Action Cards. S", "headingPath": "", "sharpsignalDocId": 1113}, {"page": 3, "score": 0.046394, "snippet": "at e s each. s: mn. ke it u d n Shuffle the 60 Garden Cards and the 21 Desire Cards into two decks and then set up the Garden . In a 4-player game, the Garden is made of 4 rows of Garden Cards followed by 1 row of Desire Cards. Each row includes 5 cards. NOTE: For the first row, deal the 2nd and 4th", "headingPath": "OBJECTIVE · GAME SETUP", "sharpsignalDocId": 1113}, {"page": 3, "score": 0.045956, "snippet": "Randomly choose a starting player, who places their pawn to the left of the topmost row of the Garden Cards. 8. Going clockwise from the starting player, each player places their pawn to the left of the next row of Garden Cards. All rows, but the last, will have a pawn in front of it. 2 3 2 Gather t", "headingPath": "", "sharpsignalDocId": 1113}, {"page": 15, "score": 0.045831, "snippet": "Find the Crow Action Cards . Shuffle them and place the Crow Actions Deck face-down near the side of the garden. Find the Crow Card and place it near the Crow Actions Deck . Place the Cup of Tea near the player. Unlike multiplayer games, you start with this card in your possession. The player takes ", "headingPath": "SOLO SETUP EXAMPLE", "sharpsignalDocId": 1113}, {"page": 14, "score": 0.045688, "snippet": "Score the most victory points and compare your score to the relaxation chart at the end of the rules to see how well you did. Meanwhile, the pesky crow will steal flowers, gather stones, and try to wreck your stroll. Setup is the same as the 2-player game with the following changes: Players may choo", "headingPath": "SOLO OBJECTIVE · SOLO SETUP", "sharpsignalDocId": 1113}, {"page": 9, "score": 0.044776, "snippet": "Make sure each pawn keeps the same position from the end of one day to the start of the next. The player who ends the day with their pawn at the top will take the first turn at the start of the next day. Remember to discard any remaining cards in the garden at the end of each day. BEGIN A NEW DAY To", "headingPath": "", "sharpsignalDocId": 1113}, {"page": 2, "score": 0.029828, "snippet": "YOUR GARDEN AWAITS Spend the afternoon in your floriferous garden. Relax while enjoying this elegant game of picking, pairing, and arranging flowers. Find joy in the abundance of nature. OBJECTIVE Score the most victory points by collecting flowers and pairing them with Arrangement, Desire, and Boun", "headingPath": "", "sharpsignalDocId": 1113}]
- citations (raw) — what the answer cited, chosen from a retrieval this page cannot show
- [{"page": 3, "quote": null, "headingPath": "OBJECTIVE · GAME SETUP", "sharpsignalDocId": 1113}, {"page": 2, "quote": null, "headingPath": "", "sharpsignalDocId": 1113}, {"page": 20, "quote": null, "headingPath": "", "sharpsignalDocId": 1113}, {"page": 14, "quote": null, "headingPath": "SOLO OBJECTIVE · SOLO SETUP", "sharpsignalDocId": 1113}, {"page": 15, "quote": null, "headingPath": "", "sharpsignalDocId": 1113}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 1113 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 1113 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.85594 of 1666 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
- debug row recorded
- Oct 8, 2026 17:38 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 Floriferous — Rulebook (corpus doc 1113) | p.20 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | 300 | |
| #2 | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | p.15 | 0.04741 (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 Floriferous — Rulebook (corpus doc 1113) | OBJECTIVE · GAME SETUP | p.3 | 0.046394 (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 Floriferous — Rulebook (corpus doc 1113) | p.3 | 0.045956 (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 Floriferous — Rulebook (corpus doc 1113) | SOLO SETUP EXAMPLE | p.15 | 0.045831 (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 Floriferous — Rulebook (corpus doc 1113) | SOLO OBJECTIVE · SOLO SETUP | p.14 | 0.045688 (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 Floriferous — Rulebook (corpus doc 1113) | p.9 | 0.044776 (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 Floriferous — Rulebook (corpus doc 1113) | p.2 | 0.029828 (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 29 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 Floriferous — Rulebook (corpus doc 1113) | p.20 | #1 | 0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1) | vector + full-text + the doc-priority boost arm | the re-ranker chose it | |
| #2 | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | SOLO SETUP EXAMPLE | p.15 | #5 | 0.045831 (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 Floriferous — Rulebook (corpus doc 1113) | SOLO OBJECTIVE · SOLO SETUP | p.14 | #6 | 0.045688 (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 Floriferous — Rulebook (corpus doc 1113) | p.15 | #2 | 0.04741 (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 | |
| #5 | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | p.3 | #4 | 0.045956 (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 | |
| #6 | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | p.2 | #11 | 0.02837 (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 Floriferous — Rulebook (corpus doc 1113) | p.9 | #7 | 0.044776 (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 Floriferous — Rulebook (corpus doc 1113) | OBJECTIVE · GAME SETUP | p.3 | #3 | 0.046394 (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
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 Floriferous — Rulebook (corpus doc 1113) | OBJECTIVE · GAME SETUP | p.3 | no quote on the wire |
| [2] | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | p.2 | no quote on the wire | |
| [3] | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | p.20 | no quote on the wire | |
| [4] | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | SOLO OBJECTIVE · SOLO SETUP | p.14 | no quote on the wire |
| [5] | RULEBOOK Floriferous — Rulebook (corpus doc 1113) | p.15 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 218 ms · first delta 1028 ms · total 4167 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 218 ms · ask 3944 ms · gateway work 4167 ms · total 4167 ms
- tokens in (the prompt the answerer read)
- 2385
- tokens out (what the answerer generated)
- 626
- tok/sec
- 203.0 tok/sec — 626 output tokens in 3.084 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 44s ago)
- answerer host (measured by rulesage)
- reachable (for 2h, checked 8s 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
- NO_APPROVED_CHECKLIST — setup-shaped, but no approved setup checklist exists for this game
- pattern that matched
- SETUP — "setup" / "set up"
- matched words (in the normalized question)
-
setup
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 1043), 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.