Formal Specification
Stick Dance-Fight — Formal Specification
Brazil · wrestling-combat · Confidence: medium
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: abstractedGap-fills: 3
# Maculelê — AI-optimized specification
## General idea
An Afro-Brazilian stick dance in which two performers strike and parry in choreographed sequence against drum rhythm, dramatising a warrior's defence. The strikes are cooperative and pre-agreed, not contested — which is precisely why it cannot be modelled as a game.
## Formal model
- **Abstraction taken:** none, deliberately. What a spec can record is the procedure, the synchronisation requirement, and the roles. There is no decision problem to abstract, because both performers are executing an agreed sequence together rather than opposing each other.
- **Player/agent count:** 2 dancers, plus musicians and singers whose tempo is an input to the performance.
- **Turn model:** continuous and rhythm-driven, not turn-based. Strikes fall on beats.
## Formal rules
R1. Two dancers face each other holding sticks (*grimas*).
R2. Musicians establish a drum rhythm and singers accompany.
R3. Dancers execute a choreographed sequence of strikes and parries.
R4. Every strike must land on the drum tempo; synchronisation with the rhythm is the performance criterion.
R5. Movement is continuous, flowing between phrases without discrete stops.
R6. [gap-fill] The specific sequences, their count, and the dramatic arc are not documented in the sources — the entry marks all three undocumented — so the spec treats the choreography as an ordered list supplied as data.
R7. [gap-fill] There is no win condition. A performance succeeds or fails on synchronisation, judged by observers rather than computed.
R8. [gap-fill] A missed beat or dropped stick interrupts the performance, which restarts at the phrase boundary.
## Edge cases
- **Tie at the end condition:** not applicable, because there is no contest and no score. Both performers succeed or fail together.
- **Player with no legal move:** not applicable — the next move is always the next step of the choreography.
- **Repetition / cycles:** the choreography is cyclic by design; phrases repeat while the drums continue. This is a feature of the form, not a defect to break.
- **Simultaneous claims:** the two dancers strike simultaneously by design, and their strikes are meant to meet. There is no contention to resolve.
- **Mid-round elimination:** not applicable; nobody is eliminated from a performance.
- **Resource exhaustion:** performer stamina bounds the performance in practice, but no rule governs it.
- **Termination guarantee:** the performance ends when the choreography's phrase list is exhausted or the musicians stop. Left to itself the cycle in R5 does not terminate, and that is honest to the form.
## State representation
Persistent: the choreography phrase list, drum tempo.
Per-performer: current phrase index, stick state, synchronisation error against the beat.
Per-turn ephemeral: current beat, whether the strike landed on it.
Information set: fully shared. Both performers know the sequence in advance — that is what makes it choreography.
## Action space
- `strike(phrase_step)` — precondition: it is the corresponding beat.
- `parry(phrase_step)` — precondition: partner is striking on this beat.
- `advance_phrase()`.
## Playability notes
- **Single-player-vs-AI:** unsuitable. There is no opponent and no objective to maximise beyond timing accuracy against a known score.
- **Group games (n>2):** the form scales to more dancers in a roda, but this adds performers, not agents.
- **Physical-skill model:** if anything is to be modelled it is timing error against the beat — a single scalar per strike.
- **What is lost:** everything that matters. Maculelê is a performance with religious and historical resonance, danced in a circle with song; treating it as a state machine over stick strikes preserves the mechanics and discards the content. It is classified `non-simulable` for exactly that reason, and forcing it into a decision problem would misrepresent it.
## Implementation hints
Implement as a rhythm-checker, not a game: feed it a choreography and a beat track and have it validate synchronisation. That is the only computational content. Do not attach an agent or a search — there is no opponent to search against.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Stick Dance-Fight (Brazil). (n.d.). Games of Countries. https://gamesofcountries.com/games/br-brazil/maculele
@misc{gamesofcountries-br-brazil-maculele,
title = {Stick Dance-Fight (Brazil)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/br-brazil/maculele}
}