fpf.tools
Library / Music and Dance Practice Engineering Principles Framework
Jump to passage
In this reading
Source · lines 3825–3850

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:40:20 UTC

MDPE.13:4 - Worked Cases

MDPE.13:4.1 - A social-dance festival separates battle, floor, teaching, and media uses

A festival team finds that its battle jury and short-video publication reward large, front-facing distinctions. Partners on the social floor care more about timing, connection, traffic awareness, consent, and recoverability. Teachers choose material that can be taught during a workshop. Treating the battle ranking as “what the scene selected” would collapse four uses.

The team compares three arrangements:

  • keep one battle ranking and publish it as the festival’s representative result;
  • keep the battle result but add an independent social-floor recognition task with rotating experienced partners;
  • keep both results, add non-ranked demonstration places for variants that fit neither task, and label media clips by the use they show.

Suppose the team selects the third arrangement for one festival. The observation plan distinguishes battle scores, partner reports, participation and refusal, safety incidents, later workshop choices, repeat participation, and which variants appear again outside the media format. The festival can learn whether the arrangement changed access or practice. It cannot yet claim that the wider dance culture retained a variant.

MDPE.13:4.2 - An Algorave programme protects live practice from one publication format

The Algorave guidelines describe an event-programming Method. Its direct result is an event programme and production brief covering a dance-event setting, sound, visible process, technological diversity, non-headliner organization, affordable access, conduct, accessibility, and community contact. That result shapes encounter and programme selection but does not establish a performed local event, audience recognition, or later cultural retention.

A local organizer expects short clips to favor immediately legible visual interfaces and brief musical events. The organizer compares curator-only programming, popularity-ranked submissions, rotating themes, and a mixed arrangement that uses curatorial feasibility checks while retaining exploration places for materially different live-coding Methods. For this constructed example, suppose the organizer selects the mixed arrangement for one local event. It names venue limits, performer needs, access and conduct requirements, selection authority, publication treatment, and observations of audience discrimination and later performer adaptation. The direct event-programming Method supplies the programme and production brief. MDPE.13 adds only the unresolved design question: how curator choice, exploration places, publication treatment, audience recognition, and performer feedback should jointly shape which live-coding variants remain available for later practice.

MDPE.13:4.3 - Stop at the direct Method when the arrangement is not being redesigned

A competition already maintains suitable eligibility, judging, conflict-of-interest, scoring, appeal, publication, and rule-revision Methods. The current question is one performance result under those Methods. Use the competition Method and C.11 where a choice remains. Do not invoke MDPE.13 merely to restate the judging process.

Return to MDPE.13 when the combined arrangement is itself in question—for example, when qualification access changes, peer recognition is added, media amplification is separated from judging, or non-ranked alternatives must remain available.