Formal Specification
Sanctuary on the Mark (Chur na maze) — Formal Specification
Belarus · chase-tag · Confidence: medium
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Чур на мазе — AI-optimized specification
## General idea
A musical-chairs-style pursuit game whose structural core is scarcity: there is traditionally one fewer sanctuary than runners, forcing constant movement between marks, compounded by a hard 5-second occupancy timer and a strict single-occupant-per-sanctuary rule that displaces whoever was there when a second runner arrives. Safety is therefore never passive — a runner must actively keep moving or actively contest a mark, since simply "camping" a sanctuary is disallowed by two independent rules.
## Formal model
- **Abstraction taken:** Real sprint speed, tag contact, and timing awareness are abstracted into stochastic per-attempt checks where relevant, since the entry describes physical technique qualitatively without numeric models; the 5-second occupancy limit and displacement rule are treated as exact, deterministic constraints since the entry states them as fixed durations/rules rather than skill contests.
- **Player/agent count:** 1 Pursuer, K Runners, K in [4, 19]; S sanctuaries, S = K - 1 by stated tradition, or an alternative openly-scattered count [gap-fill: the entry offers both conventions ("traditionally 1 fewer... or sanctuaries are scattered openly") without specifying which applies by default; treated as a session parameter].
- **Turn model:** Synchronous ticks; all agents act simultaneously each tick.
## Formal rules
R1. Setup: S sanctuaries are placed across the field; one player is chosen Pursuer via counting-out rhyme (uniform random, entry §1.2).
R2. Runner actions per tick: any Runner may submit `move(direction)` (open ground), `occupy_sanctuary()` (arrive at and touch a sanctuary while declaring "Чур на мазе!", entry §2.1), or `signal_trade()` (a visible/audible cue inviting another Runner to swap sanctuaries, entry §3.1).
R3. Sanctuary protection (entry §2.1): a Runner with `occupy_sanctuary()` active sets `protected = true` and cannot be tagged while it holds.
R4. Anti-stall timer (entry §2.2): each tick a Runner remains at the same sanctuary, `occupancy_time` increments; when `occupancy_time ≥ 5s`, `protected` automatically becomes `false` for that Runner even while still physically at the mark, forcing them to leave or become vulnerable in place [gap-fill: the entry says the Pursuer "may count aloud to 5 to force the occupant into the open," which is read here as flavor narration of the same deterministic 5-second cap, not a separate contested action].
R5. Single-occupancy displacement (entry §2.3): a sanctuary holds at most one `protected` Runner. If a second Runner touches an already-occupied sanctuary, the second Runner's `occupy_sanctuary()` succeeds and takes over `protected` status; the first occupant's `protected` immediately becomes `false`, forcing them into the open.
R6. Pursuit (entry §3.2): the Pursuer submits `move(direction)` each tick and may submit `tag(runner_id)` against any Runner with `protected = false` who is within tag range.
R7. Tag and role transition (entry §4.1-4.3): a successful `tag()` against an unprotected Runner makes that Runner the new Pursuer immediately (they declare "Я мазавод!"); the former Pursuer then acts as an ordinary Runner and may move toward the nearest sanctuary like any other Runner — the entry grants no explicit grace period, so they are immediately subject to R6 like everyone else.
## Edge cases
- Tie at the end: not applicable — there is no scoring system or terminal state.
- A player with no legal move: not applicable — every Runner always has `move`/`occupy_sanctuary`/`signal_trade` available; the Pursuer always has `move`/`tag` (when a target is in range) available.
- Repetition / cycles: expected and structural — the Pursuer role can rotate repeatedly among the same players via consecutive tags, consistent with the entry's own framing of continuous chase play with no described match-ending condition.
- Simultaneous claims on one position: directly addressed by R5 — a sanctuary is never shared; the displacement rule is exactly the game's mechanism for resolving a two-Runner conflict over one mark.
- Elimination mid-round and turn-order repair: not applicable — no player is ever removed from the game; a tag (R7) relabels the Pursuer without eliminating anyone.
- Resource exhaustion: not applicable — no consumable resource; sanctuaries and the occupancy timer reset per-Runner on each new occupation attempt.
- Termination guarantee: **not guaranteed.** The entry gives this game no win condition, describing only the continuous chase and role-rotation mechanics (R1-R7), consistent with the pattern of comparable "no formal endpoint" games in this batch. `termination_guaranteed: false` reflects this honestly.
## State representation
- Persistent (session) state: `pursuer_id`.
- Per-tick ephemeral state: `positions` (all agents), `protected[runner]` (bool), `occupancy_time[runner]` (reset to 0 whenever a Runner leaves or is displaced from a sanctuary), `sanctuary_occupant[sanctuary_id]`.
- Observable information: fully observable — all positions, protection status, and occupancy timers are public; no hidden information.
## Action space
- `move(direction)`: any agent; always legal.
- `occupy_sanctuary()`: any Runner; precondition: adjacent to/at a sanctuary.
- `signal_trade()`: any Runner at a sanctuary; precondition: `protected = true`.
- `tag(runner_id)`: the Pursuer only; precondition: `runner_id` has `protected = false` and is within tag range.
## Playability notes
- Single-player-vs-AI: natural on either side — human Runner timing sanctuary swaps against an AI Pursuer's positioning, or human Pursuer exploiting the 5-second timer to force AI Runners into the open.
- Reducing K > 4 to 2 agents: degenerate — with S = K - 1 sanctuaries and only 2 Runners, the scarcity dynamic that drives the game's core tension collapses to near-triviality.
- Physical-skill games: real sprint speed and tag contact are the entire physical contest and are collapsed into simple range-based `tag()` resolution (R6); no genuine athleticism is modeled. The occupancy timer and displacement rule (R4-R5), by contrast, are exact deterministic constraints, not stochastic skill checks.
- What is lost: the actual social choreography of runners signaling and coordinating sanctuary swaps, the specific ancient Slavic ritual weight of invoking `Чур` for protection, and the physical drama of a displaced runner having to flee the instant a rival touches "their" tree.
## Implementation hints
State is modest (positions, a protection flag and occupancy timer per Runner, sanctuary occupancy); the real design difficulty is calibrating tag range/success and movement speed, neither of which the source quantifies numerically — the timer and displacement rules, by contrast, are exact and need no calibration. First milestone: implement the occupy/displace/timeout/tag loop (R2-R7) with the deterministic 5-second cap and a simple range-based tag check to validate the scarcity dynamic (S = K-1) drives constant movement, then tune tag range and movement speed for balance.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Sanctuary on the Mark (Chur na maze) (Belarus). (n.d.). Games of Countries. https://gamesofcountries.com/games/by-belarus/chur-na-maze
@misc{gamesofcountries-by-belarus-chur-na-maze,
title = {Sanctuary on the Mark (Chur na maze) (Belarus)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/by-belarus/chur-na-maze}
}