Formal Specification
Māori Spinning Tops — Formal Specification
New Zealand · top-spinning · Confidence: medium
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: probabilistic-proxyGap-fills: 4
# Pōtaka — AI-optimized specification
## General idea
Two mechanically different games under one name. The whip top is a *control* problem —
the player keeps striking to sustain and steer a moving object through obstacles, so
there is a continuous stream of decisions. The humming top is a *launch* problem
scored partly on sound. Treating them as one game is the main modelling error to avoid.
## Formal model
- **Abstraction taken:** for the whip top, the top's motion becomes a position and a
spin reserve on a grid, and each whip strike adds spin and applies a steering
impulse with error. For the humming top, the launch maps to a spin duration and a
loudness value. No rotational physics.
- **Player/agent count:** 1 or more; players interact only in head-to-head duels.
- **Turn model:** ticked for the whip top (spin decays each tick); single-shot for the
humming top.
## Formal rules
R1. **Whip top.** The top has a position, a heading, and a spin reserve that decays
each tick. At zero the top falls and the run ends.
R2. A `whip(direction, power)` adds spin and applies a steering impulse, with angular
error increasing in power. [gap-fill] No accuracy model is given.
R3. A whip struck upward attempts a leap (*peke*) over an obstacle or water, succeeding
with a probability decreasing in the gap width.
R4. A whip may reverse the direction of rotation — an attested action with no attested
mechanical consequence. [gap-fill] Modelled as permitting a heading reversal at
the cost of spin.
R5. Course completion is scored by elapsed ticks; a fall before the finish scores nothing.
R6. **Humming top.** A `launch(cord_force)` yields a spin duration and a loudness, both
drawn from distributions parameterised by force and skill.
R7. The humming contest is won by the loudest and longest sustained hum. [gap-fill]
The source gives no weighting between loudness and duration; treat it as a
configurable pair rather than collapsing it to one number.
R8. [gap-fill] No foul conditions or round limits exist in the source. Duels are
modelled as best-of-n independent runs.
## Edge cases
- **Tie at the end condition:** equal spin durations, or one top louder and the other
longer, are both genuinely unresolved by R7. Report a tie rather than inventing a
weighting.
- **Player with no legal move:** a whip-top player whose top has fallen has no action
until the next run; a humming-top player acts once per round only.
- **Repetition / cycles:** the whip top can in principle be sustained forever on flat
ground. Spin decay plus the course length bound it; on an open flat surface with a
perfect player, only a tick cap terminates it.
- **Simultaneous claims:** in a duel the tops run on separate lanes and do not contend.
Where a shared course is used, a collision is resolved by stopping both tops, which
ends both runs.
- **Mid-round elimination and turn-order repair:** a fallen top ends that player's run
but not the round; other players continue and no order needs repair.
- **Resource exhaustion:** the spin reserve is the consumable and is replenishable by
whipping, which is what distinguishes the whip top from every other top game — the
player is not merely watching a decaying process.
- **Termination guarantee:** the humming top always terminates, since spin duration is
finite and there is one action. The whip top terminates on course completion or a
fall; on an unbounded flat course it needs the tick cap in R8.
## State representation
Persistent: course geometry, obstacle and water positions, tick cap.
Per-player: top type, skill parameter, best result.
Per-turn ephemeral: top position, heading, spin reserve, ticks elapsed; for humming
tops, the drawn duration and loudness.
Information set: fully observable.
## Action space
- `whip(direction, power)` — precondition: whip-top form, top is spinning.
- `whip_up()` — precondition: an obstacle or water gap is adjacent.
- `reverse()` — precondition: top is spinning.
- `launch(cord_force)` — precondition: humming-top form, once per round.
## Playability notes
- **Single-player-vs-AI:** the whip top is a genuine control problem and the better of
the two for an agent — steering under angular error toward a course, with a spin
budget to manage. The humming top has one action and no real decision.
- **Group games (n>4):** runs are independent, so any n reduces to 1 without loss.
- **Physical-skill model:** angular error rising with whip power, and a leap
probability falling with gap width.
- **What is lost:** the sound, and with it the meaning. *Pōtaka tākiri* were spun at
tangi so the humming carried collective mourning, and before battle to unsettle
opponents. A loudness scalar records that a noise was made and nothing about why it
mattered. An implementer scoring humming tops purely on duration has modelled the
wrong thing.
## Implementation hints
Build the whip top and the humming top as separate systems that happen to share a name;
merging them produces a model that fits neither. For the whip top, the first milestone
is spin decay plus a single whip action on a straight course — verify that an agent
must whip at a sustainable rate rather than continuously, or the spin budget is
meaningless.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Māori Spinning Tops (New Zealand). (n.d.). Games of Countries. https://gamesofcountries.com/games/nz-new-zealand/potaka
@misc{gamesofcountries-nz-new-zealand-potaka,
title = {Māori Spinning Tops (New Zealand)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/nz-new-zealand/potaka}
}