Ruling — Blood Bowl: Team Manager – The Card Game

← Blood Bowl: Team Manager – The Card Game

You asked

Before anyone takes a turn, how is everything laid out on the table?

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

Asked with: Blood Bowl: Team Manager – The Card Gamebg-90137-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 Bowl: Team Manager – The Card Game — Rulebook · p.8 · Maintenance Phase

During this phase, each manager prepares his team and staff for the upcoming week. Perform the following steps in order (all managers may perform steps 1-2 simultaneously): Refresh Cards: Each manager refreshes all exhausted cards in his play area by rotating them to their upright position (see 'Upg

RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook · p.8 · Matchup Phase · Types of Matchups

The Matchup phase is the heart of the game experience. During this phase, teams compete against other teams in head-to-head matchups. Generally speaking, the more matchups a team wins, the more it improves and the more fans it accumulates. Each manager typically has six turns over the course of the

RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook · p.20 · The Maintenance Phase · The Matchup phase · The Scoreboard Phase · Cheating Token Quantities · Cheating (mandatory) · Passing (optional) · …

Refresh Cards Replenish Hand Restock the Cheating Token Pool Reveal the Spike! Magazine Card Roll the Highlights Prepare for Kickoff Commit One Player to a Matchup or Pass (mandatory) Resolve When Played Abilities Use Skills Resolve One Matchup Action (optional) Resolve Matchups Reveal Cheating Toke

RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook · p.11 · Player States · Resolving Matchup actions

A player can be in three possible states: standing , downed , and injured . Standing: When a manager commits a player to a highlight, he places the Player card perpendicular to the Highlight card in an upright position in his team zone. This position indicates that he is standing. While a player is

RULEBOOK Blood Bowl: Team Manager – The Card Game — Rulebook · p.10 · Cheating · Passing

Cheating is mandatory . For each cheating icon, assign the player one cheating token. To assign a cheating token, draw one random cheating token from the pool and place it facedown (skull side up) on the Player card without looking at it . Cheating tokens are revealed and resolved during the Scorebo

🔧 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 300 ms · ask 7812 ms · total 8123 ms
single-flight (PR-5): queued 0 ms · generation 8123 ms
retrieval refs (raw): [{"page": 8, "score": 0.032787, "snippet": "During this phase, each manager prepares his team and staff for the upcoming week. Perform the following steps in order (all managers may perform steps 1-2 simultaneously): Refresh Cards: Each manager refreshes all exhausted cards in his play area by rotating them to their upright position (see 'Upg", "headingPath": "Maintenance Phase", "sharpsignalDocId": 487}, {"page": 8, "score": 0.032258, "snippet": "The Matchup phase is the heart of the game experience. During this phase, teams compete against other teams in head-to-head matchups. Generally speaking, the more matchups a team wins, the more it improves and the more fans it accumulates. Each manager typically has six turns over the course of the ", "headingPath": "Matchup Phase · Types of Matchups", "sharpsignalDocId": 487}, {"page": 20, "score": 0.031746, "snippet": "Refresh Cards Replenish Hand Restock the Cheating Token Pool Reveal the Spike! Magazine Card Roll the Highlights Prepare for Kickoff Commit One Player to a Matchup or Pass (mandatory) Resolve When Played Abilities Use Skills Resolve One Matchup Action (optional) Resolve Matchups Reveal Cheating Toke", "headingPath": "The Maintenance Phase · The Matchup phase · The Scoreboard Phase · Cheating Token Quantities · Cheating (mandatory) · Passing (optional) · …", "sharpsignalDocId": 487}, {"page": 11, "score": 0.03125, "snippet": "A player can be in three possible states: standing , downed , and injured . Standing: When a manager commits a player to a highlight, he places the Player card perpendicular to the Highlight card in an upright position in his team zone. This position indicates that he is standing. While a player is ", "headingPath": "Player States · Resolving Matchup actions", "sharpsignalDocId": 487}, {"page": 10, "score": 0.030769, "snippet": "Cheating is mandatory . For each cheating icon, assign the player one cheating token. To assign a cheating token, draw one random cheating token from the pool and place it facedown (skull side up) on the Player card without looking at it . Cheating tokens are revealed and resolved during the Scorebo", "headingPath": "Cheating · Passing", "sharpsignalDocId": 487}, {"page": 13, "score": 0.030303, "snippet": "This section further explains certain steps of the Scoreboard phase, such as revealing cheating tokens, determining the winner, and collecting payouts. At the beginning of each Scoreboard phase, the first manager flips all assigned cheating tokens at the matchup faceup. Apply revealed cheating token", "headingPath": "Scoreboard Phase in Detail · Reveal Cheating Tokens · Determine Winner · Collect Payouts · Highlight Payouts", "sharpsignalDocId": 487}, {"page": 9, "score": 0.029851, "snippet": "If a manager does not wish to (or cannot) commit a Player card, he must pass. A manager who passes cannot commit any more players or resolve matchup actions for the remainder of the Matchup phase. He may also discard any Player cards that he does not wish to keep for next round. After all managers h", "headingPath": "Types of Matchups · Scoreboard Phase", "sharpsignalDocId": 487}, {"page": 9, "score": 0.029412, "snippet": "To commit a player to a highlight, the manager takes one Player card from his hand and places it perpendicular to the Highlight card in one of that highlight's teaM zones (see 'Committing Players' on page 10). Each highlight consists of two team zones: one to the left and one to the right of the Hig", "headingPath": "Committing Players to a Highlight", "sharpsignalDocId": 487}]
citations (raw): []
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 487 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 487 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 7, 2026 05:55

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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Maintenance Phase	p.8	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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Matchup Phase · Types of Matchups	p.8	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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	The Maintenance Phase · The Matchup phase · The Scoreboard Phase · Cheating Token Quantities · Cheating (mandatory) · Passing (optional) · …	p.20	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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Player States · Resolving Matchup actions	p.11	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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Cheating · Passing	p.10	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 Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Scoreboard Phase in Detail · Reveal Cheating Tokens · Determine Winner · Collect Payouts · Highlight Payouts	p.13	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 Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Types of Matchups · Scoreboard Phase	p.9	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 Blood Bowl: Team Manager – The Card Game — Rulebook (corpus doc 487)	Committing Players to a Highlight	p.9	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

#	document	heading	page	quote chars

generation — timing and the path taken

timing split: retrieval 300 ms · first delta 7973 ms · total 8123 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 300 ms · ask 7812 ms · gateway work 8123 ms · total 8123 ms
tokens in (the prompt the answerer read): 4051
tokens out (what the answerer generated): 9
tok/sec: 138.5 tok/sec — 9 output tokens in 0.065 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 20s 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 418), 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.