Formal Specification
Armenian tip-cat — Formal Specification
Armenia · stick-team · Confidence: high
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Chlik-dasta — AI-optimized specification
## General idea
A two-phase bat-and-peg game structurally distinct from ordinary tip-cat in its layered elimination system: a batter can be put out on the *initial launch* (caught on the fly, or the peg's return throw strikes the resting bat) before ever reaching the *tip-and-strike* phase, where a separate three-strikes rule applies. Distance struck is measured in discrete bat-lengths rather than any continuous unit, turning the scoring itself into an integer count.
## Formal model
- **Abstraction taken:** Continuous ballistic flight of the peg (*chlik*), fielder catching, throwing accuracy, and batting-swing distance are each abstracted into a single stochastic outcome roll per attempt (caught / not caught; hit-bat / missed; struck-distance value), since none of these are meaningfully discretized without inventing physics the entry does not supply.
- **Player/agent count:** 2 teams of 3-5 players (batting order fixed per team), or a 2-agent duel variant.
- **Turn model:** Sequential — one batter is active at a time, proceeding through Phase 1 then (if not out) Phase 2, before control passes to the next batter in the lineup.
## Formal rules
R1. Setup: the trench (*pnduk*) is established at home base; the batting team's lineup order is fixed; the fielding team disperses (no formal position constraints given).
R2. Phase 1 launch (entry §2): the active batter submits `launch_flip()`, which sends the *chlik* airborne to a stochastically-determined distance/hangtime, and places the bat flat across the trench opening.
R3. Catch resolution: immediately after `launch_flip()`, resolve a stochastic `catch_attempt` for the nearest fielder(s). Success: the batter is out (*ktsats*) and control passes to the next batter (R7); no Phase 2 occurs for this at-bat.
R4. Return-throw resolution: if R3 fails (chlik lands), the fielder holding it submits `throw_at_bat()`, aimed at the bat resting on the trench; resolve a stochastic hit check. Success: the batter is out (control passes to R7). Failure: the batter proceeds to Phase 2 from the chlik's resting spot.
R5. Phase 2 tip-and-strike (entry §3): from the resting spot, the batter may submit up to 3 `tip_and_strike()` attempts in sequence (entry §3.3 notes 1-3 by region; the formal model fixes the cap at 3, the entry's own upper bound, to keep the rule well-defined) [gap-fill: regional variance in the juggle count is collapsed to a single fixed parameter rather than modeled as a per-region variant]. Each attempt independently resolves a stochastic success/miss; a successful attempt sends the chlik to a stochastically-determined struck distance and ends Phase 2 for this at-bat; a miss consumes one of the 3 attempts.
R6. Three-miss out (entry §5): if all 3 `tip_and_strike()` attempts in R5 miss consecutively, the batter is out; control passes to R7 with no distance scored for this at-bat.
R7. Turn advance: when a batter is out (R3, R4, or R6), the next batter in the fixed lineup order becomes active and Phase 1 (R2) begins for them. When every batter in the lineup has been put out, the teams swap batting/fielding roles and a new inning begins with the new batting team's lineup reset to its start.
R8. Scoring (entry §4): when a Phase 2 attempt succeeds (R5), the distance from the trench to the peg's final rest is measured in whole bat-lengths (*dasta*, integer floor of continuous distance divided by bat length) and added to the batting team's running score.
R9. Match length: the entry describes the inning/role-swap structure (R7) but specifies no number of innings or target score that ends a full match [gap-fill: treated honestly as an external parameter — a match is a caller-supplied fixed number of innings or a first-to-score-threshold, neither of which the source specifies, so no number is invented here].
## Edge cases
- Tie at the end: not resolved by the entry, since no match-ending score threshold exists (R9); under an externally-supplied fixed-innings match, a tie in total bat-length score after the agreed innings count is possible and the entry gives no tiebreak — this is a genuine silence, not an oversight.
- A player with no legal move: not applicable — the active batter always has exactly one legal action at each step (`launch_flip` in Phase 1, `tip_and_strike` in Phase 2 while attempts remain), and fielders always have `catch_attempt`/`throw_at_bat` available when triggered.
- Repetition / cycles: not applicable — each at-bat strictly consumes lineup progress (R7) and each Phase 2 sequence is capped at 3 attempts (R5-R6), so no state can recur indefinitely within an inning.
- Simultaneous claims on one position: not applicable — only the single nearest fielder acts on a given landed chlik (entry §2.4: "the nearest fielder picks it up"), so there is no contest over who fields it.
- Elimination mid-round and turn-order repair: an out batter is simply removed from the active slot and the next lineup entry becomes active (R7); the lineup order itself is never altered mid-inning.
- Resource exhaustion: not applicable — no consumable resource; the chlik and bat are reused every at-bat.
- Termination guarantee: each inning is provably bounded — the lineup has a fixed finite size, every batter is put out in a bounded number of steps (Phase 1 resolves in at most 2 stochastic checks; Phase 2 resolves in at most 3 attempts, R5-R6), so an inning terminates in at most (lineup size) × (bounded per-batter steps). The full match's termination depends on the externally-supplied innings/score parameter from R9, which is outside what the source specifies but does not undermine the per-inning guarantee.
## State representation
- Persistent (match) state: `score[team]`, `lineup_position[team]`, `current_batting_team`.
- Per-at-bat ephemeral state: `phase` (1 or 2), `attempts_used` (Phase 2 only, 0-3), `chlik_position`.
- Observable information: fully observable — all players see the chlik's position, the batter's phase, and both teams' scores at all times.
## Action space
- `launch_flip()`: active batter only; precondition: `phase = 1`, batter has not yet been put out this at-bat.
- `catch_attempt()`: nearest fielder(s); triggered automatically after `launch_flip()`.
- `throw_at_bat()`: the fielder holding the landed chlik; precondition: R3 failed.
- `tip_and_strike()`: active batter only; precondition: `phase = 2`, `attempts_used < 3`.
## Playability notes
- Single-player-vs-AI: workable as human-batter-vs-AI-fielders, alternating with the AI batting against human-controlled or algorithmic fielders each inning.
- Reducing team size to a 2-player duel: the entry explicitly supports this ("2 individual players in duels"); Phase 1's catch/throw resolution simply uses the lone opposing player as the sole fielder.
- Physical-skill games: catching, throw accuracy, and batting power/timing are the entire game and are collapsed here into three stochastic checks; no genuine hand-eye coordination is modeled.
- What is lost: the actual bat-flip technique for launching the peg, real fielding positioning and reaction, the social forfeit tradition (losing batters carried on winners' backs), and the specific regional variation in allowed juggle count (fixed to 3 here for a well-defined rule set).
## Implementation hints
State space is small per at-bat (phase + attempt counter + position); the design difficulty is entirely in choosing the catch/throw/strike-distance probability distributions, none of which the source quantifies. First milestone: implement one full inning (lineup cycling through Phase 1/Phase 2 with flat stochastic parameters) and verify the score accumulates correctly in integer bat-lengths, before deciding on an external match-length convention (R9).
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Armenian tip-cat (Armenia). (n.d.). Games of Countries. https://gamesofcountries.com/games/am-armenia/chlik-dasta
@misc{gamesofcountries-am-armenia-chlik-dasta,
title = {Armenian tip-cat (Armenia)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/am-armenia/chlik-dasta}
}