Ruling — Hadrian's Wall

You asked

How do I play?

Answered counted as answered

Asked with: Hadrian's Wallbg-304783-en-1e

The aim of the game is to be the player with the most Victory Points (VP) at the end of the 6th Year.[1] Players gain VP by developing their fort, defending walls, and increasing attributes.[1]

**Setup**

1. Shuffle the Fate Cards into a facedown Draw Pile in the centre of the playing area.[1]

2. Place all Resources and Workers (Solders, Builders, Servants, and Civilians) nearby to form the Main Supply.[1]

3. Collectively decide on a difficulty level.[1]

4. Give each player 12 Player Cards, 1 Player Board, 1 of each Sheet, and a pen or pencil.[1]

5. Players place their 2 Sheets side-by-side, with their Player Board above both Sheets.[1]

6. Each player shuffles their Player Cards and places them in a facedown Draw Pile to the left of their Player Board.[1]

**Gameplay**

* **Actions:** Most actions require players to pay a combination of Workers or Resources and then fill in one or more boxes on their Sheets.[2] Filling boxes on Tracks must be done from left-to-right.[2] Some areas, like Buildings, may be filled top-to-bottom or in any order.[2]

* **Player Cards:** Each Year, players draw the top 2 Player Cards from their Draw Pile.[3] One must be selected as a Path Card (placed facedown above the Player Board) and the other becomes a Prospect Card (placed facedown to the right of the Player Board).[3] After selection, both are turned faceup; Path Cards are tucked under Player Boards in line with the current Year, and Prospect Cards remain visible.[3] Players gain any Workers or Resources pictured in the bottom left of their Prospect Card.[3]

* **End of Year:** A Year ends once all players have stopped taking actions.[4] Any Workers and Resources still on Player Boards must be returned to the Main Supply.[4]

* **The Pict Attack:** One player draws a number of cards from the Fate Card Draw Pile (the number depends on the current Year and chosen difficulty) and places them faceup to simulate an attack.[4] Players check the Cohorts at the top of their left Sheet to see if they have enough filled boxes to repel the attacks (requiring an equal or greater number of filled boxes for every arrow revealed).[4]

* **Success:** If players defend successfully, they gain Valour equal to the number in the grey flag of the current Year.[4] If this fills a box on the Valour Track that rewards Workers or Attributes, those are gained immediately.[4]

* **Failure:** If players fail to defend, they gain Disdain for each attack that gets through, up to the amount indicated on the grey flag for that Year.[4] If they let through fewer attacks than the grey flag indicates, they gain a combination of Disdain and Valour (1 Disdain for each attack that got through, then 1 Valour for the difference).[4]

[1] RULEBOOK Hadrian's Wall — Rulebook · p.3 · AIM OF THE GAME · SETUP

[2] RULEBOOK Hadrian's Wall — Rulebook · p.6 · ACTIONS - GENERAL CONCEPTS

[3] RULEBOOK Hadrian's Wall — Rulebook · p.5 · SELECTING PLAYER CARDS

[4] RULEBOOK Hadrian's Wall — Rulebook · p.20 · SCOUTS

🔧 debug — where this ruling came from

outcome: ANSWERED — Answered
corpus profile: live,vps
answerer pin (deploy-frozen, attribution only): gemma4:26b think:false 5571076f3d70
timings: search 84 ms · ask 5194 ms · total 18226 ms
single-flight (PR-5): queued 12946 ms · generation 5280 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 3, "score": 0.04918, "snippet": "The aim of Hadrian's Wall is to be the player with the most Victory Points (VP) at the end of the 6th Year. Players gain VP by developing their fort, defending its walls and by increasing their attributes. Players will need to carefully manage their workforce and resources to accomplish their chosen", "headingPath": "AIM OF THE GAME · SETUP", "sharpsignalDocId": 323}, {"page": 22, "score": 0.047371, "snippet": "In this example, this player has scored a total of 57 VP from their Attributes (6 + 23 + 12+ 16), 11 VP from their Path Cards (conditions not shown) and -5 VP from their Final Disdain, making a total final score of 63 VP. When setting up a game for only 1-2 players, shuffle and set aside a Neutral D", "headingPath": "SCORING EXAMPLE · CHANGES FOR 1-2 PLAYERS", "sharpsignalDocId": 323}, {"page": 4, "score": 0.046898, "snippet": "Hadrian's Wall is played over 6 Years (rounds). At the beginning of each Year, players will gain a number of Workers and Resources. These will come from the current Fate Card, Prospect Cards and other benefits from specific areas of Player Sheets. Over the course of each Year, players will simultane", "headingPath": "GAMEPLAY OVERVIEW · YEAR SETUP", "sharpsignalDocId": 323}, {"page": 20, "score": 0.046176, "snippet": "Each Year ends once all players have stopped taking actions. At this point, any Workers and Resources still on Player Boards must be returned to the Main Supply. Then, have 1 player draw a number of cards from the top of the Fate Card Draw Pile, placing them faceup on the table. This is to simulate ", "headingPath": "SCOUTS", "sharpsignalDocId": 323}, {"page": 5, "score": 0.032258, "snippet": "As previously mentioned, each Year players will be drawing the top 2 Player Cards from their Draw Pile. Of these cards, 1 must be selected as a chosen Path Card, while the other will become a Prospect Card for that Year. The top section of each Player Card depicts 1 of 12 Paths. Over the course of t", "headingPath": "SELECTING PLAYER CARDS", "sharpsignalDocId": 323}, {"page": 6, "score": 0.03125, "snippet": "As a general rule, most actions will require players to pay a combination of Workers or Resources, followed by filling in 1 or more boxes on their Sheets. The term 'box' or 'boxes' refers to the white spaces on player Sheets, be they squares, circles or any other shapes. Some boxes are empty, while ", "headingPath": "ACTIONS - GENERAL CONCEPTS", "sharpsignalDocId": 323}, {"page": 19, "score": 0.029851, "snippet": "For example, this player already has 1 Diplomat on the right Cohort, and has even used 1 of their Favours. If they decided to acquire another Diplomat, they would have to serve the left or centre Cohort. An important part of defending the milecastle is effective Scouting. This action has players fil", "headingPath": "DIPLOMATS · SCOUTS", "sharpsignalDocId": 323}, {"page": 13, "score": 0.029412, "snippet": "The Market is where players can purchase various Trade Goods to boost their Renown. In order to start trading, players must first build the Market. This requires at least 4 filled boxes on the Traders Track. It also requires 1 Servant, 1 Builder and 2 Resources to be returned to the Main Supply. Onc", "headingPath": "PRECINCTS", "sharpsignalDocId": 323}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 3, "quote": null, "headingPath": "AIM OF THE GAME · SETUP", "sharpsignalDocId": 323}, {"page": 6, "quote": null, "headingPath": "ACTIONS - GENERAL CONCEPTS", "sharpsignalDocId": 323}, {"page": 5, "quote": null, "headingPath": "SELECTING PLAYER CARDS", "sharpsignalDocId": 323}, {"page": 20, "quote": null, "headingPath": "SCOUTS", "sharpsignalDocId": 323}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 323 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 323 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)
answer fence: passed — letter density 0.91220 of 2255 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 14, 2026 20:27

retrieval — what the passage search returned

what this block IS: the PASSAGE SEARCH's own results — the same search that fills this page's closest-passages list — and NOT the passages the answerer read. Answering runs its OWN retrieval: a far wider candidate pool, re-ranked down to a final handful, plus floors this search never applies — the base rulebook, surviving errata corrections, and one slot per book on a multi-book read. Each of those armed only if THIS ask sent what it needs: the boost block names the ids it forwarded, and the scope line names the books it read. A document the answer CITES that no row here names is therefore EXPECTED, not a defect: two searches, two candidate pools, two orders. The answerer's own final rows are shown in their own block below, beside these and never mixed into them.

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 Hadrian's Wall — Rulebook (corpus doc 323)	AIM OF THE GAME · SETUP	p.3	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	SCORING EXAMPLE · CHANGES FOR 1-2 PLAYERS	p.22	0.047371 (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 Hadrian's Wall — Rulebook (corpus doc 323)	GAMEPLAY OVERVIEW · YEAR SETUP	p.4	0.046898 (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 Hadrian's Wall — Rulebook (corpus doc 323)	SCOUTS	p.20	0.046176 (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 Hadrian's Wall — Rulebook (corpus doc 323)	SELECTING PLAYER CARDS	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
#6	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	ACTIONS - GENERAL CONCEPTS	p.6	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
#7	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	DIPLOMATS · SCOUTS	p.19	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 Hadrian's Wall — Rulebook (corpus doc 323)	PRECINCTS	p.13	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

what the answerer read — the passages it actually had in front of it

what this block IS: the passages the ANSWERING read put in front of the answerer, in the order it read them — the other half of the two reads described above, and the one that decides what the answer could possibly say. Each row names the book it came from and where in that book it sits, what it scored when the search arms were fused, which arm carried it there, and whether the re-ranker chose it or a floor guaranteed it a slot. A row here that no passage-search row names is EXPECTED: a far wider pool, re-ranked, with floors the passage search never applies.

candidate pool: the answering read scored 25 passages, out of a ceiling of 80 set gateway-side. Both figures are reported by the gateway for THIS ask — measurements of what actually happened, not constants read out of anyone's source and printed here on faith.

floors armed for this ask: the base rulebook — armed · surviving errata corrections — not armed · one slot per book on a multi-book read — not armed. Every floor is stated on every ask, armed or not, so a floor that did not apply here is never mistaken for one this app does not know about.

arms fused for this ask: vector + full-text + the doc-priority boost arm. Stated separately from the rows because an arm that ran and carried nothing is a different fact from an arm that never ran.

read at	document	heading	page	fused rank	fused RRF score	carried by	how it got its slot
#1	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	SCOUTS	p.20	#4	0.046176 (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))	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#2	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	ACTIONS - GENERAL CONCEPTS	p.6	#6	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))	vector + the doc-priority boost arm	the re-ranker chose it
#3	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	AIM OF THE GAME · SETUP	p.3	#1	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	vector + full-text + the doc-priority boost arm	the re-ranker chose it
#4	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	CITIZEN TRACKS · PRECINCTS	p.12	#16	0.013158 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#5	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	GARDENS · TEMPLES	p.16	#21	0.012346 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#6	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	SELECTING PLAYER CARDS	p.5	#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))	vector + the doc-priority boost arm	the re-ranker chose it
#7	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	THEATRE · LUDUS GLADIATORIOUS	p.14	#9	0.014493 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it
#8	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	GRANARIES	p.9	#10	0.014286 (below 0.016, the low end of the measured band — a weak fuse (that band was taken on two-arm asks; only its low end, one arm's #1 vote, carries over to a 3-arm one))	vector	the re-ranker chose it

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	AIM OF THE GAME · SETUP	p.3	no quote on the wire
[2]	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	ACTIONS - GENERAL CONCEPTS	p.6	no quote on the wire
[3]	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	SELECTING PLAYER CARDS	p.5	no quote on the wire
[4]	RULEBOOK Hadrian's Wall — Rulebook (corpus doc 323)	SCOUTS	p.20	no quote on the wire

generation — timing and the path taken

timing split: retrieval 84 ms · first delta 1950 ms · total 18226 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 12946 ms · retrieval 84 ms · ask 5194 ms · gateway work 5280 ms · total 18226 ms
tokens in (the prompt the answerer read): 3718
tokens out (what the answerer generated): 653
tok/sec: 199.9 tok/sec — 653 output tokens in 3.267 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 15s 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 251), 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.