Skip to main content
Formal Specification

Wolf in the Ditch (Belarusian Ravine Interception Game) — Formal Specification

Belarus · chase-tag · Confidence: medium

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Воўк у рове — AI-optimized specification ## General idea A wave-based ditch-crossing game whose structural core is a spatial confinement rule: the Wolf can never leave the ditch corridor, so every threat to Runners happens exactly at the moment of the jump itself (mid-air or a foot-fault landing) rather than through open-field pursuit. Two named endings diverge sharply — a simple role swap that never formally concludes, versus a pack-expansion mode that is provably bounded because every captured Runner permanently joins the hunting side. **Provenance note:** this entry's slug/filename references "Chyrvonaya shapachka i vouk" (Red Riding Hood and the Wolf), but its actual title and full rules content describe an unrelated game, "Воўк у рове" (Wolf in the Ditch). This spec formalizes the entry's actual described content per this task's boundaries (specs only, no entry edits); the naming mismatch is noted here for the record. ## Formal model - **Abstraction taken:** Real jump distance, mid-air tag timing, and landing precision are abstracted into stochastic per-jump outcomes, since the entry describes them qualitatively without numeric models. The 5-second hesitation timeout (entry §2.3), by contrast, is treated as an exact deterministic rule. - **Player/agent count:** 1-2 Wolves, confined to the ditch corridor; K Runners, K in [5, 23]. - **Turn model:** Wave-based — the Wolf issues a crossing call, all Runners attempt to cross simultaneously, the wave resolves, then the next wave begins. ## Formal rules R1. Setup (entry §1): a ditch corridor 1.5-2 m wide is drawn across the field; 1-2 Wolves take position inside it; all Runners assemble on one bank. R2. Session mode: exactly one of `role_swap_mode` (entry §4.2) or `pack_expansion_mode` (entry §4.3) is fixed for the whole session [gap-fill: presented as named alternative variants rather than a per-wave choice, consistent with how dual-ruleset entries are handled elsewhere in this batch]. R3. Crossing call (entry §2.1): the Wolf submits `call_crossing()`, triggering the wave. R4. Crossing attempt (entry §2.2-2.3): each Runner not yet captured must submit `jump_across()` within 5 seconds of the call; a Runner who has not begun their jump when the 5-second window elapses is automatically captured (a deterministic timeout, not a stochastic check). R5. Wolf confinement (entry §3.1): the Wolf's `move(direction)` action is only ever legal within the ditch corridor's boundary lines; leaving onto either bank is not a member of the legal action set. R6. Jump resolution (entry §3.2-3.3): a `jump_across()` resolves a stochastic outcome — clean clearance (Runner reaches the far bank safely, unless tagged, R7), or a foot-fault landing inside the ditch ("fell into the ravine," entry §3.2), which is an automatic capture regardless of tagging. R7. Mid-air tag (entry §3.3): while a Runner's `jump_across()` is in progress (airborne over the ditch) or if they have fallen into the ditch, the Wolf may submit `tag(runner_id)`, resolving a stochastic success check; success captures that Runner. R8. Capture consequence — role swap mode (entry §4.2): a captured Runner becomes the new Wolf for the next wave; the previous Wolf (or Wolves) rejoin the Runner pool [gap-fill: the entry does not state what happens to the outgoing Wolf(s) under this mode, especially when 2 Wolves exist; rejoining the Runner pool is the minimal reading, mirroring how other role-swap games in this batch handle the outgoing role-holder]. R9. Capture consequence — pack expansion mode (entry §4.3): a captured Runner joins the Wolf pack permanently, entering the ditch as an additional "wolf cub"; they never return to the Runner pool. Waves (R3-R7) repeat with the growing pack until exactly one uncaught Runner remains. R10. Victory (entry §5, pack expansion mode only): the last surviving uncaught Runner is declared the most agile jumper of the village; this is the mode's formal win condition. ## Edge cases - Tie at the end: not applicable in `pack_expansion_mode` — R10 triggers the instant exactly one Runner remains, which is by definition a unique outcome; not applicable in `role_swap_mode`, which has no terminal state to tie at. - A player with no legal move: not applicable — every Runner not yet captured always has `jump_across()` available (or is deterministically captured for not attempting it, R4); the Wolf always has `move`/`tag` available within the corridor. - Repetition / cycles: in `role_swap_mode`, the Wolf role can rotate indefinitely among the same players with no formal stopping point, consistent with the entry's silence on a win condition for that variant. In `pack_expansion_mode`, no repetition is possible in the relevant sense, since the Runner pool strictly and permanently shrinks every wave that captures anyone (R9). - Simultaneous claims on one position: not applicable — multiple Runners jump simultaneously (R4) but each resolves independently (R6-R7); there is no shared contested position between Runners. - Elimination mid-round and turn-order repair: not applicable to `role_swap_mode` (no elimination, only relabeling). In `pack_expansion_mode`, a captured Runner is permanently removed from the Runner pool and added to the Wolf pack (R9); remaining Runners' wave participation is otherwise unaffected. - Resource exhaustion: not applicable — no consumable resource; the ditch and crossing mechanic are reused every wave. - Termination guarantee: `pack_expansion_mode` is provably bounded — the Runner pool is finite (K) and strictly, permanently non-increasing every wave that captures at least one Runner (R9), and every wave carries a non-zero probability of at least one capture (R6-R7, plus the deterministic R4 timeout path), so the pool reaches exactly 1 with probability 1 in finite expected waves, triggering R10. `termination_guaranteed: true` in the frontmatter reflects this mode, which also carries the entry's only explicit win condition (§5). `role_swap_mode`, by contrast, has no formal terminal state, exactly as noted in the Repetition/cycles edge case above. ## State representation - Persistent (session) state: `mode` (fixed, R2), `wolf_ids` (set, grows in `pack_expansion_mode` or stays size 1-2 in `role_swap_mode`), `runner_ids` (set, shrinks permanently in `pack_expansion_mode`). - Per-wave ephemeral state: `jump_in_progress[runner]`, `captured_this_wave` (set). - Observable information: fully observable — all positions, corridor boundaries, and pool memberships are public; no hidden information. ## Action space - `call_crossing()`: any current Wolf; precondition: new wave ready to begin. - `jump_across()`: any un-captured Runner; precondition: within the 5-second window after `call_crossing()` (R4). - `move(direction)`: any Wolf; precondition: destination within the ditch corridor (R5). - `tag(runner_id)`: any current Wolf; precondition: `runner_id` is airborne over the ditch or has fallen into it. ## Playability notes - Single-player-vs-AI: natural in `pack_expansion_mode` — a human Runner tries to survive successive waves against an AI-controlled, growing Wolf pack; also workable as a human Wolf hunting AI Runners. - Reducing K > 4 to 2 agents: mechanically consistent in either mode, though `pack_expansion_mode`'s escalating-pack drama depends on there being enough Runners for multiple waves to matter. - Physical-skill games: real horizontal jump distance, mid-air reaction, and landing precision are the entire game and are collapsed into the stochastic clearance and tag checks (R6-R7); no genuine athleticism is modeled. - What is lost: the actual explosive jumping power and courage-under-pressure of leaping over a real ditch under direct threat, the traditional call-and-response dialogue ("Козы, у лес!"), and the escalating tension of the expanding-ditch variant. ## Implementation hints State is modest (pool memberships, per-wave jump status); the real design difficulty is calibrating clearance and tag-success probabilities, neither of which the source quantifies. First milestone: implement `pack_expansion_mode`'s wave loop (R3-R9) with flat probabilities to validate the guaranteed single-survivor termination (R10), then add `role_swap_mode` as a separate, non-terminating variant.

Download as JSON

Download the full game corpus entry for this game as structured JSON.

Download JSON
Cite this page

Wolf in the Ditch (Belarusian Ravine Interception Game) (Belarus). (n.d.). Games of Countries. https://gamesofcountries.com/games/by-belarus/chyrvonaya-shapachka-i-vouk

@misc{gamesofcountries-by-belarus-chyrvonaya-shapachka-i-vouk,
  title = {Wolf in the Ditch (Belarusian Ravine Interception Game) (Belarus)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/by-belarus/chyrvonaya-shapachka-i-vouk}
}