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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:10:10 UTC

Practical entries

Bring the performance, teaching, or practice-development decision that is waiting. These selected examples show how one pattern’s result changes what another method can do, where a useful branch can stop, and what changes when the conditions do. They are not a catalogue or a required sequence. If no example fits, use the Table of Contents to open a pattern by its working question. Use a direct specialist method when it already supplies the needed result.

The Preface explains the shared language and its Music and Dance profiles. You can ask an assisting agent: “Explain this and give me your comments in the language of my work, without framework jargon.”

MDPE-CARD-STYLE-DEVELOPMENT — Develop a new style without mistaking one showcase for a maintained practice

  • Situation: A collective has an exciting performance and wants to invest in a recurring practice, but other participants have not yet reproduced the relation that made the showcase work.
  • Question: Which change and next commitment are justified for the practice the collective wants to develop?
  • First useful result or honest blocker: A bounded practice-development question, a selected arrangement for the intended recurrence, and a specified first representative test; or the missing participant, capability, authority, or support that prevents it.
  • Start with: MDPE.8 to distinguish the subjects being changed, MDPE.1 to frame the project, and MDPE.21 when different ways to produce and reproduce the intended practice need comparison.
  • Stop or return: Finish at the supported local change or next-development decision. Return when an observed performance, changed participant, or support condition defeats the selected arrangement.

The constructed social-dance and live-music case begins with a rehearsed pair and a live coder who have made a successful showcase. The organizers want unfamiliar pairs to sustain partner-responsive timing in a monthly social event. MDPE.8 separates that recurring practice from the showcase and from a possible later style line. MDPE.1 bounds the present project to one twenty-minute block. MDPE.21 compares the showcase arrangement with a social-practice arrangement: the latter needs varied partners, readable timing, a host, usable sound and floor conditions, and another opportunity to practise. The intended social use selects the latter for a trial.

MDPE.22 addresses the missing opportunity by arranging that protected event block. Its result supplies the participants, host, floor, and permission for the trial. MDPE.5 brings the music, dance, sound, and event contributions together for a pair’s performance. MDPE.12 compares what happens across eight pairs: three sustain the intended timing; five return to a memorized phrase after a dense accent change, and four on the far side report difficulty locating the pulse.

That observation makes a particular conflict current for MDPE.14: musical changes and the partner cue must work together during the same performance. The team treats a longer verbal explanation as insufficient for the identified sound and timing difficulty. The team compares constraining the musical changes, keeping the showcase arrangement, and maintaining separate showcase and social configurations. It selects the split. MDPE.15 carries that choice into a changed social configuration: the musician moves large accent changes away from the partner-cue interval, and the sound operator re-aims the monitor. In the later round, six pairs sustain the timing and two still need teacher cues. Both the sound and musical configuration changed, and the pairs had already practised, so these observations do not isolate either change’s effect.

MDPE.7 consumes the changed configuration and those limited observations when comparing the larger festival slot, another transfer trial, capability development, and stopping the social branch. In this case the team chooses an unfamiliar-partner trial and keeps the current event block for a month. The showcase branch remains useful for its own audience. MDPE.16 can maintain that branch when its performers, material, equipment, and permissions remain available. Another receiving group or a season-long continuation promise would make different results necessary; the worked decision has not established either. The full case remains below, including its scope and the conditions for those returns.

MDPE-PERFORM — Create alternatives and prepare a performing whole

  • Situation: An attractive arrangement or movement candidate works in a rendering or isolated demonstration, but its live performer and coordination demands remain unsettled.
  • Question: Which candidate can serve the intended performance, and which relation must be repaired before relying on it?
  • First useful result or honest blocker: Candidate dispositions tied to a performer-involving comparison, or the unavailable performer or condition that prevents that comparison.
  • Start with: MDPE.9 with the intended use from MDPE.1. If the candidate is already selected, enter at the limiting capability in MDPE.10 or the uncertain interaction in MDPE.3.
  • Stop or return: Stop when the present creation or performance decision has the result it needs. A changed venue, instrument, performer, or receiving use reopens the contribution that depends on that condition.

MDPE.9’s constructed music example compares three arrangements for singer, clarinet, cello, and live electronics. The intended relation is antiphonal: the participants must hear and answer one another, with room for breath and recovery from electronic failure. Dense spectral doubling, sparse instrumental answers, and generated responses pose different demands. A rendering can expose range and balance; a short rehearsal with the intended musicians can expose breath, cueing, latency, and recovery.

Suppose that rehearsal shows that the dense version masks the answers, the sparse version preserves the desired space, and the generated responses arrive too late for the intended exchange. Those observations can reject the first candidate for this use, retain an acoustic branch, and return the electronic branch for revision. For a further electronic trial, the musical requirement and failed timing relation guide MDPE.3: configure the cue and signal path, identify who can detect a missed response, and provide the recovery the performers need. Test that interaction together. If a performer cannot make the required response even with an adequate cue and setup, MDPE.10 addresses that capability instead.

MDPE.11 concerns how musicians realize the prepared material and steer its permitted live variation. If a trial shows that dropping the electronic response and using an acoustic answer sustained the exchange, preserve that observed fallback and its conditions for the next decision. MDPE.5 asks whether production and presentation let the intended recipients encounter the same musical relation: a successful monitor mix for the performers can still leave the audience unable to hear the answers.

If the next venue changes audibility or latency, use MDPE.6 to decide whether the existing result can be used, revised, or branched for that venue. Return the affected cue, sound, or performance result for repair. A working acoustic branch can remain available while the electronic branch is revised; a stored score alone does not establish that its musicians and setup are available.

MDPE-TRANSFER — Move a practice to new conditions and keep it reproducible

  • Situation: Learners can repeat a taught coordination with the teacher but cannot use it with unfamiliar partners, and a school wants to rely on the practice beyond the present class.
  • Question: What transferred, what still depends on the teaching situation, and which result is needed for the school’s next commitment?
  • First useful result or honest blocker: The relations the receiving version must preserve and a judgement of whether existing evidence supports its use; or the missing capability, source content, partner, or support that prevents it.
  • Start with: MDPE.6 for the changed conditions and MDPE.17 for receiving performance. Use MDPE.23 when the uncertainty concerns recognition rather than the movement that follows.
  • Stop or return: Keep the claim at the tested receiving use. Return a recognition problem to MDPE.23, a performance limitation to MDPE.10, or a missing support relation to MDPE.22. A broader continuation promise requires its own basis.

Suppose the teaching team wants learners to use two already taught partner-coordination variants with unfamiliar partners. MDPE.6 compares the class with that receiving use. Partner timing and contact must remain readable; teacher labels and a fixed exercise order need not remain. The team can choose a receiving version of the teaching arrangement that varies those conditions while retaining the original class for learners who still need its support.

MDPE.17 follows what the receiving dancers actually do, which taught method or variant their performance enacts, and how they used the demonstration or lesson material. When the performance fails, MDPE.23 can separate “did not recognize the current coordination” from “recognized it but could not perform the response”. Its constructed recognition case asks for a spoken A/B response before the movement. The learner identifies ten of twelve held-out trials with unfamiliar partners and music, but seven of twelve immediately after a rapid switch between dance contexts. This supports the tested recognition and a remaining transition-sensitive limit; it does not establish movement fluency. A correct recognition followed by a failed response returns to MDPE.10. If competent recognizers cannot maintain the distinction across the intended contexts, revise the distinction or receiving task before drilling it.

These results change the receiving trial and the next teaching move. MDPE.17 uses representative dance-performance observations to judge the receiving claim. It can report that the source was used and a receiving variant was enacted while leaving the source’s causal contribution undecided. Productive changes to the received variant can remain when they preserve the relations the receiving use needs.

When the school asks whether another teacher can continue the practice, MDPE.18 identifies what the lesson descriptions, recordings, and testimony can actually help that teacher recover, including the embodied relations they omit. MDPE.19 uses this evidence together with available performance and support results to assess the stated continuation promise. Existing evidence may support continuation with the current teacher while replacement remains unknown. Test a replacement only when the result is needed, obtainable, and worth the full teaching, performer, support, and observation burden. A claim that replacement performance was tested must rest on that performance; the proposal to develop another teacher is already a useful, narrower result.