Ruling — Memoir '44

← Memoir '44

You asked

How do I play?

Answered counted as answered

Asked with: Memoir '44bg-10630-en-1e

To play the game, follow these steps:

Setup

1. Assemble the cardholder segments and place them on the long edges of the board, if you want to use them.[1]

2. Choose each player's side and sit in front of the board accordingly.[1]

3. Shuffle the command card deck thoroughly.[1]

4. Deal command cards as indicated by the scenario's briefing notes.[1]

5. Keep your command cards secret from the opposing player.[1]

6. Place the remainder of the command card deck face down, next to the board, within easy reach of both players.[1]

7. Each side takes four attack dice.[1]

A Turn

1. The starting player, as indicated in the scenario's briefing notes, begins play by selecting and playing one command card from their hand of cards.[2][3][1][4]

2. Place the played card face up next to the board, facing you, and read it aloud.[5]

3. After playing a command card, announce which corresponding unit(s) you choose to order.[5]

4. Moves are announced and made successively, one ordered unit at a time, in the sequence of your choice.[5]

5. An ordered unit may move, attack, or take a special action (if the card allows), though it does not have to move.[5]

[1] RULEBOOK Memoir '44 — Rulebook · p.3 · -SETTING UP THE GAME -

[2] RULEBOOK Memoir '44 — Rulebook · p.3

[3] RULEBOOK Memoir '44 — Rulebook · p.3

[4] RULEBOOK Memoir '44 — Rulebook · p.3

[5] RULEBOOK Memoir '44 — Rulebook · p.4 · 1 - PLAY A COMMAND CARD · SECTION CARDS · TACTIC CARDS · 2 - ORDER UNITS · 3 - MOVE UNITS

That settles it — whose turn was it?

🔧 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 102 ms · ask 6588 ms · total 7792 ms
single-flight (PR-5): queued 1100 ms · generation 6692 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 12, "score": 0.04918, "snippet": "The best way to introduce children to the game is to play in teams with adults. For that, you can play the following simplified team mode: Make two teams of up to 3 players per side (if you have an odd number of players, simply put one more player on one side than on the other). O In 3-player teams,", "headingPath": "TEAM PLAY WITH YOUNG GENERALS", "sharpsignalDocId": 234}, {"page": 4, "score": 0.047875, "snippet": "At the start of your turn, play one command card from your hand. Place it face up next to the board, facing you, and read it aloud. Units may only move and/or attack when given an order. The card you play will usually indicate which section(s) of the battle -field you may issue orders, and how many ", "headingPath": "1 - PLAY A COMMAND CARD · SECTION CARDS · TACTIC CARDS · 2 - ORDER UNITS · 3 - MOVE UNITS", "sharpsignalDocId": 234}, {"page": 4, "score": 0.047183, "snippet": "The object of the game is to be the first to win a set number of victory medals (usually 4 to 6, depending on the selected sce -nario's victory conditions). In Memoir '44, a victory medal is gained for each enemy unit entirely eliminated from the battlefield. Each medal won is des -ignated by placin", "headingPath": "-OBJECT OF THE GAME - · -GAME TURN - · BATTLEFIELD · ON YOUR TURN, FOLLOW THE SEQUENCE BELOW:", "sharpsignalDocId": 234}, {"page": 3, "score": 0.046394, "snippet": "Assemble the cardholder segments and place them on the long edges of the board, if you want to use them. Choose each player's side and sit in front of the board accordingly. Given the relatively short duration of a typical scenario and to help balance any historical advantage, we recommend playing f", "headingPath": "-SETTING UP THE GAME -", "sharpsignalDocId": 234}, {"page": 12, "score": 0.045235, "snippet": "O For a player on their own, command cards are dealt as usual. Note: in some scenarios, like Pegasus Bridge, a side may start with less than 4 cards and will draw additional command cards during the game. In such cases, the starting cards must be dealt so that there is always one shared card, and th", "headingPath": "-APPENDIX 4 -AIR SUPERIORITY · 3- GAME TURN", "sharpsignalDocId": 234}, {"page": 3, "score": 0.043636, "snippet": "Place the remainder of the command card deck face down, next to the board, within easy reach of both players. 12. 12. Each side takes four attack dice. 13. 13. The starting player, as indicated in the scenario’s briefing notes (in Pegasus Bridge, the Allies), begins play by selecting and playing one", "headingPath": "", "sharpsignalDocId": 234}, {"page": 2, "score": 0.043155, "snippet": "The game mechanics, although simple, will still require strategic card play, timely dice rolling and an aggressive, yet flexible battle plan to achieve victory. Welcome and Enjoy!", "headingPath": "", "sharpsignalDocId": 234}, {"page": 3, "score": 0.040775, "snippet": "44 -- SETTING UP THE GAME SETTING UP THE GAME -- We strongly recommend that you follow the step-by-step approach outlined below when setting up a scenario in Memoir '44, espe- cially for your first few plays. The reward is a smooth setup for the endless variety of battlefields, allowing you to focus", "headingPath": "", "sharpsignalDocId": 234}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 3, "quote": null, "headingPath": "-SETTING UP THE GAME -", "sharpsignalDocId": 234}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 234}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 234}, {"page": 3, "quote": null, "headingPath": "", "sharpsignalDocId": 234}, {"page": 4, "quote": null, "headingPath": "1 - PLAY A COMMAND CARD · SECTION CARDS · TACTIC CARDS · 2 - ORDER UNITS · 3 - MOVE UNITS", "sharpsignalDocId": 234}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 234 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 234 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.88413 of 958 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row recorded: Aug 25, 2026 17:01 UTC

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 Memoir '44 — Rulebook (corpus doc 234)	TEAM PLAY WITH YOUNG GENERALS	p.12	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)	1 - PLAY A COMMAND CARD · SECTION CARDS · TACTIC CARDS · 2 - ORDER UNITS · 3 - MOVE UNITS	p.4	0.047875 (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 Memoir '44 — Rulebook (corpus doc 234)	-OBJECT OF THE GAME - · -GAME TURN - · BATTLEFIELD · ON YOUR TURN, FOLLOW THE SEQUENCE BELOW:	p.4	0.047183 (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 Memoir '44 — Rulebook (corpus doc 234)	-SETTING UP THE GAME -	p.3	0.046394 (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 Memoir '44 — Rulebook (corpus doc 234)	-APPENDIX 4 -AIR SUPERIORITY · 3- GAME TURN	p.12	0.045235 (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 Memoir '44 — Rulebook (corpus doc 234)		p.3	0.043636 (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 Memoir '44 — Rulebook (corpus doc 234)		p.2	0.043155 (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))	179
#8	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	0.040775 (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 55 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 Memoir '44 — Rulebook (corpus doc 234)	1 - PLAY A COMMAND CARD · SECTION CARDS · TACTIC CARDS · 2 - ORDER UNITS · 3 - MOVE UNITS	p.4	#2	0.047875 (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 Memoir '44 — Rulebook (corpus doc 234)	TEAM PLAY WITH YOUNG GENERALS	p.12	#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
#3	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	#20	0.024786 (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 re-ranker chose it
#4	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.2	#16	0.026257 (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 re-ranker chose it
#5	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.2	#7	0.043155 (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
#6	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	#13	0.027027 (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 re-ranker chose it
#7	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)	-SETTING UP THE GAME -	p.3	#4	0.046394 (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
#8	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	#6	0.043636 (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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)	-SETTING UP THE GAME -	p.3	no quote on the wire
[2]	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	no quote on the wire
[3]	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	no quote on the wire
[4]	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)		p.3	no quote on the wire
[5]	RULEBOOK Memoir '44 — Rulebook (corpus doc 234)	1 - PLAY A COMMAND CARD · SECTION CARDS · TACTIC CARDS · 2 - ORDER UNITS · 3 - MOVE UNITS	p.4	no quote on the wire

generation — timing and the path taken

timing split: retrieval 102 ms · first delta 4380 ms · total 7792 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 1100 ms · retrieval 102 ms · ask 6588 ms · gateway work 6692 ms · total 7792 ms
tokens in (the prompt the answerer read): 2612
tokens out (what the answerer generated): 300
tok/sec: 132.0 tok/sec — 300 output tokens in 2.272 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 47s ago)
answerer host (measured by rulesage): reachable (for 22h, checked 6s ago)
answerer node (the seat proxy's own header — this probe, not this ask): node1
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 160), 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.