You asked
How do I setup the game?
Answered counted as answered1. Remove specific bean types based on player count: three players (Cocoa Beans), four/five players (Coffee Beans), or six/seven players (Cocoa and Garden Beans) [1]. 2. Add Cocoa, Wax, and Coffee Beans to the game [2]. 3. Set up the number of available bean fields based on the number of players: use the side with three bean fields for 3 players, and the side showing two bean fields for 4-7 players [1]. 4. Each player starts with five cards in their hands [3]. 5. Every player draws one card from the draw pile, starting with the active player and moving clockwise [4].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:12b think:false 4eb23ef187e2
- timings
- search 244 ms · ask 4610 ms · total 4866 ms
- single-flight (PR-5)
- queued 0 ms · generation 4866 ms
- retrieval refs (raw)
- [{"page": 3, "score": 0.016393, "snippet": "The starting player is the first active player. After that, players take turns going to the in clockwise order. The starting player keeps the starting player card for the whole game (see 'The End of the Game'). When it is your turn, you play through these four phases in order: Plant Bean Cards from ", "headingPath": "playInG The Game", "sharpsignalDocId": 79}, {"page": 7, "score": 0.016129, "snippet": "Unlike in the base game, every player draws one card from the draw pile , adding them to their hands behind the last card. Start with the active player and draw cards in a clockwise direction.", "headingPath": "Phase 4: Draw Bean Cards", "sharpsignalDocId": 79}, {"page": 3, "score": 0.015873, "snippet": "You must plant the first card in your hand (i.e. the one that is completely visible) in one of your fields (see both illustrations to the right). After that, you may choose to plant one more card - the one that is now completely visible - in one of your fields (see both illustrations to the right). ", "headingPath": "Phase 1: Plant Bean Cards from Your Hand", "sharpsignalDocId": 79}, {"page": 7, "score": 0.015625, "snippet": "Add the Cocoa , Wax , and Coffee Beans to your game. Depending on the number of players, you will need to remove certain types of beans from the game. The number of available bean fields also depends on the number of players.", "headingPath": "ComponenTs & seTup", "sharpsignalDocId": 79}, {"page": 7, "score": 0.015385, "snippet": "Play the game just like regular Bohnanza : Each player starts with five cards in their hands; On your turn, play through the usual four phases. Only the rules for phase 4, 'Drawing bean cards' , and the end of the game change when you play with extra types of beans.", "headingPath": "playInG The Game", "sharpsignalDocId": 79}, {"page": 4, "score": 0.015152, "snippet": "When planting, you start or extend the column of cards in the field. If you have to plant a kind of bean you do not have space for, you must harvest a field first (see 'Harvesting Beans'). If you do not have any cards in your hand at the start of phase 1, skip it and go straight to phase 2.", "headingPath": "Phase 1: Plant Bean Cards from Your Hand", "sharpsignalDocId": 79}, {"page": 8, "score": 0.014925, "snippet": "After planting one or two cards in his bean fields (as in the normal game), the player may discard one card from anywhere in his hand face up on the discard pile.", "headingPath": "2. Plant bean cards & discard", "sharpsignalDocId": 79}, {"page": 8, "score": 0.014706, "snippet": "The active player draws the three topmost cards from the draw deck and puts them face up on the table so both players can see them. If the topmost card on the discard pile matches any of the cards just drawn, the player adds it to them. He does the same with the new topmost card from the discard pil", "headingPath": "3. Draw, plant, and offer beans", "sharpsignalDocId": 79}]
- citations (raw)
- [{"page": 7, "quote": null, "headingPath": "Number of Bean Fields", "sharpsignalDocId": 79}, {"page": 7, "quote": null, "headingPath": "ComponenTs & seTup", "sharpsignalDocId": 79}, {"page": 7, "quote": null, "headingPath": "playInG The Game", "sharpsignalDocId": 79}, {"page": 7, "quote": null, "headingPath": "Phase 4: Draw Bean Cards", "sharpsignalDocId": 79}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base-rulebook boost: not recorded (this ruling predates it); rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base-rulebook boost: not recorded (this ruling predates it)
- 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 22, 2026 00:56
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 Bohnanza — Rulebook (corpus doc 79) | playInG The Game | p.3 | 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 Bohnanza — Rulebook (corpus doc 79) | Phase 4: Draw Bean Cards | p.7 | 0.016129 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 192 |
| #3 | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | Phase 1: Plant Bean Cards from Your Hand | p.3 | 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 Bohnanza — Rulebook (corpus doc 79) | ComponenTs & seTup | p.7 | 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) | 225 |
| #5 | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | playInG The Game | p.7 | 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) | 266 |
| #6 | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | Phase 1: Plant Bean Cards from Your Hand | p.4 | 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) | 291 |
| #7 | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | 2. Plant bean cards & discard | 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) | 162 |
| #8 | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | 3. Draw, plant, and offer beans | p.8 | 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 Bohnanza — Rulebook (corpus doc 79) | Number of Bean Fields | p.7 | no quote on the wire |
| [2] | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | ComponenTs & seTup | p.7 | no quote on the wire |
| [3] | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | playInG The Game | p.7 | no quote on the wire |
| [4] | RULEBOOK Bohnanza — Rulebook (corpus doc 79) | Phase 4: Draw Bean Cards | p.7 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 244 ms · first delta n/a · total 4866 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 244 ms · ask 4610 ms · gateway work 4866 ms · total 4866 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 42s 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
- SERVED — setup-shaped and this game's approved setup checklist is offered above
- 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 13), 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.