MDPE.10 - Develop and Test Music-or-Dance Performing Capability

Pattern type: Music-and-Dance performing-capability pattern

Public result: demonstrated transfer to representative Music or Dance Work, with its limits

MDPE.10:0 - Use This When

Use this pattern when intended Music or Dance Work asks more of a performer than current evidence supports, while lessons, exercises, rehearsal hours, model training, equipment, credentials, or one successful demonstration are being treated as the required capability.

The performer may be a person, pair, ensemble, robot, AI System, equipped person, or another configured whole. The development Method and evidence must fit that holder. Human practice, pair rehearsal, robot-control adaptation, model training, instrument redesign, prosthesis calibration, and human–machine co-adaptation are not the same Method with a different noun.

The first useful result answers a bounded question: can this performer now do the named Music or Dance Work under the conditions that matter, and where does the answer stop? It supports the next creation, configuration, rehearsal, performance, or development decision within those limits.

Use current FPF E.23.CDI for the general capability-development move and A.2.2 for capability identity, envelope, measures, evidence, and currentness. MDPE.10 adds what changes the action in Music and Dance: bodily, rhythmic, perceptual, instrumental, partner, ensemble, expressive, technical, contextual, and performance conditions; direct field Methods; and representative transfer.

Do not use this pattern when a direct teaching, rehearsal, adaptation, control, model-training, device-engineering, or other domain Method already returns the holder-specific transfer result and limits. Do not use it for a missing candidate set (MDPE.9), a capable but badly configured performing whole (MDPE.3), a curriculum or provider design, or population-wide cultural transmission.

MDPE.10:1 - The Recurring Difficulty

Capability-development projects often start from an available intervention instead of the Work that must become possible. A class is purchased, exercises are assigned, a model is fine-tuned, a prosthesis is built, or rehearsal hours are increased before anyone states who must become capable of what.

Four errors recur:

• activity replaces transfer: completing an exercise, course, build, training run, or rehearsal is treated as ability to perform under representative conditions;
• the wrong holder gets the capability: a person’s adaptation is attributed to a device, a component result to a robot, one member’s ability to a pair or ensemble, or a generated output to an entire human–AI arrangement;
• one successful context becomes universal: a result is generalized beyond the repertoire, partner, instrument, software, cue, venue, assistance, or time window that made it possible;
• development becomes unbounded: “master rhythm”, “learn the style”, or “build artistry” replaces a current Work family, limiting contribution, test, and stopping point.

Performing capability is also multiscale. During one occurrence, a musician may use bodily control, anticipation, rhythm, phrasing, instrument interaction, ensemble coordination, and concert practice at once. A social dancer may use posture, weight transfer, timing, figure vocabulary, partner response, floor navigation, and participation in the event at once. These concurrent contributions are not a lesson sequence. Training may proceed through first–then activities, but representative Work tests their joint functioning.

Capability belongs to an independently identified System. In practitioner prose, use the narrower useful name— performer, performing Agent, dancer, musician, pair, ensemble, robot, or equipped performer. Keep performer assignment, capability, development Work, provider contribution, and practice-development decision separate. The performer and the Agent who chooses later development Work may be different.

MDPE.10:2 - Solution

Develop one holder’s capability for one named Music-or-Dance Work family. The subsections below form a useful reasoning traversal, not a claim that capabilities function in this sequence during performance.

MDPE.10:2.1 - Name the performer and receiving Work

Identify:

• the performer or performing whole whose capability is being developed or tested;
• the Music-or-Dance Work family and intended use;
• the practice-development decision waiting for the result;
• the Agent who may make that decision;
• providers and other affected Systems when their contributions matter.

Do not infer capability from being assigned as performer, and do not infer performed Work from capability. For an equipped person, distinguish the person, device, and combined configuration. For a pair or ensemble, use a whole-level capability only when that whole is independently identified and the claim concerns its coordination.

MDPE.10:2.2 - Set the target from representative Work

Start from the candidate or performance family, not from a curriculum. State the material, performer configuration, receiving conditions, required result, measures or qualitative distinctions, protected conditions, representative Work, and currentness window.

Choose the smallest target that changes the present decision. “Know Balboa” is too broad. “This pair can keep a continuous movement carrier while placing a partner-readable weight event through the selected phrase and tempo range” can be tested. “This robot can produce the selected dynamic and timing range for the named repertoire and gesture condition” can be tested.

MDPE.9 can supply candidate demands; MDPE.3 can supply a performing configuration. Neither establishes capability.

MDPE.10:2.3 - Find the limiting contribution and protected trade-offs

Recover the direct domain Methods needed by the Work and identify a contribution whose current value materially limits the target. Examples include:

• perception, attention, anticipation, pulse, rhythm, timing, or recovery;
• bodily or effector control, posture, effort, weight, contact, articulation, breath, or endurance;
• instrument, voice, software, sensor, actuator, model, or interface control;
• reading, memory, repertoire access, improvisation, or material transformation;
• partner, ensemble, group, conductor, audience, or interactive-System coordination;
• phrasing, dynamics, timbre, movement quality, expressive range, or controlled variation;
• safety, latency, reliability, error recovery, or support dependence.

These are examples of contributions, not one capability stack or universal rubric. Decompose only far enough to select an intervention and transfer test without hiding an interaction. Keep a conflict visible when improving speed, range, accuracy, novelty, or visibility may worsen expression, safety, autonomy, partner readability, recovery, or another protected result.

MDPE.10:2.4 - Choose a development Method that fits the holder

Choose teaching and attentional interventions by performer, material, limitation, and outcome. Current Music evidence does not support one universal internal-versus-external focus cue. Current Dance evidence does not support one universally superior teacher-led or learner-led pedagogy. Demonstration, correction, exploration, reflection, peer feedback, choice, and deliberate return of attention to an automatized detail are candidate moves to test, not a mandatory order.

MDPE.10:2.5 - Design practice for later contexts, not only acquisition

When the action must transfer, practice only in one repeated context can make acquisition look better than later use. Characterize the cues available before action, feedback available after action, recent sequence of contexts, and conditions of the receiving Work. The learner may group situations differently from the teacher’s labels.

COIN offers a useful human motor-learning hypothesis: several motor memories can be created or updated while their expression is mixed according to inferred context. Apparent forgetting can therefore be a failure to retrieve or express an available response under the current cues rather than destruction of the earlier memory.

Use that claim as a hypothesis that changes a probe, not as an explanation attached after the fact:

• return to a previously successful context before reteaching;
• alter one cue while preserving the task;
• compare blocked and interleaved practice when flexible switching matters;
• vary cue reliability or the order and frequency of context transitions;
• test unfamiliar but relevant contexts and delayed transfer;
• record recovery, blending, interference, generalization, and protected performance conditions.

Keep rivals live: the target may lie outside the capability envelope; a different contribution may be missing; fatigue, partner, tempo, device, or another condition may explain the result; or the intended coordination may not have been isolated from its surrounding style organization. Stop relying on the contextual-inference hypothesis when another explanation predicts the observations better.

The broader claim that all memory and reasoning work through the same COIN mechanism remains open. Context dependence appears across several memory and decision domains, so the hypothesis is worth testing when it yields a better learning or transfer experiment. It is not a reason to suppress rival explanations. In robot and AI work, domain randomization, curriculum design, context-aware retrieval, and held-out-distribution tests are direct machine-learning Methods; a shared word context does not establish the same mechanism as human motor learning.

MDPE.10:2.6 - Perform development Work and test transfer

Perform the selected development Work. Keep the Method, MethodDescription, performing Agent, capability holder, provider contribution, affected Systems, direct results, and observations distinct.

Completion shows that development Work occurred. It does not establish changed capability or that the Work caused the change. A before/after comparison is meaningful only when holder, configuration, measures, envelope, and qualification windows remain comparable. Make a causal claim only when its own evidence supports it.

Then perform the representative transfer Work. Use the least costly test that exposes the target and protected conditions. Where robustness changes the decision, vary one relevant condition: phrase or repertoire, tempo or rhythmic density, partner or ensemble, venue or floor, instrument or device, software or model, assistance or cue, fatigue or interruption, failure recovery, or delay before reassessment.

A reversible artistic experiment can support a narrower claim than a safety-relevant public performance.

MDPE.10:3 - First Useful Result

Record the result in a compact capability statement:

• Capability holder: [performer or configured performing whole].
• Music-or-Dance Work family: [the receiving Work].
• Current baseline and envelope: [what the holder could do, under which conditions].
• Target and protected conditions: [what must become possible and what must not be traded away].
• Limiting contribution: [the contribution selected for development].
• Development Method and Work: [what was done, by whom, with which provider or tool].
• Practice contexts: [cues, feedback, transition history, and variation when these affect transfer].
• Representative transfer Work: [task, configuration, conditions, and observations].
• Supported capability: [what the holder can now do and the evidence used].
• Unsupported conditions: [where the result must not be generalized].
• Receiving decision: [what can now proceed, change, or stop].
• Reopen condition: [changed holder, material, configuration, context, measure, evidence, or time window].

If transfer cannot be tested, name what is missing and which decision it blocks. “Needs more practice” is not a useful result.

MDPE.10:4 - Worked Cases

MDPE.10:4.1 - Balboa pair: readable weight timing

The Dance profile illustrates a useful distinction: continuous contact and movement can carry time while pressure, direction change, weight arrival, or another event articulates it. The target is not completion of an exercise. It is that a named pair keeps the continuous carrier while placing a partner-readable weight event in a representative social-dance phrase and preserving posture, connection, and readiness for redirection.

Practice can contrast full, partial, and zero transfer, move the articulated event, and interleave a few phrases. The transfer Work uses partnered Dance rather than only the isolated exercise. The source supplies Method-design ideas, not a capability claim about any pair.

MDPE.10:4.2 - Multidance, clean switching, and intentional transfer

Two different difficulties occur in multidance. Some dancers blend styles when they intend a clean switch. Others switch whole dance organizations cleanly but cannot carry one chosen coordination into another style. Those are different capability targets.

Suppose dancer P can use a torso-initiated direction change C in a tango phrase, and partner Q can read it. P can also perform a kizomba phrase, but when asked to insert C, either omits it or shifts into the wider tango movement organization. This does not show that C was forgotten.

An A–B–A probe first uses the tango phrase with C, then the kizomba phrase, then returns to the same tango cues without new teaching. A later trial varies one explicit cue or the order. Observations change the next Work:

• prompt return of C in tango weakens a lost-capability explanation and favors work on cue recognition, interleaving, or deliberate transfer;
• failure in both initial and return tango weakens the context-expression explanation and points back to direct development of C;
• restoration of C in kizomba together with unwanted tango relations shows that C has not yet been isolated from the surrounding organization;
• dependence on partner, tempo, fatigue, or another condition changes the holder or envelope under development.

The practitioner report supplies the recognizable problem and a contextual-inference hypothesis. The probe is a constructed application, not evidence about a named dancer or prevalence of the difficulty.

MDPE.10:4.3 - Shimon: robot capability, human development decision

The Shimon sources report bounded composition-continuation, marimba performance, actuator, dynamic-range, striking-speed, and gesture results across configurations. For a capability claim, the robot is the holder. Learned generation, sensing, control, actuation, rehearsal, and performance remain different contributions.

The human team is the practice-developing Agent that changes software, mechatronics, and trial conditions, interprets evidence, and chooses later Work. The robot’s performance does not assign that decision to it. Every capability result stays limited to the tested configuration, material, measures, and conditions.

MDPE.10:4.4 - Jason Barnes and a robotic prosthesis

Barnes, each prosthesis, and Barnes-with-that-prosthesis have different capabilities. A useful capability account distinguishes Barnes’s bodily and musical capability; device sensing, control, actuation, grip, and response; combined drumming or piano Work; engineering Work by the team; and Barnes’s practice and co-adaptation.

Repeated public performances support later use under their conditions. They do not make device configurations equivalent or establish that faster or autonomous strikes provide expressive control, endurance, piano transfer, or cultural adoption.

MDPE.10:4.5 - JIZAI ARMS and generated movement

A team developing a wearable system with additional robotic limbs can produce prototypes and configurations, obtain embodied observations, and make design decisions while Dance capability remains unestablished. A reachable pose or filmed role-play does not show partner coordination, timing, force control, recovery, teaching, or later reproduction. Name the holder, representative Dance Work, safe development Method, and evidence before making the claim.

Likewise, a model can generate movement that viewers call danceable without being a performer or capability holder. The output can enter MDPE.9 as material. Performability remains open until an identified dancer, robot, or configured whole enacts it in representative Work.

MDPE.10:5 - Checks and Common Repairs

MDPE.10:6 - Sources and Epistemic Boundaries

Capability development connects learning support, practice and transfer. Assess what the performer can do in the intended later Work and which conditions the assessment covers.

Reconsider the capability-development Method when a direct field Method supplies the same transfer result with less burden, a changed performer, partner, instrument or controller configuration requires different practice conditions or a different transfer test, or observations contradict a relied-on transfer hypothesis.

MDPE.10:7 - Relations

• MDPE.9 can supply a candidate and its capability demand. It does not establish capability.
• MDPE.3 supplies the performing configuration and coordination basis. It does not establish that the holder can enact the selected material.
• MDPE.5 may use a current capability result for the same holder, configuration, material, and conditions. Capability does not produce the later performance occurrence.
• MDPE.14 can use current capability limits and protected conditions when they change a practice-conflict candidate, veto, representative trial, or moved burden.
• For human-general varied practice, applicability recognition, transfer, retention or tool dependence, use the applicable direct teaching or capability-development Method. Use a published Human Capability Development result when it answers the current question under its stated conditions.
• C.36, MDPE.17, MDPE.19, and MDPE.20 govern cultural transmission, continuation, and trajectories. One holder’s capability establishes none of them.
• Systems Engineering supplies general performer, device, instrument, interface, and configuration results. Method Engineering supplies general Method construction, support, trial, and revision when a Method is changed. This specialization uses those results when they change the performer-facing capability decision.

MDPE.10:End