You asked
How many patch tiles does each player start with?
Answered counted as answeredAsked with: Calicobg-283155-en-1e
Each player draws 2 Patch Tiles from the facedown stacks (or Bag, if using) into their hand [1], [2], [3].
🔧 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 266 ms · ask 4980 ms · total 5258 ms
- single-flight (PR-5)
- queued 0 ms · generation 5258 ms
- retrieval refs (raw)
- [{"page": 5, "score": 0.032787, "snippet": "Each player draws 2 Patch Tiles from the facedown stacks (or Bag, if using) into their hand. Reveal 3 Patch Tiles to form the tile market in the center of the table. Shuffle all Patch Tiles and place them into facedown stacks within easy reach of all players OR put them in the Bag. You are now ready", "headingPath": "STANDARD SETUP", "sharpsignalDocId": 230}, {"page": 5, "score": 0.032258, "snippet": "Beginning with the first player and going clockwise around On your turn you must perform steps 1 + 2 in order. the table, players will take turns until each player's Quilt Board is completely filled with Patch Tiles (22 turns). The players will then count points for Design Goal Tiles, Cat Tokens, an", "headingPath": "GAMEPLAY OVERVIEW PLAYER TURN", "sharpsignalDocId": 230}, {"page": 5, "score": 0.031746, "snippet": "' ' ! 8222S S22 SSSVSBBS**BSS*BOS*'BS*LS&SSBVAS'S SSS eSE GH O222222\" ! ! 1 ! ! ! ! ' ! ! ' , ' ! ! ' 1 1 ! ! 1 ' ! ' ! ! ' ! i] ' ' 1 ' ' ' ! ' ' i] D Place the Button Scoring Tile and Button Tokens in the center of the table. ®& Give each player a Quilt Board and their matching set of 6 Design Goa", "headingPath": "STANDARD SETUP", "sharpsignalDocId": 230}, {"page": 4, "score": 0.03125, "snippet": "We recommend using the beginner setup until you arefamiliar with the game, before moving to the standard setup. Cee ee ee ee ee ee ee ee ee ee eee ee ee eee een Place the Millie, Tidsit, and Coconut Cat Scoring iE Give each player a Quilt Board and their matching set of 6 Tiles and their matching Ca", "headingPath": "BEGINNER SETUP", "sharpsignalDocId": 230}, {"page": 7, "score": 0.030769, "snippet": "The colors on your Patch Tiles can earn you buttons to sew onto your quilt. To sew a button onto your quilt you must make a group of three Patch Tiles or more, of the same color. The group may be in any shape. Each button is worth 3 points. You may use the partial and whole edge tiles printed on you", "headingPath": "BUTTON SCORING TILE + BUTTON TOKENS", "sharpsignalDocId": 230}, {"page": 3, "score": 0.030303, "snippet": "24 Design Goal Tiles 6 Black + White 5 Double-sided (4 sets of 6 in 4 player colors Patch Tiles Cat Scoring Tiles shown on tile back) 86 Cat Tokens 1 Cloth Tile Bag 1 Score Pad 52 Button Tokens 1 Button Scoring Tile 1 Master Quilter Tile (8 of each color + 4 rainbow)", "headingPath": "COMPONENTS", "sharpsignalDocId": 230}, {"page": 6, "score": 0.029851, "snippet": "Each Design Goal Tileis a long-term goal that may score points at the end of the game based on the six Patch Tiles that surroundit. To score points, each Design Goal Tile must be completed using either the colors OR the patterns of the six surrounding Patch Tiles. You can complete a Design Goal Tile", "headingPath": "DESIGN GOAL TILES", "sharpsignalDocId": 230}, {"page": 8, "score": 0.029412, "snippet": "The game ends after each player has completely filled their Quilt Board with Patch Tiles. Use the Score Pad to record points for each player's Design Goal Tiles, Cat Tokens, and Button Tokens. The player with the most points is the winner! In case of a tie, the player with the most cat tokens is the", "headingPath": "GAME END + FINAL SCORING · Family Variant · 2-Player Lower Variance Variant", "sharpsignalDocId": 230}]
- citations (raw)
- [{"page": 5, "quote": null, "headingPath": "STANDARD SETUP", "sharpsignalDocId": 230}, {"page": 4, "quote": null, "headingPath": "BEGINNER SETUP", "sharpsignalDocId": 230}, {"page": 5, "quote": null, "headingPath": "STANDARD SETUP", "sharpsignalDocId": 230}]
- boost provenance — errata + base rulebook (E2/E3)
-
no registered errata card matched this query; base rulebook doc 230 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 230 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 4, 2026 16:11
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 Calico — Rulebook (corpus doc 230) | STANDARD SETUP | p.5 | 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 Calico — Rulebook (corpus doc 230) | GAMEPLAY OVERVIEW PLAYER TURN | p.5 | 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 Calico — Rulebook (corpus doc 230) | STANDARD SETUP | p.5 | 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 Calico — Rulebook (corpus doc 230) | BEGINNER SETUP | p.4 | 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 Calico — Rulebook (corpus doc 230) | BUTTON SCORING TILE + BUTTON TOKENS | p.7 | 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)) | 300 |
| #6 | RULEBOOK Calico — Rulebook (corpus doc 230) | COMPONENTS | 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)) | 267 |
| #7 | RULEBOOK Calico — Rulebook (corpus doc 230) | DESIGN GOAL TILES | 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 Calico — Rulebook (corpus doc 230) | GAME END + FINAL SCORING · Family Variant · 2-Player Lower Variance Variant | p.8 | 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 Calico — Rulebook (corpus doc 230) | STANDARD SETUP | p.5 | no quote on the wire |
| [2] | RULEBOOK Calico — Rulebook (corpus doc 230) | BEGINNER SETUP | p.4 | no quote on the wire |
| [3] | RULEBOOK Calico — Rulebook (corpus doc 230) | STANDARD SETUP | p.5 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 266 ms · first delta 4973 ms · total 5258 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 266 ms · ask 4980 ms · gateway work 5258 ms · total 5258 ms
- tokens in (the prompt the answerer read)
- 2722
- tokens out (what the answerer generated)
- 32
- tok/sec
- 138.5 tok/sec — 32 output tokens in 0.231 s of generation
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 13s 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
- 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 156), 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.