Skip to main content
Formal Specification

Karabakh equestrian polo — Formal Specification

Azerbaijan · equestrian-team · Confidence: high

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Çovqan — AI-optimized specification ## General idea A mounted stick-and-ball goal-scoring team sport, structurally a fixed-clock polo variant whose distinguishing rule is a constrained hooking mechanic: an opponent's mallet may only be legally hooked while they are mid-strike and the hooking rider is on the correct physical side of the ball's line — a right-of-way safety rule, not an open contest for the ball at all times. ## Formal model - **Abstraction taken:** Real mallet-striking accuracy, mounted positioning, and ball-control are abstracted into stochastic per-action success checks, since the entry describes technique qualitatively without numeric models. - **Player/agent count:** 2 teams of 5 mounted riders each (fixed on-field roles: 2 backs, 3 forwards), with substitutes available but substitution mechanics not specified by the entry. - **Turn model:** Synchronous ticks; all riders submit actions simultaneously each tick, resolved at tick end, bounded by a fixed match clock. ## Formal rules R1. Setup: teams assemble on their respective sides of the center line; the referee casts the ball to the center, where forwards from both teams contest it with mallets (entry §1.1-1.2). R2. Ball movement (entry §2.1): the ball may only be advanced by `strike_ball()` or `push_ball()` using the mallet head. R3. Illegal ball contact (entry §2.2): `carry_by_hand()`, `kick_ball()`, `strike_opponent_body()`, `strike_opponent_mount()` are never members of the legal action set; committing any of these is a foul (R6). R4. Legal hook (entry §2.3): `hook_mallet(opponent_id)` is legal only when the target opponent is currently mid-`strike_ball()` action and the hooking rider is positioned on the correct physical side of the ball's line of travel [gap-fill: the entry's "on the same side" is read as a right-of-way/line-of-the-ball safety constraint, consistent with real-world polo hooking rules, since a same-team-only reading would make no sense for a hook targeting an opponent]. A `hook_mallet()` attempted outside these conditions is itself a foul. R5. Goal (entry §3.1-3.2): a goal is scored the instant the ball passes completely between a team's goalposts at any height below the 3 m post height (no crossbar). The scoring team's `goals` increments by 1, and play restarts from the center line (R1's face-off repeats). R6. Fouls (entry §4.1-4.2): dangerous right-of-way crossing in front of a galloping opponent, striking a horse with a mallet, dangerous spurring, or riding off at an unsafe angle. Any foul results in a penalty hit awarded to the non-offending team from 30 m or 60 m, the distance set by foul severity [gap-fill: the entry names both distances as available penalty-hit distances but does not map specific fouls to a specific distance; treated as a severity-based referee decision, an external parameter rather than an invented fixed mapping]. R7. Match structure (entry §5): two fixed 15-minute halves with a 10-minute halftime interval (halftime carries no gameplay effect on state beyond pausing the clock). R8. Win condition (from the entry's Objective section): the team with the higher `goals` total when both halves' time has elapsed wins. The entry gives no tiebreak or overtime procedure for equal totals at full time. ## Edge cases - Tie at the end: not addressed by the entry — a genuine silence on equal goal totals at full time. - A player with no legal move: not applicable — a mounted rider always has movement and `strike_ball()`/`push_ball()` (when in range) available. - Repetition / cycles: not applicable — the match is bounded by a fixed clock (R7) independent of how many goals or fouls occur within it. - Simultaneous claims on one position: not applicable — the ball has a single well-defined position at all times; contested strikes at the opening face-off (R1) resolve via a stochastic contest, not a rules ambiguity. - Elimination mid-round and turn-order repair: not applicable — no rider is ever removed from play (aside from substitutions, whose mechanics the entry does not specify); a foul (R6) results in a penalty hit, not a removal. - Resource exhaustion: not applicable — no consumable resource; horses' stamina is flagged as a welfare concern (content_flags) but not formalized as a game-mechanical resource by the entry. - Termination guarantee: the match is bounded by a fixed two-half clock (R7, 15 + 15 minutes, independent of the halftime pause), regardless of how many goals, fouls, or penalty hits occur within that time. The match therefore terminates within a fixed, bounded duration regardless of the stochastic outcomes of individual plays. ## State representation - Persistent (match) state: `goals[team]`, `half_number` (1 or 2), `time_remaining`. - Per-tick ephemeral state: `ball_position`, `rider_positions`, `possession` (which rider last contacted the ball). - Observable information: fully observable — all positions, scores, and match time are public; no hidden information. ## Action space - `strike_ball()` / `push_ball()`: any rider; precondition: ball within mallet range. - `hook_mallet(opponent_id)`: any rider; precondition: target is mid-`strike_ball()` and hooking rider is on the correct side of the ball's line (R4). - Illegal actions the referee model must recognize but that are never in the legal set: `carry_by_hand`, `kick_ball`, `strike_opponent_body`, `strike_opponent_mount` (R3). ## Playability notes - Single-player-vs-AI: workable as human-controls-one-rider-on-a-team vs AI teammates and opponents, similar to any team stick-and-ball sport adaptation. - Reducing 5-per-team to fewer: the entry's own village variant (`Qarabağ Çövkəni`) explicitly allows flexible team sizes of 6-8, suggesting the core rules tolerate team-size variation without structural change; reducing below 5 is not addressed but is not obviously incompatible with R1-R8. - Physical-skill games: real mounted mallet-striking, positioning, and right-of-way judgment are the entire game and are collapsed into stochastic success checks (R2, R4); no genuine horsemanship or mallet skill is modeled. - What is lost: the actual bond between rider and Karabakh horse, the live Jangi folk music accompaniment, the historical/ceremonial weight of a UNESCO-safeguarded tradition, and the specific danger and skill of a legal hook executed at a full gallop. ## Implementation hints State is modest (ball and rider positions, scores, a clock); the real design difficulty is calibrating strike/hook success probabilities and the right-of-way legality check (R4), neither of which the source quantifies numerically. First milestone: implement the tick loop with flat probabilities to verify goal-scoring (R5) and the fixed two-half match clock (R7-R8), then add the right-of-way-constrained hooking mechanic and foul/penalty-hit system.

Download as JSON

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

Download JSON
Cite this page

Karabakh equestrian polo (Azerbaijan). (n.d.). Games of Countries. https://gamesofcountries.com/games/az-azerbaijan/chovqan

@misc{gamesofcountries-az-azerbaijan-chovqan,
  title = {Karabakh equestrian polo (Azerbaijan)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/az-azerbaijan/chovqan}
}