You asked
How do I set up the game?
Answered counted as answeredAsked with: Hivebg-2655-en-1e
1. Each player takes all pieces of one colour and places them face up in front of them [1]. 2. One player places a piece from their hand in the centre of the table [2]. 3. The next player joins one of their own pieces to it edge to edge [2].
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- gemma4:26b think:false 5571076f3d70
- timings
- search 240 ms · ask 2284 ms · total 1665403 ms
- single-flight (PR-5)
- queued 1662870 ms · generation 2533 ms
- retrieval refs (raw)
- [{"page": 3, "score": 0.032787, "snippet": "Play begins with one player placing a piece \\ from their hand in the centre of the table and the next player joining one of their 'own pieces to it edge to edge. Players then take turns to either place or move any one of their pieces. A new piece can be introduced into the game at any time. However,", "headingPath": "Playing the Game EF) · Placing", "sharpsignalDocId": 196}, {"page": 12, "score": 0.032258, "snippet": "Ifa player can nether place a new piece or move an existing piece, the turn passes to their opponent who then takes their turn again. The game continues in this way until the player is able to move or place one oftheir pieces, or until the game is lost with the surrounding of their Queen Bee. The ga", "headingPath": "Unable to move or place · The End of the Game", "sharpsignalDocId": 196}, {"page": 4, "score": 0.031746, "snippet": "The pieces in play define the playing surface, known as the Hive. Your Queen Bee can be placed at any time from your first to your fourth turn. You must place your Queen Bee on your fourth turn if you have not placed it before. Once your Queen Bee has been placed (but not before), you can decide whe", "headingPath": "The Hive · Placing your Queen Bee · Moving", "sharpsignalDocId": 196}, {"page": 2, "score": 0.03125, "snippet": "The object of the game is to totally surround your opponent's Queen Bee whilst at the same time trying to stop your opponent from doing the same to you. The pieces surrounding the Queen Bee can be made up of a mixture of both your pieces and your opponent's. The first player to surround their oppone", "headingPath": "The Object of Hive · Preparation", "sharpsignalDocId": 196}, {"page": 1, "score": 0.030769, "snippet": "© 2010 Gen42 Games www.gen42.com Author: John Yianni", "headingPath": "a game buzzing with possibilities", "sharpsignalDocId": 196}, {"page": 11, "score": 0.030303, "snippet": "The creatures can only move in a sliding movement. If a piece is surrounded to the point that it can no longer physically slide out of its position, it Ce) ) #) may not be moved. (x) the Grasshopper, which can jump into can also climb up or down. & & The only exceptions are 7) or out of a space, and", "headingPath": "Freedom to Move", "sharpsignalDocId": 196}, {"page": 6, "score": 0.029851, "snippet": "A piece with a beetle on top of it is unable to move and for the purposes of the placing rules on p. 2, the stack takes on the colour of the Beetle. From its position on top of the Hive, the Beetle can move from tile to tile rz) across the top of the Hive. It can also drop into spaces that are surro", "headingPath": "Beetle", "sharpsignalDocId": 196}, {"page": 10, "score": 0.029412, "snippet": "The pieces in play must be linked at all times. At no i) time can you leave a piece stranded (not joined to the Hive) or separate the Hive in Moving the black Ant awe would result in the Hive J being split in two. Use this rule to your advantage by moving your pieces to strategic positions around th", "headingPath": "One Hive rule", "sharpsignalDocId": 196}]
- citations (raw)
- [{"page": 2, "quote": null, "headingPath": "The Object of Hive · Preparation", "sharpsignalDocId": 196}, {"page": 3, "quote": null, "headingPath": "Playing the Game EF) · Placing", "sharpsignalDocId": 196}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 196 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 196 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)
- debug row retained until
- Nov 6, 2026 14:37
retrieval — what the search arm returned
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 Hive — Rulebook (corpus doc 196) | Playing the Game EF) · Placing | p.3 | 0.032787 (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 Hive — Rulebook (corpus doc 196) | Unable to move or place · The End of the Game | p.12 | 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 |
| #3 | RULEBOOK Hive — Rulebook (corpus doc 196) | The Hive · Placing your Queen Bee · Moving | p.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)) | 300 |
| #4 | RULEBOOK Hive — Rulebook (corpus doc 196) | The Object of Hive · Preparation | p.2 | 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 |
| #5 | RULEBOOK Hive — Rulebook (corpus doc 196) | a game buzzing with possibilities | p.1 | 0.030769 (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)) | 52 |
| #6 | RULEBOOK Hive — Rulebook (corpus doc 196) | Freedom to Move | p.11 | 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 |
| #7 | RULEBOOK Hive — Rulebook (corpus doc 196) | Beetle | p.6 | 0.029851 (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 Hive — Rulebook (corpus doc 196) | One Hive rule | p.10 | 0.029412 (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 |
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 Hive — Rulebook (corpus doc 196) | The Object of Hive · Preparation | p.2 | no quote on the wire |
| [2] | RULEBOOK Hive — Rulebook (corpus doc 196) | Playing the Game EF) · Placing | p.3 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 240 ms · first delta 2015 ms · total 1665403 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
- full breakdown
- queued 1662870 ms · retrieval 240 ms · ask 2284 ms · gateway work 2533 ms · total 1665403 ms
- tokens in (the prompt the answerer read)
- 1489
- tokens out (what the answerer generated)
- 63
- tok/sec
- 138.8 tok/sec — 63 output tokens in 0.454 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 54s ago)
- 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)
-
set up
errata registry — what the gate above had to match against
this game registers NO errata cards (edition 114), 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.