Ruling — Blood on the Clocktower

You asked

How do I take my turn?

Abstained — no grounded answer; closest passages below counted as honest abstain

Asked with: Blood on the Clocktowerbg-240980-en-1e

The answerer couldn't ground a confident answer in the rulebook. The closest rulebook passages are below — check them before ruling.

RULEBOOK Blood on the Clocktower — Rulebook · p.30 · RUNNING THINGS SMOOTHLY

3… 2… 1…' You don't want to hog the limelight and demand attention at the expense of the players' fun, so this visual cue-being in the center of the circle-is an easy way to let the group know you are doing something important. If you make a mistake, just play on and do your best. Don't try to 'bala

RULEBOOK Blood on the Clocktower — Rulebook · p.21 · DOES THE GAME ALWAYS END WHEN THE

W ELCOME TO THE NITTY-GRITTY ...and beyond. You don't need to read further until you've run a game or two or until you run into a thorny rules question. If you have read the previous chapters in this rulebook and the TROUBLE BREWING character almanac but would like a little practice before running y

RULEBOOK Blood on the Clocktower — Rulebook · p.30 · RUNNING THINGS SMOOTHLY

Moving tokens around in the Grimoire is something you may need to do when good players such as the Slayer or Juggler use their abilities. When evil players bluff as these characters, pretend to move tokens around the Grimoire in the same manner. Veteran players will not be able to tell by looking at

RULEBOOK Blood on the Clocktower — Rulebook · p.13 · 9. PASS OUT CHARACTER TOKENS. · NOW YOU'RE READY TO BEGIN !

Shuffle the character tokens and put them in the bag . Then, each player takes one character token out of the bag, and then passes the bag to the next player. Continue this until each player has one token. Each player looks at their character token in secret, revealing it to no one else. 10. ADD THE

RULEBOOK Blood on the Clocktower — Rulebook · p.16 · NOMINATIONS AND VOTING

C ALL FOR NOMINATIONS when you feel it is appropriate. Doing so after five to ten minutes of chit-chat is usually about right, but some groups may want to talk for longer or shorter. Make sure everyone is back in their seats at this point. Say 'I now call for nominations,' or something similar. A pl

🔧 debug — where this ruling came from

outcome: ABSTAINED — Abstained — no grounded answer; closest passages below
corpus profile: live
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 370 ms · ask 12056 ms · total 12438 ms
single-flight (PR-5): queued 0 ms · generation 12438 ms
retrieval refs (raw): [{"page": 30, "score": 0.032787, "snippet": "3… 2… 1…' You don't want to hog the limelight and demand attention at the expense of the players' fun, so this visual cue-being in the center of the circle-is an easy way to let the group know you are doing something important. If you make a mistake, just play on and do your best. Don't try to 'bala", "headingPath": "RUNNING THINGS SMOOTHLY", "sharpsignalDocId": 159}, {"page": 21, "score": 0.032258, "snippet": "W ELCOME TO THE NITTY-GRITTY ...and beyond. You don't need to read further until you've run a game or two or until you run into a thorny rules question. If you have read the previous chapters in this rulebook and the TROUBLE BREWING character almanac but would like a little practice before running y", "headingPath": "DOES THE GAME ALWAYS END WHEN THE", "sharpsignalDocId": 159}, {"page": 30, "score": 0.031746, "snippet": "Moving tokens around in the Grimoire is something you may need to do when good players such as the Slayer or Juggler use their abilities. When evil players bluff as these characters, pretend to move tokens around the Grimoire in the same manner. Veteran players will not be able to tell by looking at", "headingPath": "RUNNING THINGS SMOOTHLY", "sharpsignalDocId": 159}, {"page": 13, "score": 0.03125, "snippet": "Shuffle the character tokens and put them in the bag . Then, each player takes one character token out of the bag, and then passes the bag to the next player. Continue this until each player has one token. Each player looks at their character token in secret, revealing it to no one else. 10. ADD THE", "headingPath": "9. PASS OUT CHARACTER TOKENS. · NOW YOU'RE READY TO BEGIN !", "sharpsignalDocId": 159}, {"page": 16, "score": 0.030769, "snippet": "C ALL FOR NOMINATIONS when you feel it is appropriate. Doing so after five to ten minutes of chit-chat is usually about right, but some groups may want to talk for longer or shorter. Make sure everyone is back in their seats at this point. Say 'I now call for nominations,' or something similar. A pl", "headingPath": "NOMINATIONS AND VOTING", "sharpsignalDocId": 159}, {"page": 26, "score": 0.030366, "snippet": "To include a Traveller in your game, do the following: 1. LET THE PLAYER CHOOSE A TRAVELLER. Take the player aside and give them the Traveller sheet, which is kept under the Town Square. This sheet details which Travellers are available for this game and what their abilities are. Ask the player to c", "headingPath": "ADDING TRAVELLERS", "sharpsignalDocId": 159}, {"page": 12, "score": 0.030303, "snippet": "Likewise, we recommend you run a game or two with five to ten players to get the hang of things, then try your hand at larger games. 4. PREPARE THE TOWN SQUARE. Put the Town Square board on the floor in the center of the chairs. Put one life token per player on the Town Square matching their seating", "headingPath": "SETUP", "sharpsignalDocId": 159}, {"page": 31, "score": 0.029851, "snippet": "This also encourages players to leave their seats to talk in private to players on the opposite side of the circle, as everybody is close together. Players having private conversations with each other can be a huge part of some games, and is something that really adds new levels of strategy to both ", "headingPath": "RUNNING THINGS SMOOTHLY", "sharpsignalDocId": 159}]
citations (raw): []
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 159 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 159 boosted
answered-before recall: no past answered ruling for this game matched closely enough
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 17:58

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 Blood on the Clocktower — Rulebook (corpus doc 159)	RUNNING THINGS SMOOTHLY	p.30	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 Blood on the Clocktower — Rulebook (corpus doc 159)	DOES THE GAME ALWAYS END WHEN THE	p.21	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 Blood on the Clocktower — Rulebook (corpus doc 159)	RUNNING THINGS SMOOTHLY	p.30	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 Blood on the Clocktower — Rulebook (corpus doc 159)	9. PASS OUT CHARACTER TOKENS. · NOW YOU'RE READY TO BEGIN !	p.13	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 Blood on the Clocktower — Rulebook (corpus doc 159)	NOMINATIONS AND VOTING	p.16	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 Blood on the Clocktower — Rulebook (corpus doc 159)	ADDING TRAVELLERS	p.26	0.030366 (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 Blood on the Clocktower — Rulebook (corpus doc 159)	SETUP	p.12	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
#8	RULEBOOK Blood on the Clocktower — Rulebook (corpus doc 159)	RUNNING THINGS SMOOTHLY	p.31	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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars

generation — timing and the path taken

timing split: retrieval 370 ms · first delta 12318 ms · total 12438 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 370 ms · ask 12056 ms · gateway work 12438 ms · total 12438 ms
tokens in (the prompt the answerer read): 4484
tokens out (what the answerer generated): 9
tok/sec: 147.5 tok/sec — 9 output tokens in 0.061 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 16s 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: ABSTAINED — Abstained — no grounded answer; closest passages below
abstain rationale: I don't have enough information.
the answerer's own words, verbatim — hostile corpus/LLM text, rendered escaped

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 81), 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.