Move-Announce-Acknowledge Cycle¶
Coordination protocol — instantiates Constraint-Guided Improvisation
Before or as an improviser acts, they announce the move and wait for an explicit acknowledgment — so independent, unscripted moves don't collide and everyone's picture stays current.
Move-Announce-Acknowledge Cycle is the closed loop that keeps parallel improvisation from colliding: an actor about to make a move states it aloud, and it is not treated as coordinated until someone explicitly acknowledges it back. Its defining feature — what separates it from the other coordination mechanisms — is the acknowledgment. A move merely announced into the air is a broadcast; a move announced and confirmed received is coordinated. That return leg does two jobs at once: it catches the imminent collision (two people about to do the same or conflicting thing) before it happens, and it forces each move to be small enough to announce. Silence is not consent here — an un-acknowledged move is treated as not yet landed.
Example¶
In a busy operating room, the surgeon, anaesthetist, scrub nurse, and circulator are all improvising against a patient who is not following the textbook. Rather than acting silently and hoping, each says the move and waits for a read-back. The surgeon calls, "clamping the left renal artery now"; the assistant answers, "clamp, left renal — confirmed." The anaesthetist announces a pressor going in; the nurse reads the drug and dose back before it is given.
The read-back is not manners — it is the coordination. When the anaesthetist announces a pressor moments after someone else has already pushed one, the read-back surfaces the clash and the second dose is held. A team that has never run this exact case still moves in parallel without stepping on each other, because every move is announced small and confirmed heard before it counts.
How it works¶
- Announce the intended move. State it before (or as) you act, in terms specific enough to act on — the move, not a vague heads-up.
- Wait for explicit acknowledgment. A move counts as coordinated only once it is confirmed received; no acknowledgment means re-announce or hold, never assume.
- Read back the content. The acknowledgment repeats the substance, not just "copy," so mishearing is caught inside the loop.
- Size moves to fit the cycle. Because each move must be announced and confirmed, moves are kept small enough to announce — which also keeps them reversible.
Tuning parameters¶
- Announce threshold — which moves must be announced: all of them, or only the consequential and irreversible. Announcing everything maximizes safety but floods the channel; announcing only big moves quiets the channel but lets small collisions through.
- Acknowledgment strictness — full content read-back versus a light "copy." Strict read-back catches mishearing but costs time; a light ack is fast but weak.
- Move granularity — how small a move must be to fit one announce-acknowledge cycle. Smaller moves announce and reverse easily but multiply cycles; larger moves mean fewer cycles but coordinate and undo poorly.
- Channel — voice, radio, chat, or gesture, matched to the noise and latency of the setting.
- No-acknowledgment rule — what to do on silence: hold, re-announce, or proceed. Holding is safest, proceeding is fastest, and the choice encodes how much the setting trusts silence.
When it helps, and when it misleads¶
Its strength is that it is the cheapest guard against the signature failure of parallel improvisation — collisions and blindsiding — and it keeps everyone's picture current as a side effect of doing its main job. The pattern is the everyday form of closed-loop communication, the sender–receiver–confirm loop used in aviation crew coordination and in surgical and resuscitation call-outs.[n1]
It misleads when it is over-applied or hollowed out. Require an announce-acknowledge for every trivial move and the channel jams until people tune the ritual out; let the acknowledgment become reflexive — "copy" said without processing — and the loop turns to theater that confirms nothing. It also costs time exactly when speed is scarcest. The classic misuse is defensive: announcing to build a record that shifts blame ("I called it, not my fault") rather than to actually coordinate. The discipline is to reserve mandatory announce-acknowledge for the moves that can collide or cannot be undone, and to keep acknowledgments substantive — read back the content, not just the receipt.
How it implements the components¶
Move-Announce-Acknowledge Cycle realizes the live-coordination side of the archetype — the machinery that runs while moves are being made in parallel:
coordination_signal— the announcement is the outbound signal that tells others a move is coming.feedback_channel— the acknowledgment is the return channel confirming the signal was received and understood; its absence is itself information.move_granularity_rule— requiring each move be announced and confirmed forces moves to a grain small enough to announce, setting the working move size.
It does not maintain the shared picture the announcements keep updating (that is Shared Situation Model), allocate whose turn it is to act (Facilitated Turn-Taking), or run the alternating call-and-answer exchange where each turn builds on the last (Call-and-Response Pattern).
Related¶
- Instantiates: Constraint-Guided Improvisation — lets independent improvisers act in parallel without colliding.
- Consumes: Shared Situation Model — the cycle presupposes a shared picture and is what keeps it current, move by move.
- Sibling mechanisms: Shared Situation Model · Facilitated Turn-Taking · Call-and-Response Pattern · Decision-Rights Matrix · Constraint Backbone Brief · Variable Scenario Rehearsal · Improvisation Learning Harvest · After-Action Review · Tactical Reset Point · Minimum Safe Stabilization · Rollback or Pause Protocol
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Move-Announce-Acknowledge Cycle operates as a repeatable ordered procedure or handoff sequence that coordinates action because it before or as an improviser acts, they announce the move and wait for an explicit acknowledgment — so independent, unscripted moves don't collide and everyone's picture stays current.
Independent corroboration: The frozen evidence defines Move-Announce-Acknowledge Cycle as 'Before or as an improviser acts, they announce the move and wait for an explicit acknowledgment — so independent, unscripted moves don't collide and everyone's picture stays current', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Aviation closed-loop communication directly supplies announce/readback/acknowledge safety practice; performance cueing and clinical, organizational, and military coordination broaden it. This establishes aviation_aeronautics as the primary origin lineage rather than merely a domain where the mechanism is now applied.
Related originating lineages:
- Medicine & Healthcare — Clinical team training independently institutionalized call-outs, check-backs, and handoff acknowledgment.
- Military & Strategic Studies — Command acknowledgment and common-operating-picture discipline provide another operational lineage.
- Organizational & Management Science — Coordination practice generalizes explicit acknowledgment across interdependent teams.
- Performing Arts & Theatre Studies — Explicitly cueing and acknowledging unscripted moves is rooted in ensemble improvisation and stage coordination.
Review resolution: Authoritative/primary-source research resolves the conflicting primary-origin claims in favor of aviation_aeronautics: Aviation closed-loop communication directly supplies announce/readback/acknowledge safety practice; performance cueing and clinical, organizational, and military coordination broaden it. Retained alternate origins (performing_arts_theatre, medicine_healthcare, organizational_management, military_strategic_studies) are limited to independently formative or materially shaping lineages supported by the reviewer evidence; downstream adoption alone was not promoted to origin. The breadth of present-day use is recorded separately as domain_reach=multi_domain. origin_mode=cross_disciplinary_synthesis, confidence=medium, and encyclopedia_synthesis=true reflect the surviving provenance evidence and the encyclopedia's generalization.
Attribution caveat: The improviser vocabulary points to performance, while the announce-acknowledge protocol also has safety-critical origins.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- FAA report on pilot-controller communication — Documents aviation's closed-loop announce/readback/hearback practice for safety-critical coordination.
Notes¶
[n1] Closed-loop communication is a standard practice in crew resource management and clinical team training: the sender states a message, the receiver reads it back, and the sender confirms the read-back is correct, closing the loop. It is named here as a real, correctly-used practice, not as evidence for any particular outcome. ↩