Formal Specification
Rooster fight — Formal Specification
Armenia · wrestling-combat · Confidence: high
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 4
# Aklorakriv — AI-optimized specification
## General idea
A one-legged shoulder-contact balance duel fought inside a marked circle: combatants hop continuously on a single supporting leg with the other foot/hand held behind them and use only shoulder, upper-arm, or torso contact to force a fall or an out-of-ring step. Its structural distinctness versus a plain "bump duel" is the two-tier fault system — an instant loss for touching down or leaving the ring, but a warning-then-disqualification loss for releasing the held stance (arms/ankle), which is a softer, escalating penalty rather than a single loss trigger.
## Formal model
- **Abstraction taken:** Continuous one-legged hopping and shoulder-strike physics are abstracted into a per-tick stochastic imbalance check triggered by contact, identical in spirit to a bump-duel: contact raises the probability of a fall rather than guaranteeing one.
- **Player/agent count:** 2 agents per bout. Team battles run as a sequence of independent 1v1 bouts (or, per the `khoroz-khagh` variant, as one simultaneous multi-agent free-for-all — see Playability notes).
- **Turn model:** Synchronous ticks; both agents submit an action simultaneously each tick, resolved at tick end.
## Formal rules
R1. Setup: both agents enter a circular ring (diameter 3-4 m). Each agent sets `stance = held` (raised foot behind them or held by hand, arms crossed tight per entry §1.2) and `hopping = true` on the standing leg.
R2. Both agents must hop continuously on the supporting foot every tick (entry §2.1); `wait()` in place is not a legal no-hop option — an agent that is not moving is still modeled as continuously hopping in place [gap-fill: the entry requires continuous hopping but the formal action set still needs a "no displacement" option, so `hop_in_place()` satisfies R2 while `move(direction)` both hops and displaces].
R3. Legal offensive action: `bump()`, contact using shoulder/upper-arm/torso only, against an opponent within contact range (entry §2.2).
R4. Illegal actions (entry §2.3): `push_hands`, `headbutt`, `kick`, `trip`, `grab_clothing`. Any of these committed by an agent is an immediate bout loss for that agent, with no warning tier — the entry lists these as strictly prohibited without a graduated-penalty clause, unlike the stance-release fault (R6).
R5. Instant-loss faults (entry §3.1-3.2): an agent loses the bout the instant (a) any body part other than the supporting foot's sole touches the ground inside the ring, or (b) the agent steps on or over the ring's outer perimeter.
R6. Graduated-loss fault (entry §3.3): if an agent's `stance` becomes `released` (uncrossed arms or released ankle) during contact, it records a `warning`. A second such violation by the same agent in the same bout is an immediate disqualification loss; the first is a warning only, with no other in-bout penalty [gap-fill: the entry does not state whether a warned agent's contact actions are restricted before the second violation; none are assumed, since the entry describes the warning purely as a counter toward disqualification].
R7. Contact resolution: when `bump()` connects, both the striking and struck agent independently roll a stochastic imbalance check; a well-placed bump can cost the attacker their own footing too (mirroring the shoulder-jostling physicality described in Cultural notes) [gap-fill: the entry describes the strike/counter-balance dynamic qualitatively only, so the probabilistic proxy from the calibration game is reused here since no numeric model is given].
R8. Bout end: the bout ends the instant one agent triggers R4, R5, or the second R6 violation; the other agent wins the bout. If both trigger a loss condition on the same tick, the bout is a draw and replayed [gap-fill: entry is silent on simultaneous double-loss; least-invented resolution, consistent with the calibration duel].
R9. Match structure (entry §4): bouts are contested best-of-three. The match ends the instant one agent has won 2 bouts.
## Edge cases
- Tie at the end: handled at bout level by R8 (simultaneous double-loss → drawn bout, replayed); never a match-level tie since R9 requires a clean 2-bout majority.
- A player with no legal move: not applicable — `move`/`hop_in_place`/`bump` are always available to a balanced, non-warned agent.
- Repetition / cycles: not applicable in the strict sense — R7's imbalance check is triggered by any contact and the entry gives combatants strong incentive to engage (a non-engaging bout has no path to victory), so indefinite stalling is not a structural loop the rules protect; a pure non-engagement stalemate is a valid but self-defeating strategy, not a repeating state cycle, since it never advances toward a win for either side.
- Simultaneous claims on one position: not applicable — agents may occupy overlapping contact space during a bump by design.
- Elimination mid-round and turn-order repair: not applicable to a 2-agent duel (one loser, immediate end, R8). In the team variant's sequential-bout form, an eliminated team member is simply not selected for the next bout; team play continues per Playability notes.
- Resource exhaustion: not applicable — no consumable resource; `warning` count is the only accumulating state and it is bounded at 2 (R6).
- Termination guarantee: each tick with contact carries a positive imbalance probability (R7) that does not decrease, so the probability the bout remains undecided after t ticks → 0 as t → ∞ (non-decreasing hazard argument). Independently, `warning` count is monotonically non-decreasing and caps at 2 (R6), giving a second, purely deterministic path to termination. The match is a bounded sequence of at most 3 such bouts (R9).
## State representation
- Persistent (match-level) state: `bouts_won[A]`, `bouts_won[B]`, `bout_number`.
- Per-bout state: `stance[agent]` (held/released), `warnings[agent]` (0, 1, or DQ), `position[agent]`, `ground_contact[agent]` (bool), `in_ring[agent]` (bool), `ticks_elapsed`.
- Observable information: fully observable — both agents see all state; no hidden information.
## Action space
- `hop_in_place()`: maintain position while satisfying the continuous-hopping requirement (R2); always legal while `in_ring = true`.
- `move(direction)`: hop toward a target direction within the ring; precondition: `in_ring = true`.
- `bump()`: attempt shoulder/torso contact against an opponent in range; precondition: `stance = held`, bout ACTIVE.
- Illegal actions the referee model must recognize but that are never in the legal set: `push_hands`, `headbutt`, `kick`, `trip`, `grab_clothing` (R4).
## Playability notes
- Single-player-vs-AI: natural, one side of the duel vs an AI opponent managing its own imbalance risk and warning count.
- Team variant (`khoroz-khagh`): the entry describes it as one large simultaneous ring with all team members hopping at once, "last remaining upright hopping player wins" — structurally a multi-agent battle-royale variant of R1-R8 rather than sequential 1v1 bouts, and would need its own elimination/spectator-collision rules the entry does not specify beyond the last-survivor condition.
- Physical-skill games: the entire balance/strike contest is a stochastic contact-probability proxy (R7); no true balance physics or footwork skill is modeled.
- What is lost: real proprioceptive balance skill, the specific comic "rooster strut" framing and crowd's imitation crowing, and the graduated social pressure of a public warning before disqualification.
## Implementation hints
Branching factor per tick is small and constant (bump/move/hop-in-place × 2 agents); design difficulty is entirely in calibrating the imbalance probability so bouts feel skill-driven. First milestone: implement the 2-agent duel with a flat imbalance probability per contested bump plus the two-tier warning/DQ fault (R6), verify R8/R9 termination and best-of-three scoring, then extend to the team battle-royale variant.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Rooster fight (Armenia). (n.d.). Games of Countries. https://gamesofcountries.com/games/am-armenia/aklorakriv
@misc{gamesofcountries-am-armenia-aklorakriv,
title = {Rooster fight (Armenia)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/am-armenia/aklorakriv}
}