You asked
How does the Marquise de Cat build and score?
Answered counted as answeredThe Marquise de Cat scores victory points each time she builds one of her buildings—specifically a workshop, sawmill, or recruiter [1][2]. She scores more points for each additional building of the same type she has on the map [1][2].
Strategy guides → — community tips, kept separate from rulings
🔧 debug — where this ruling came from
- outcome
- ANSWERED — Answered
- corpus profile
- live
- answerer pin (deploy-frozen, attribution only)
- unset-dev (corpus lane freezes the deploy value)
- timings
- search 102 ms · ask 2895 ms · total 3008 ms
- single-flight (PR-5)
- queued 0 ms · generation 3008 ms
- retrieval refs (raw)
- [{"page": 10, "score": 0.032522, "snippet": "/The Marquise de Cat occupies the Woodland and wants to turn it into an industrial and military powerhouse. Each time the Marquise builds one of her buildings -a workshop, sawmill, or recruiter-she scores victory points. /The more of the same building she has on the map, the more points she scores. ", "headingPath": "Marquise de Cat", "sharpsignalDocId": 57}, {"page": 5, "score": 0.032266, "snippet": "/The Marquise de Cat occupies the Woodland and wants to turn it into an industrial and military powerhouse. Each time the Marquise builds one of her buildings-a workshop, sawmill, or recruiter-she scores victory points. /The more of the same building she has on the map, the more points she scores. H", "headingPath": "6.1 Overview", "sharpsignalDocId": 56}, {"page": 2, "score": 0.031754, "snippet": "You can win in one of two ways: score 30 victory points or play and complete a dominance card � Dominance cards cannot be played early in the game, so we recommend learning about them later-they are described more on page 21� In Root, you will play one of four factions� Each scores victory points in", "headingPath": "Victory and Gaining Victory Points", "sharpsignalDocId": 57}, {"page": 12, "score": 0.029911, "snippet": "First, you may cra/ft any number of cards, using roosts� /Then, you must resolve the Decree, starting with the le/ftmost column and moving right� In each column, you may resolve cards in any order� For each card in a column, you must take the action listed by the column in a clearing matching the ca", "headingPath": "Daylight", "sharpsignalDocId": 57}, {"page": 20, "score": 0.015873, "snippet": "He exhausts a sword to battle the Marquise. /The Marquise doesn't play an ambush card. /The Vagabond then rolls the dice, rolling a 1 and a 1. /The Vagabond deals one hit and moves the Marquise's relationship marker to Hostile. /The Marquise also deals one hit, so the Vagabond chooses to damage the ", "headingPath": "/The First Battle", "sharpsignalDocId": 57}, {"page": 20, "score": 0.015385, "snippet": "Undeterred, he exhausts his second sword to battle again. /The Marquise doesn't play an ambush card. /The Vagabond then rolls the dice, rolling a 2 and a 0. With only one undamaged sword, the Vagabond can only deal one hit. Because he removed a warrior of a Hostile faction, the Vagabond scores one p", "headingPath": "/The Second Battle", "sharpsignalDocId": 57}, {"page": 5, "score": 0.015152, "snippet": "6.2.1 Cra/fting. /The Marquise cra/fts during Daylight by activating workshops. 6.2.2 /The Keep. /The Marquise can place pieces in the clearing with the keep token, and other players cannot. (Pieces may be moved into it. If the keep is removed, there is no way to place it on the map again.) 6.2.3 Fi", "headingPath": "6.2 Faction Rules and Abilities", "sharpsignalDocId": 56}, {"page": 22, "score": 0.014925, "snippet": "Eyrie versus Marquise is an ideal two-player learning game� /The Eyrie must grow explosively to keep the Marquise in check� Two-player Alliance games offer Alliance players a chance to hone their skills in difficult situations� /They will usually fare better against the Eyrie, but well-timed revolts", "headingPath": "Three Players", "sharpsignalDocId": 57}]
- citations (raw)
- [{"page": 5, "quote": null, "headingPath": "6.1 Overview", "sharpsignalDocId": 56}, {"page": 10, "quote": null, "headingPath": "Marquise de Cat", "sharpsignalDocId": 57}]
- boost provenance — errata + base rulebook (E2/E3)
- gate not evaluated for this ruling (boost, supersedence, and wrench all off at ask time), and the base-rulebook arm went unrecorded for the same reason — the wrench that would have stored it was off; rulesage.errata.boost-enabled=false, rulesage.errata.supersedence-enabled=false
- 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 7, 2026 21:06
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 Root — Learning to Play (corpus doc 57) | Marquise de Cat | p.10 | 0.032522 (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 Root — Law of Root (corpus doc 56) | 6.1 Overview | p.5 | 0.032266 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #3 | RULEBOOK Root — Learning to Play (corpus doc 57) | Victory and Gaining Victory Points | p.2 | 0.031754 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #4 | RULEBOOK Root — Learning to Play (corpus doc 57) | Daylight | p.12 | 0.029911 (inside the measured healthy band 0.016–0.033 (measured on two-arm asks; this ruling's arm count was never recorded)) | 300 |
| #5 | RULEBOOK Root — Learning to Play (corpus doc 57) | /The First Battle | p.20 | 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 |
| #6 | RULEBOOK Root — Learning to Play (corpus doc 57) | /The Second Battle | p.20 | 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) | 300 |
| #7 | RULEBOOK Root — Law of Root (corpus doc 56) | 6.2 Faction Rules and Abilities | p.5 | 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) | 300 |
| #8 | RULEBOOK Root — Learning to Play (corpus doc 57) | Three Players | p.22 | 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) | 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 Root — Law of Root (corpus doc 56) | 6.1 Overview | p.5 | no quote on the wire |
| [2] | RULEBOOK Root — Learning to Play (corpus doc 57) | Marquise de Cat | p.10 | no quote on the wire |
generation — timing and the path taken
- timing split
- retrieval 102 ms · first delta n/a · total 3008 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 102 ms · ask 2895 ms · gateway work 3008 ms · total 3008 ms
- live seat (read from the running child)
- answering — gemma4:26b think:false · num_ctx 32768 (live-verified 53s 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
- 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 6), 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.