Ruling — D-Day at Omaha Beach

You asked

How do I play?

Answered counted as answered

Asked with: D-Day at Omaha Beachbg-29603-en-1e

DDOB is played in turns.[1] Each turn consists of several phases, conducted in the following sequence:[1]

1. US Amphibious Operations Phase: Draw a landing card and apply its results to US units in Beach Landing boxes in the East Sector, then draw a second landing card and apply its results to units in Beach Landing Boxes in the West Sector.[1] Conduct landing checks in each sector in which units are in beach landing boxes, beginning with the East sector, to determine if units are affected by hazards.[2] Land all units remaining in Beach Landing Boxes by moving each to the corresponding waterline/beach hex.[1] Take units in the current turn of the Turn Track and place them in the Beach Landing Boxes listed on the units.[1]

2. Event Phase (skip on Turn 1): Draw an event card and implement the event listed for the current turn.[1]

3. German Fire Phase: Draw a fire card and conduct German fire against US units in the East sector, then draw a second fire card and conduct fire in the West Sector.[1] Occupied German positions that match the colors shown on the fire card fire at US units in the position's field of fire.[1] Check to see which US units are hit by fire and apply disruption, step losses, or elimination as called for.[1] Beginning Turn 4, if the fire card includes a German artillery value, check to see if a US unit in the sector is hit by artillery fire.[1]

4. US Engineer Phase (skip on Turn 1): Beginning with Turn 2, you may clear obstacles in one or two beach obstacle hexes in each sector, provided they are not in the field of fire of any non-disrupted German positions whose color appears on the fire card drawn for that sector.[3]

5. US Action Phase: Perform actions with US units, which include movement, attack, and barrage.[1] In each US division, two units or stacks may perform actions; additionally, certain units (such as infantry performing a preservation move, ranger infantry, units with specific markers, or HQ/General units) may perform actions "for free".[1]

At the end of a turn, move all cards from the card track to the discard pile and move the Phase marker back to the beginning of the card track.[2] If the turn track indicates, shuffle all discards back into the deck.[2] Move the turn marker one turn ahead on the Turn Track.[2]

The game ends when either the US division suffers a catastrophic loss or the end of the scenario is reached, at which time victory points are calculated.[2]

[1] RULEBOOK D-Day at Omaha Beach — Rulebook · p.8 · 4. seQUenCe oF PLAY · I. US Amphibious Operations Phase · II. Event Phase (skip on Turn 1) · III. German Fire Phase · IV. US Engineer Phase (skip on Turn 1) · V. US Action Phase

[2] RULEBOOK D-Day at Omaha Beach — Rulebook · p.8 · VI. End of Turn · 5. Us AMPHIBIoUs oPeRAtIons · 5.1 Landing Checks

[3] RULEBOOK D-Day at Omaha Beach — Rulebook · p.21 · 9.4 German Tactical Reinforcements triggered by a WN Depth Marker · 9.5 Releasing Kampfgruppe Meyer · 10. Us enGIneeR BeACH oBstACLe DeMoLItIon · 10.1 Clearing Beach Obstacles

The sage rests. The game continues.

🔧 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 77 ms · ask 8897 ms · total 12970 ms
single-flight (PR-5): queued 3993 ms · generation 8977 ms
retrieval refs (raw) — what the PASSAGE SEARCH returned, not what the answerer read: [{"page": 7, "score": 0.04918, "snippet": "Every card in the 54-card deck is divided into three sections. A 55th card summarizes US actions and should be removed from the deck for reference during play. During play, draw cards from the deck and look at the appropriate section: The Landing Results section determines how US units are affected ", "headingPath": "2.3 The Cards · 2.4 Charts & Tables · 3. settInG UP FoR PLAY", "sharpsignalDocId": 741}, {"page": 8, "score": 0.045079, "snippet": "DDOB is played in turns. Each turn consists of several phases, conducted in the following sequence. Move the Phase marker along the Card/Phase track to keep track of the current phase. During the course of the turn you will draw several cards, each for a different function. As you draw each card, pl", "headingPath": "4. seQUenCe oF PLAY · I. US Amphibious Operations Phase · II. Event Phase (skip on Turn 1) · III. German Fire Phase · IV. US Engineer Phase (skip on Turn 1) · V. US Action Phase", "sharpsignalDocId": 741}, {"page": 8, "score": 0.044854, "snippet": "Move all cards from the card track to the discard pile, and move the Phase marker back to the beginning of the card track. If the turn track indicates that the cards are to be shuffled, shuffle all discards back into the deck. Move the turn marker one turn ahead on the Turn Track. Keep playing turns", "headingPath": "VI. End of Turn · 5. Us AMPHIBIoUs oPeRAtIons · 5.1 Landing Checks", "sharpsignalDocId": 741}, {"page": 5, "score": 0.043015, "snippet": "tions may be occupied by German reinforcement units entering during play. Most reinforcement positions have an ID letter/number consisting of a Zone Letter (from A to G) and a Reinforcement Priority Number (from 1 to 11), used to determine when and where German reinforcements appear. Blank reinforce", "headingPath": "German Reinforcement Positions . These posi-", "sharpsignalDocId": 741}, {"page": 8, "score": 0.042803, "snippet": "Set up The First Waves or D-Day at Omaha Beach scenario as follows: Prepare the German Widerstandsnests. Mix together the 18 WN depth markers, face down. Place an unrevealed depth marker in the following nine WN positions: 60, 61, 62N, 65N, 66N, 68N, 70, 72N, 73. Place the remaining WN depth markers", "headingPath": "3. settInG UP FoR PLAY", "sharpsignalDocId": 741}, {"page": 15, "score": 0.042499, "snippet": "When playing with two players, a unit that moves just one hex across the boundary remains in its original division's control. A unit that moves more than one hex beyond the boundary comes under the control of the other division. Conduct this action to move a unit of any type one hex in any direction", "headingPath": "7.2 Conducting Actions · 7.3 Action: Move One Hex", "sharpsignalDocId": 741}, {"page": 5, "score": 0.041214, "snippet": "Time Scale : The turn track covers a twelve hour period beginning at 0615 hours on June 6 1944. The first 16 turns each represent 15 minutes of time. Beginning with turn 17, each turn represents 30 minutes. The Card/Phase Track. As you draw cards during each turn, place each card in the box matching", "headingPath": "German Reinforcement Positions . These posi-", "sharpsignalDocId": 741}, {"page": 26, "score": 0.039412, "snippet": "An unoccupied position may perform an action allowed it by the German Action Summary, regardless of whether the color symbol is single or double. Sequencing Actions. In the rare event that the sequencing of German Actions affects play, conduct the action for the higher numbered position first. If th", "headingPath": "16. GeRMAn ACtIons", "sharpsignalDocId": 741}]
citations (raw) — what the answer cited, chosen from a retrieval this page cannot show: [{"page": 8, "quote": null, "headingPath": "4. seQUenCe oF PLAY · I. US Amphibious Operations Phase · II. Event Phase (skip on Turn 1) · III. German Fire Phase · IV. US Engineer Phase (skip on Turn 1) · V. US Action Phase", "sharpsignalDocId": 741}, {"page": 8, "quote": null, "headingPath": "VI. End of Turn · 5. Us AMPHIBIoUs oPeRAtIons · 5.1 Landing Checks", "sharpsignalDocId": 741}, {"page": 21, "quote": null, "headingPath": "9.4 German Tactical Reinforcements triggered by a WN Depth Marker · 9.5 Releasing Kampfgruppe Meyer · 10. Us enGIneeR BeACH oBstACLe DeMoLItIon · 10.1 Clearing Beach Obstacles", "sharpsignalDocId": 741}]
boost provenance — errata + base rulebook (E2/E3): no registered errata card matched this query; base rulebook doc 741 boosted; rulesage.errata.boost-enabled=true, rulesage.errata.supersedence-enabled=true
base rulebook doc 741 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.93747 of 2015 non-space chars (floor 0.45); 0 glyph-index tokens (max 2)
debug row retained until: Nov 22, 2026 16:19 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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	2.3 The Cards · 2.4 Charts & Tables · 3. settInG UP FoR PLAY	p.7	0.04918 (at the 3-arm ceiling (0.04918) — every arm ranked it #1)	300
#2	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	4. seQUenCe oF PLAY · I. US Amphibious Operations Phase · II. Event Phase (skip on Turn 1) · III. German Fire Phase · IV. US Engineer Phase (skip on Turn 1) · V. US Action Phase	p.8	0.045079 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	VI. End of Turn · 5. Us AMPHIBIoUs oPeRAtIons · 5.1 Landing Checks	p.8	0.044854 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	German Reinforcement Positions . These posi-	p.5	0.043015 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	3. settInG UP FoR PLAY	p.8	0.042803 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	7.2 Conducting Actions · 7.3 Action: Move One Hex	p.15	0.042499 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	German Reinforcement Positions . These posi-	p.5	0.041214 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	16. GeRMAn ACtIons	p.26	0.039412 (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 80 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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	3. settInG UP FoR PLAY	p.8	#5	0.042803 (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 D-Day at Omaha Beach — Rulebook (corpus doc 741)	VI. End of Turn · 5. Us AMPHIBIoUs oPeRAtIons · 5.1 Landing Checks	p.8	#3	0.044854 (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
#3	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	7.2 Conducting Actions · 7.3 Action: Move One Hex	p.15	#6	0.042499 (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
#4	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	4. seQUenCe oF PLAY · I. US Amphibious Operations Phase · II. Event Phase (skip on Turn 1) · III. German Fire Phase · IV. US Engineer Phase (skip on Turn 1) · V. US Action Phase	p.8	#2	0.045079 (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
#5	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	9.4 German Tactical Reinforcements triggered by a WN Depth Marker · 9.5 Releasing Kampfgruppe Meyer · 10. Us enGIneeR BeACH oBstACLe DeMoLItIon · 10.1 Clearing Beach Obstacles	p.21	#11	0.028624 (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
#6	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	16. GeRMAn ACtIons	p.26	#8	0.039412 (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
#7	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	9.3 German Reinforcements Triggered by Events	p.21	#15	0.027693 (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
#8	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	2.3 The Cards · 2.4 Charts & Tables · 3. settInG UP FoR PLAY	p.7	#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

chosen chunks — what the answer actually cited

#	document	heading	page	quote chars
[1]	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	4. seQUenCe oF PLAY · I. US Amphibious Operations Phase · II. Event Phase (skip on Turn 1) · III. German Fire Phase · IV. US Engineer Phase (skip on Turn 1) · V. US Action Phase	p.8	no quote on the wire
[2]	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	VI. End of Turn · 5. Us AMPHIBIoUs oPeRAtIons · 5.1 Landing Checks	p.8	no quote on the wire
[3]	RULEBOOK D-Day at Omaha Beach — Rulebook (corpus doc 741)	9.4 German Tactical Reinforcements triggered by a WN Depth Marker · 9.5 Releasing Kampfgruppe Meyer · 10. Us enGIneeR BeACH oBstACLe DeMoLItIon · 10.1 Clearing Beach Obstacles	p.21	no quote on the wire

generation — timing and the path taken

timing split: retrieval 77 ms · first delta 4751 ms · total 12970 ms (retrieval and first-delta both measured from the START of gateway work, so first-delta INCLUDES retrieval — do not subtract)
full breakdown: queued 3993 ms · retrieval 77 ms · ask 8897 ms · gateway work 8977 ms · total 12970 ms
tokens in (the prompt the answerer read): 3504
tokens out (what the answerer generated): 548
tok/sec: 132.5 tok/sec — 548 output tokens in 4.137 s of generation
live seat (read from the running child): answering — gemma4:26b think:false · num_ctx 32768 (live-verified 21s ago)
gateway schema (read from the running child): schema head 0042_definer_search_path (live revision not readable by this principal)
answerer host (measured by rulesage): reachable (for 60h, checked 9s 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 675), 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.