Part II - Performance Possibilities and the Performing Whole

MDPE.9 - Generate and Compare Music-or-Dance Performance Candidates

Status: Stable

Pattern type: Music-and-Dance performance-candidate pattern

Public result: several identified candidates with supported retain, revise, branch, or reject decisions

MDPE.9:0 - Use This When

Use this pattern when a composer, choreographer, performer, teacher, live coder, human–AI team, or other practice-developing Agent has one plausible answer and is about to treat it as the only serious candidate. Also use it when many takes, phrases, model outputs, arrangements, figures, or rule sets have accumulated but nobody has exposed their consequences in the Music or Dance Work that matters.

The costly errors lie at both extremes:

• the first fluent, familiar, visible, or easily notated answer is accepted before breath, body, partner, instrument, timing, control, rehearsal, or recovery demands become visible; or
• generation continues without a receiving decision, so an archive of variants replaces comparison and later Work cannot tell what to retain, revise, branch, or reject.

The first useful result is a small set of materially different candidates, each kept under its actual kind and tried in proportion to the decision, with observations, evidence limits, and one next treatment.

Use the applicable composition, arrangement, orchestration, choreography, improvisation, live-coding, editing, generative, co-creative, constraint-design, or other domain Method to make candidates. MDPE.9 does not replace those Methods. It adds the shared engineering move of challenging the incumbent answer, involving the intended performer, and returning bounded dispositions.

Do not use this pattern when a direct domain Method already returns the same candidates, trials, comparison and next decisions; when only one settled work is needed; or when the gap is performing capability (MDPE.10) or configuration (MDPE.3).

When the question is a broader branching development, use C.40 to connect usable material, an actual professional changing operation, examination and worthwhile continuation. It does not supply an unknown specialist operation merely by naming generation. Use C.18 for the retained exploration, archive or front account; C.19 for deciding which lines in a live pool warrant further work or retention; and C.11 for accountable local choice. A pool policy or archive account does not produce the next musical or movement variant.

MDPE.9:1 - The Recurring Difficulty

Music-and-Dance creation never starts from an empty possibility space. Learned Methods, bodies, instruments, software, partners, venues, audiences, notation, and cultural memory make some variants easy to produce and others hard even to notice.

Those constraints are productive, but they also hide assumptions. A notation system makes written differences easy to compare while bodily control remains invisible. A model can produce many fluent samples while rehearsal cost and performer agency remain hidden. A teacher can vary visible figures while preserving the same partner relation—or preserve the figure while losing the weight change that made it work. A camera can make a phrase look clear while contact, effort, timing, or navigation fails for the dancers.

Ask which materially different candidates expose the current assumption and which observation involving a performer will change the next creation decision.

Each candidate keeps its domain kind. Depending on the case, a candidate may be musical or movement material; a score, choreography, prompt, or another description used in performance Work; or a specification of constraints intended to obtain during Work. Keep material, descriptions, constraint claims, performed relations, Work occurrences, and performance occurrences distinct.

MDPE.9:2 - Solution

Generate and compare enough difference to challenge the current commitment. Stop when the next creation decision can be made. Keep capability, production readiness, cultural recognition, and population-wide selection as separate claims that local comparison has not established.

MDPE.9:2.1 - Name the use and incumbent assumption

State the receiving use, intended performer, and decision. Examples include choosing material for an ensemble rehearsal, selecting movement relations for a social-dance exercise, deciding which human–AI interface deserves another prototype, or preserving branches for later choreography.

Then state the incumbent assumption in a form that another candidate can challenge. For example:

• denser doubling is needed to preserve harmonic identity;
• the visible figure carries the partnered timing;
• higher model fidelity gives a dancer more useful control;
• a symmetric duet rule is easier to perform and read;
• the most popular take is the best concert arrangement.

A genre label or request to “be more creative” is not a testable incumbent assumption.

MDPE.9:2.2 - Produce materially different candidates

Apply suitable domain Methods and keep each candidate identifiable. Record only the derivation, edition, configuration, or distinguishing relation needed for the current comparison.

A candidate is materially different when the difference could change the receiving decision. Change rhythm, attack, instrumentation, form, partner relation, body organization, spatial relation, interface, generative rule, constraint, recovery mechanism, or another relevant feature. Renaming a copy or changing an irrelevant parameter does not add useful diversity.

Prefer a few candidates that pull the decision in different directions over many near-duplicates. Preserve a branch when its trade-off or stepping-stone value may matter later; do not force every difference back into one revised identity.

For a connected rhythmic construction, use Construct a rhythmic part from a seed, phase and action rule. It derives a small seed, changes its phase against a fixed accompaniment, generates hand/sound parts and adapts them when the receiving entry or phrase span changes.

For performers who already know the constituent material, Build and adapt a whole rhythmic performance from learned sections explains how to choose the form’s sections, connect them and change the arrangement when phrase density, duration or participants change.

MDPE.9:2.3 - Choose a proportionate performer-involving trial

For each serious candidate, choose the cheapest Work that can expose the relied-on consequence:

• notation, rendering, or simulation can expose range, balance, geometry, latency, or feasibility;
• a listening pass can expose timbre, masking, form, or perceptual distinction;
• an embodied walkthrough can expose reach, weight, effort, contact, balance, or control;
• a rehearsal fragment can expose breath, cueing, ensemble timing, recovery, and instrument interaction;
• a pair, social-floor, battle, class, installation, or audience probe can expose relations that isolated studio Work cannot.

Use the intended performer or performing Agent where practical. A justified proxy can answer a narrower question, but state what it cannot show.

When a candidate is a constraint specification, identify the participants, relations, and conditions it proposes. Observe the later Work to establish whether those relations held. Producing the rule card does not produce the duet relation.

MDPE.9:2.4 - Separate observation from judgement

Keep the trial, observation, and decision apart. A dancer’s felt control, partner report, audio recording, motion trace, rehearsal interruption, listener discrimination, model score, or audience response can each bear on a claim. None automatically supplies the whole judgement.

Interpret the observations for the named use. A candidate can be novel but unusable, technically feasible but artistically wrong, effective for one body but unsafe for another, or valuable only as a branch. Avoid collapsing control, effort, quality, novelty, popularity, fidelity, and cultural recognition into one score.

MDPE.9:2.5 - Give every candidate a next treatment

Return one scoped disposition:

• retain — use or compare the candidate again under the stated conditions;
• revise — change the named feature and retry under a stated condition;
• branch — preserve the difference as a separate line or for another use;
• reject — stop using it for the stated performer, conditions, and purpose.

Do not write “reject globally” unless the claim truly covers all relevant performers and uses. A disposition does not authorize later Work, select a production programme, establish performing capability, or show that a wider practice recognized or retained the candidate.

MDPE.9:3 - First Useful Result

Use one short comparison table:

Above the table, state:

• Receiving use and decision: [what later Work or commitment will use the result].
• Intended performer: [performing Agent, ensemble, robot, hybrid, or other admitted System].
• Incumbent assumption: [the claim the candidate set must challenge].
• Comparison grounds: [characteristics that can change the decision without being collapsed into one score].
• Reopen condition: [changed performer, use, configuration, evidence, or live alternative].

Use the candidate dispositions within their stated trial and receiving-use limits.

MDPE.9:4 - Worked Cases

MDPE.9:4.1 - Human–AI movement generation

Chédin et al.’s reported co-design with Voguing and Dancehall practitioners connected repertoire curation, prototype improvisation, model/interface revision and comparative observation. The three-model comparison was performed by Dancer-Y alone, in medium/high/low order, with self-selected music and a practice that had changed. Different outputs could serve different purposes, but this observation does not isolate fidelity as a cause or establish a shared preference across dancers.

For a new project, adapt that constructive chain to its own receiving decisions. Identify the generated movement material and interface edition; involve the intended dancers in proportionate improvisation trials; observe what each can recognize, control and adapt; and return separate dispositions for choreographic stimulus and tool design. Compare conditions and exposure order when they could change the inference. A low-fidelity candidate might be retained as a stimulus while a more faithful candidate serves another use; those are possible local decisions to establish, not results inherited from the study. Model scores do not settle those uses.

MDPE.9:4.2 - Three music arrangements

A composer prepares a work for singer, clarinet, cello, and live electronics. The intended relation is antiphonal; breath and a recoverable electronic failure mode matter. Three arrangements differ materially:

• dense spectral doubling preserves pitch content but may mask the antiphonal relation;
• sparse instrumental answers preserve space and breath;
• generated responses allow variation but add latency and recovery demands.

Rendering exposes range and balance. A short rehearsal with the intended musicians exposes breath, cueing, latency, and fallback recovery. The first version can be rejected for the current use, the second retained for an acoustic branch, and the third revised for another trial. Those decisions do not yet select a concert programme.

MDPE.9:4.3 - Balboa, brushes, and articulated weight

Drum brushes offer a useful design analogy: a brush can keep sweeping across a drumhead while a pressure change articulates an accent. The Dance profile explains the source and its limits. For a partnered Balboa phrase, the corresponding design question is how to make a weight transfer readable without interrupting the movement that prepares and follows it. A foot touching the floor, a tap becoming audible, and a partner recognizing weight arrival need not be the same event.

In this constructed comparison, a teacher and pair start from a familiar small-step phrase with continuous floor contact. The brief asks for an audible free-leg ornament while preserving the agreed transfer timing, comfortable connection and the following change of direction. They compare the same phrase, pair, recording and pace, beginning with the unornamented phrase as a reference. They then generate two candidates: A adds a distinct tap while that foot is still unloaded; B keeps the sliding preparation but makes the tap quieter and lets the body’s continuing transfer carry the partner cue. Both candidates retain the same intended weight-arrival point.

The stipulated trial makes the choice consequential. The reference supports the next direction change but lacks the requested audible ornament. In A, the partner begins that change at the tap, before the transfer is ready. In B, the ornament remains audible and the partner continues at the intended transfer. After each phrase, the partner identifies the moment taken as the cue; the teacher compares that report with the pair’s continuation. Listening to the recording lets the teacher compare the ornaments’ audible prominence; video helps inspect movement and interruption. Neither substitutes for the partner’s experience.

Retain B for the next rehearsal under these conditions and revise A’s misleading accent. Keep the unornamented phrase as the available simpler version if readability is lost. A deliberately later transfer could instead become a separate candidate under a brief permitting delayed articulation; it does not meet this brief merely because its delay is expressive. The result is a compared candidate and disposition, not a demonstrated capability with unfamiliar partners or music. MDPE.11:4.5 addresses the different decision of changing articulation while a phrase is already being performed.

A brief requiring a regular supporting pulse and movable accent positions adds another comparison. Generate alternatives from MDPE.11:4.5.2: earlier preparation, a shorter feasible articulation or a different allocation can change their mutual interference. Compare each through the requested accent and the following supporting event, then change the requested accent place. A quieter but still required accent may qualify; an omitted accent or one captured by a convenient beat does not meet that brief. If the preferred construction requires unavailable coordination, MDPE.10:4.6 supplies its practice design before a capability claim.

MDPE.9:4.4 - Ableton comping as a direct-Method stop

Ableton Live’s comping Method retains takes, supports audition, copies chosen portions to a main lane, and preserves source material. When that Method already returns the takes, auditions, composite, source relations, and receiving use needed by the project, stop. Apply MDPE.9 only when a broader performance question remains—for example, when two composites create different breath or ensemble demands, or branches must remain available.

MDPE.9:4.5 - Shimon and the development decision

The reported Shimon case supports a bounded claim: after people supplied a four-measure seed, the robot generated the remainder and performed it on marimba. One generated remainder is not a compared candidate set. The case also does not make the robot holder of the team’s later practice-development decision.

MDPE.9 would become relevant if several identified continuations or gesture variants were tried under stated musical conditions and the Agent responsible for the development decision returned bounded dispositions.

MDPE.9:4.6 - Duet constraint specifications

One duet rule says that dancer P changes travel direction only after dancer Q produces a readable pressure-change event. Another permits either dancer to initiate while the other preserves contact through the response. The cards describe candidate constraints; they do not make pressure, initiation, contact, or response occur.

During partnered-improvisation trials, the dancers use the cards and observers record whether the proposed relations obtained and remained readable. One rule may be revised because the pressure event is ambiguous; the other may branch because mutual initiation improves recovery while weakening intended asymmetry.

MDPE.9:4.7 - Build and adapt a whole rhythmic performance from learned sections

Use this case when performers can already speak or play the constituent rhythmic material but still need to decide which sections belong in a whole piece, how they connect and who performs them. The result is an arrangement that can enter a joint rehearsal. Learning the constituent phrases or establishing concert readiness is a different task.

David P. Nelson’s Solkattu Manual, chapters 8–12, supplies a concrete arranging method for the tani āvartanam, the percussion feature in the Karnatak concert practice described there. Chapter 12 develops solo, duo and four-player pieces from the preceding lessons. Its ingredients include time-affirming passages (sarvalaghu), shaped compositions ending in a repeated phrase (kōrvai), shortening exchanges (koraippu) and an identifiable ending. Keep the learned notation or an adequate demonstration of each chosen section available: an outline names those parts without teaching their contents.

Begin with what the whole must do. In this idiom, the periya mōrā and final kōrvai tell the other musicians that the percussion feature is ending and that they must return to the song. Reserve that ending before filling the available duration. The material leading to it may change. Keep the sarvalaghu in roughly the taught order when recognition as this form matters; omit whole sections when duration or preparation requires it. These are conditions of the chosen use. A different composition can deliberately change the form, but then its ending and recognition requirements must be established for that new use.

Suppose two prepared players want a compact piece using Nelson’s learned material. They select the opening, a kōrvai with its preparation, the exchange and the ending. They omit the separate Palani composition to shorten the whole. Their outline connects functions as well as names:

This outline follows Nelson’s two-player example. To obtain a usable rehearsal outline, attach the chosen notation, identify each player and enter each part’s start, end and repetitions against the continuing cycle. Count setups, closing figures and preparation as well as the principal compositions. Convert the resulting beat total to duration at the intended beat tempo. If the whole exceeds the available time, remove an optional section or a complete permitted group of patterns, then recompute the joins and duration. Merely adding the nominal lengths of the named compositions leaves their connecting work unaccounted for.

Choose the transition from the phrase’s actual density. Here the reference is an eight-beat cycle whose beat tempo continues through the change. A pulse is a subdivision of that beat, not another name for a syllable. Nelson’s chapter 8 kōrvai occupies 96 counted pulse units in both its simpler and filled versions. Changing how many pulses fit inside a beat changes the statement’s duration; filling a phrase can also change the number of syllables inside a pulse.

These totals exclude the preceding setup and any following arudi. Copying the simpler version’s four-to-six transition onto the filled version would demand twelve syllables per beat in its double-speed phrases. The seven-cycle alternative preserves the filled material while lowering its peak demand at the second rate. It also occupies two more cycles than the five-cycle treatment. If that extra duration cannot fit, shorten optional material or retain the simpler version; silently speeding the beat changes another condition.

The next section determines how to use this treatment. Nelson’s solo uses the simpler four-to-six transition to lead directly into three-pulse material. His duo uses the filled four-to-three treatment as a section in its own right and closes it before the exchange. Another supplied option is three kōrvai versions at four pulses per beat, an arudi, and then a new three-pulse section. Choose the continuation with the intended shape of the whole in view: a local rate change does not require every arrangement to include the same following section.

Make the exchange converge. For the chapter 10 koraippu, successive stages give each player two eight-beat cycles, one cycle, half a cycle and a quarter cycle. Choose the patterns for each stage from the learned material, maintaining their order and their stated spans. A shorter duo can omit selected patterns while retaining the progression. Do not shorten a phrase merely because the next turn is shorter: the source gives the corresponding smaller construction.

The subsequent unison transition uses phrase lengths seven down to one, each four times. At four pulses per beat, 4 × (7 + 6 + 5 + 4 + 3 + 2 + 1) = 112 pulses. Its additional one-pulse articulation and fifteen-pulse mōrā produce 112 + 1 + 15 = 128 pulses: four eight-beat cycles. Go directly from the last statement of the mōrā into the ending’s preparation.

Adapt the whole when the people change. With one player, omit the koraippu and its exchange-specific unison transition. Reconnect the preceding section to the ending, choosing its closing figure and preparation from the learned material. Nelson’s solo offers an actual alternative: it includes the three-pulse kōrvai section and proceeds from that section’s arudi to the ending. The periya mōrā and final kōrvai remain; unison ceases to be relevant.

With more players of unequal preparation, allocate demanding solos to those who can perform them and give others manageable material together. Put reliable players at vulnerable beginning and ending positions in the exchange order. This changes the performing arrangement without requiring every participant to acquire the hardest solo. Preserve the ending’s recognizable function when reallocating it: Nelson treats unison as usual, not compulsory. If the intended form or receiving musicians change, reconsider what actually makes their return possible instead of preserving this ending by name.

Return the arrangement to performance. RHY.8 supports local transformations and their timing. RHY.9 supplies allocation, usable cues and recovery while the passage continues. Use MDPE.3 when the assembled piece needs a joint configuration and trial.

In that trial, play through the selected transitions and the final return, not only the separate sections. A missed shared entry can require a better cue or allocation; an unperformable filled phrase can require the simpler material or capability development through MDPE.10. A correctly counted plan supplies neither observation. Retain, revise or branch the arrangement under MDPE.9 according to the actual trial and receiving use. The useful construction here is the way from learned parts to a purposeful whole, including the choices that must change when density, duration or participants change.

MDPE.9:5 - Checks and Common Repairs

MDPE.9:6 - Sources and Epistemic Boundaries

For a constraint-specification candidate, name participants, proposed relations, trial observations and the resulting disposition. Use a direct field Method when it supplies the same result with less burden. Reconsider a candidate when it no longer fits the stated receiving use and trial conditions.

MDPE.9:7 - Relations

• MDPE.1 can supply intended use, preservation, and variation constraints. It is not a mandatory preceding step.
• MDPE.10 uses candidates only when their capability demands matter to the present decision; generation does not establish capability.
• MDPE.3 uses a candidate only when it changes the performer, material, instruments, interfaces, timing, control, or another configuration decision.
• MDPE.11 concerns shaping material during Work. MDPE.5 concerns a performance occurrence and its availability. Neither result is the candidate comparison.
• MDPE.13 can use candidates for a recognition-and-selection decision. MDPE.14 can use them for a practice-conflict decision when they change a supported relation or moved burden. Each pattern returns its own result.
• C.40 connects feasible material variation, examination and worthwhile continuation through an available professional operation. C.17 characterizes differences; C.18 supplies the exploration/archive/front account; C.19 decides live-pool treatment; C.11 governs accountable local choice. These are different results. C.36 governs later cultural relations.
• Systems Engineering supplies general performer, instrument, interface, venue, software, and configuration results. Core’s Method-development patterns supply general Method construction, composition, trial, and revision results when a Method is the changed subject. MDPE.9 supplies the Music-and-Dance candidate, performer, trial, and decision specialization.

MDPE.9:End

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

Status: Stable

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. If the receiving phrase also requires changing free-leg accents, retain that demand: the pulse must remain regular and each chosen accent must arrive at its intended place. “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.

For partnered movement, MDPE.Application:5.4 derives practice from the relation that fails in joint performance: obtaining bodily support and articulation, making a cue usable, allocating attention or entering a different movement organization. Begin with an attainable joint attempt and return local practice to the passage it is meant to enable.

Participation can also require learning to finish an encounter or receive a refusal. MDPE.Application:5.5 derives practice from an unnoticed ending, unavailable stopping movement or unreleased contact. MDPE.Application:5.6 distinguishes bargaining after an answer from difficulty carrying out the inviter’s wanted next action. Use the actual failed contribution to choose practice or support; a courteous reply alone leaves the emotional result unestablished.

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.

In a constructed continuation, Lina and Owen are the identified partnered performing whole: the same two people coordinate initiation and response through their agreed contact and timing relations. This case concerns that pair’s joint result, not either person’s ability with every partner. The next decision is whether to use their eight-pulse weight-timing phrase in the following supported studio rehearsal, with the same footwear, floor, contact convention and two selected recordings at 120 and 132 beats per minute.

In the initial trials at those same settings, the pair completes the phrase when the teacher speaks each weight-arrival cue. Without that extra count, Owen reads Lina’s free-leg brush as the transfer and responds before the standing-leg weight arrival in four of six phrases. Both can repeat the simple full transfer in isolation; the selected limitation is making its timing readable inside the continuing phrase. The target is a jointly readable arrival without the teacher’s extra count, while keeping continuous movement, comfortable contact, balance and the ability to stop or redirect. Loudly accenting every step might make arrival obvious but would sacrifice the chosen movement quality, so it is not an adequate repair.

The pair and teacher carry out two short practice periods. They first alternate full and partial transfers while Owen reports when weight arrival becomes usable, then insert the selected full transfer into the phrase without changing its legato carrier. The teacher gives feedback after a phrase instead of counting through it. They interleave the target phrase and an already familiar walking phrase, returning to the simpler transfer when readability is lost. In the first uncounted attempt the brush still misleads Owen; they reduce that free-leg accent and repeat the actual partnered task. This is the selected development operation and stipulated Work in the example, not a claim that every pair should follow this order.

On the next day, the pair performs two three-minute takes, one with each selected recording, without the teacher’s spoken count. Across the twelve selected phrase entries, Owen’s reported arrival and the observed response agree; continuous movement and comfortable contact remain, and the pair stops and redirects at the agreed musical break. These are stipulated observations for the constructed case. They support using this pair and phrase in the next studio rehearsal under those conditions. They do not establish a numerical long-run success rate, performance through an entire public evening, an unfamiliar partner, other recordings or a wider tempo range.

The teacher therefore stops this particular remedial exercise and returns the phrase to rehearsal. Normal music and partner contact remain legitimate supports; removing the teacher’s extra count does not mean removing every cue. Reopen the affected ability/fit judgement if the phrase fails there or the partner, contact convention or receiving demand changes. Retain the observed result for the original pair and conditions. The before/after contrast makes the development decision intelligible; it does not by itself establish that this exercise, rather than every other intervening factor, caused the change.

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

Two different difficulties occur in multidance. A performer may blend two taught movement organizations while intending to switch between them, or switch cleanly but fail to carry one chosen coordination into the other. Specify the movement instructions and musical material separately before choosing either target.

In this constructed exercise, phrase A is a travel-and-pivot phrase taught in the local tango class; phrase B is a close-contact walking phrase with completed weight arrivals and a pause before redirection, taught in the local kizomba class. These instructions identify the task fragments; the class labels do not define all performance under either name. The pair has already performed each fragment with the same selected practice recording R at its fixed tempo. That established compatibility permits keeping R, partner Q, room and contact conditions fixed while changing the movement task.

Dancer P can use a small torso-initiated direction change C in A, and Q can read it. P can also perform B, but when asked to introduce C after B’s pause, either omits it or imports A’s travel-and-pivot sequence. The target is C within B’s stated weight-arrival and pause conditions. It is not a new classification of the recording or a requirement to make all of B resemble A.

An A–B–A probe uses A with C, then B with the attempted C, then returns to A without new teaching. The same recording, tempo and partner remain. Observations change the next Work:

• prompt return of C in A weakens a lost-capability explanation and favors work on cue recognition, interleaving or deliberate transfer;
• failure in both initial and return A weakens the context-expression explanation and points back to direct development of C;
• C in B accompanied by A’s unwanted travel-and-pivot sequence shows that the selected coordination has not yet been separated from that surrounding movement organization;
• dependence on partner, tempo, fatigue or another condition changes the holder or envelope under development.

A later comparison can retain the movement instructions and change only R to another recording already usable for that task. If the practitioner instead changes both the movement instructions and recording, preserve that as a joint-change case: its result cannot identify which change accounts for the difference. Recheck compatibility when either change alters a condition required by the partnering Method.

The practitioner report supplies the recognizable problem and a contextual-inference hypothesis. These specified probes are constructed applications, not evidence about a named dancer, all methods taught under those labels or the 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:4.6 - Learn to vary accents over a continuing pulse

The execution explained in MDPE.11:4.5.2 supplies the capability target. A drummer needs to vary one hand’s accents while the other sustains a regular brush pulse. A Balboa performer needs free-leg accents within continuing support and scheduled weight arrival, including a change of which leg is free. The common difficulty is mutual interference between simultaneously performed contributions. Consequently, both learning designs practise the chosen accent relative to continuing support and judge both results; their physical instructions and observations remain specific to the activity.

The following is a constructed practice design, not a report that particular learners acquired the capability. The teacher first obtains a comfortable supporting action and an identifiable articulation within each learner’s existing technique. If either is unavailable, that specific instruction precedes the joint exercise. The later performance selects the tempo, accent character, musical material and contact conditions.

For example, begin with the midpoint accent, then request a later subdivision while retaining the supporting period. If a learner keeps the period but still accents at the midpoint, the second choice has not been learned. If the new accent is correct but the next pulse lengthens, the other half of the task has failed. Demonstrate the revised preparation and repeat a short joint passage; isolated success is useful preparation for this return, not its completion. The teacher gives target information in advance with enough time for preparation rather than making an impossible last-instant request.

Choose subsequent difficulty from the intended use: a changed accent sequence, intensity, tempo, phrase, allocation or partner. Begin with sufficiently stable conditions to make an actionable correction, then vary the demand whose freedom is missing. This derives similar teaching moves from the common interference problem rather than assuming that all variation or random practice is beneficial. RHY.12:4.2.1 gives the shared construction and its feedback logic.

If the receiving performance requires no teacher count, move feedback after the phrase and try intervals without that extra cue. The pair keeps the music and partner contact; the drummer keeps the instrument and any accompaniment belonging to the target. Use a new required accent sequence to test choice, and a relevant tempo or reference change to test continued synchronization. Include a later attempt when retained capability matters. Judge pulse regularity, accent placement and character, continuation and protected bodily or partner conditions together.

A useful result may authorize the studied phrase and range, identify one still unavailable phase or support exchange, or return a required technique. It cannot be improved merely by dropping the required accents. Transfer to another activity begins by recovering its supporting action, variable articulation, available means and feedback, then carrying out its representative joint task. Structural similarity justifies trying a corresponding teaching construction; actual skill transfer requires the receiving performance.

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. Core’s Method-development patterns supply 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

MDPE.3 - Configure and Coordinate a Music-or-Dance Performing Whole

Status: Stable

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

Public result: a performance-ready configuration and tested coordination basis

MDPE.3:0 - Use This When

Use this pattern when performers, bodies or effectors, instruments, partners, ensemble members, robots, AI Systems, software, media, space, timing, sensing, feedback, and interaction rules have each been considered, but the intended Music or Dance Work still fails when they meet.

Every component may work alone. The whole can still fail through an unreadable partner cue, mismatched timing, latency, weak recovery, spatial conflict, incompatible signal or connector, missing capability, hidden authority, or a score and stage plan that describe coordination without making it occur.

The first useful result is the smallest performing whole needed by the current Work, the load-bearing relations and supporting conditions that must obtain, and a proportionate test of the first uncertain coordination condition. If the whole cannot be made ready, the result names the missing component, relation, capability, permission, or safe test condition and the Work it prevents.

Use applicable ensemble, partnering, rehearsal, staging, instrument-setup, control, venue, interaction-design, Systems Engineering, or other direct Methods to establish the configuration. MDPE.3 adds the performance-specific whole, simultaneous structures, timing, partner, material, and correction distinctions. Do not use it when a direct Method already returns the same actual configuration, tested coordination, limits, and fallback.

MDPE.3:1 - The Recurring Difficulty

Music-and-Dance projects optimize parts and discover incompatibility late. A dancer knows a figure but cannot lead it through the intended contact. A musician can play a part but cannot hear the cue in the venue. A model produces material faster than the performer-facing control can expose it. A robot reaches the notes but its actuation noise, latency, gesture, or recovery changes the musical relation. A prosthesis increases striking speed while moving control away from the musician. A stage plot lists equipment without saying who senses which state or how a failure is corrected.

Documents often hide the failure:

• a diagram line is called an interface without naming the connector, signal, protocol description, or actual interaction;
• a score or count is treated as coordination rather than a description used by performers;
• a performer label is treated as an obtaining assignment and sufficient capability evidence;
• a component test is treated as evidence that the whole can perform;
• a proposed configuration is written as though its Systems and relations already obtain.

The opposite error is boundary inflation. Every venue, service, power source, archive, audience, and platform is made a constituent of one enormous “performing system”. Select the smallest whole that can carry the Work claim; keep external interacting and enabling Systems visible through their actual relations.

Several structures can operate simultaneously. During partnered Dance, bodily control, weight transfer, partner communication, figure execution, musical timing, floor navigation, and social participation can all matter at different scales. Rehearsal may address them in sequence; that first–then unfolding is not the holonic architecture of the performing whole.

MDPE.3:2 - Solution

Configure one performing whole for one named Music-or-Dance Work family. Use Systems Engineering for the general system boundary, architecture, realization, and assurance. Use direct performance Methods to establish and exercise the domain relations. MDPE.3 joins those results around the particular musical or dance occurrence.

MDPE.3:2.1 - Fix the material, Work, and decision

State the selected material or candidate, the Work it must support, the intended conditions, the person or system using the result, the first configuration assumption, and the consequence if that assumption fails.

Do not configure an abstract “show”, “dance”, or “music production”. Name the social-dance phrase, concert set, improvisation constraint, installation interaction, recording occurrence, rehearsal family, or other use.

MDPE.9 can supply a candidate. MDPE.10 can supply current capability evidence. Neither selects or realizes the performing whole.

MDPE.3:2.2 - Choose the smallest performing boundary

Identify separately:

• the candidate whole that will perform the Work;
• constituent Systems and their actual constructive relations;
• external interacting or enabling Systems;
• material, scores, prompts, choreography descriptions, props, floor area, energy, network access, and other values used by Work without being forced into the System kind;
• the interval or configuration for which the boundary applies.

A pair can be the whole when the current claim concerns pair-level coordination. A person with a configured instrument or prosthesis can be the whole for a named Work family. An ensemble can be the whole when joint timing and result production matter. An AI model is not automatically the performer because it generated input material.

Apply the general holon and Systems Engineering criteria rather than assuming systemhood from a group label. In reader prose, call the performer a dancer, musician, pair, ensemble, robot, or equipped performer. Use technical SystemRole classification and assignment only when a downstream claim needs them.

MDPE.3:2.3 - Select architectural views by the failure they expose

Use only views that can change the current decision:

These views need not be trees or isomorphic. They must refer consistently to the same Systems and relations where the decision joins them. A list, diagram, stage plot, score, configuration file, or architecture description is an episteme about the configuration, not the world-side configuration.

MDPE.3:2.4 - Name load-bearing relations and interfaces

For every relation whose failure can defeat the Work, state the participants, condition, direction or reciprocity, and observation that matters. Examples include partner contact and weight exchange, musician-to-musician cueing, instrument-to-audio signal, model-to-control display, controller-to-actuator command, performer-to-device sensing, venue-to-listener audibility, or emergency-stop access.

Treat interface as a prompt to recover the concrete object or relation. In one case it is a connector or physical boundary; in another a functional port; in another a protocol or API description; in another a direct interaction predicate. The shared word does not make them instances of one useful kind.

Keep proposals and actual relations separate. A score can describe timing, a rule card can describe contact, and a protocol can describe messages. Only actual Work and observation can establish that performers used them and the stated relations obtained.

MDPE.3:2.5 - Ground timing in processes and events

Do not let notation or one measured onset replace the rhythm and coordination that performers use. Identify the actual carrier and event relevant to the decision.

In Balboa, continuing floor contact and movement can carry time while pressure change, direction change, or weight arrival articulates it. The foot-touch time, acoustic event, partner-readable event, intended beat, and perceived p-centre can differ. In Music, a physical attack, acoustic onset, perceived beat centre, gestural cue, and software timestamp can likewise differ.

Choose the observation that bears on the performance relation. A waveform onset can support one claim; it does not define rhythm, partner intelligibility, or musical timing for every use.

MDPE.3:2.6 - Establish and challenge the first uncertain relation

Use direct Methods to realize the configuration: setup, fitting, calibration, rehearsal, cue design, sound check, partner practice, control tuning, safety preparation, access preparation, venue setup, or another applicable Method.

Then test the first load-bearing relation with the weakest evidence that it will hold during the intended Work. A short pair trial may expose cue readability. A rehearsal fragment may expose latency and recovery. A venue test may expose audibility and sightlines. A robot probe may expose actuation noise, control delay, or emergency stop. Test the whole-level relation rather than repeating component qualification.

Include correction and recovery. State who or what senses deviation, what action can restore the relation, and the condition that stops Work safely. A perfect-run description is not performance readiness.

MDPE.3:3 - First Useful Result

Record the configuration in a compact basis:

• Music-or-Dance Work: [selected material, occurrence or Work family, and receiving use].
• Performing whole: [smallest whole that carries the Work claim].
• Constituents: [Systems and obtaining constructive relations].
• External enablers and interactions: [Systems and conditions outside the whole].
• Material and descriptions: [scores, prompts, recordings, rules, or other values used by Work].
• Selected views: [only the functional, physical, timing, control, placement, participation, or material views needed].
• Load-bearing relations: [participants, conditions, timing, control, and correction].
• Current capabilities and assignments: [only those relied on].
• Coordination probe: [representative Work, observation, and result].
• Unsupported dependency: [missing component, relation, capability, authority, evidence, or safe condition].
• Fallback and stop: [correction, recovery, or refusal condition].
• Reopen condition: [changed material, performer, component, relation, venue, configuration, or evidence].

The basis describes the actual or proposed configuration. It is not the performing whole, does not make relations obtain, and does not produce a performance occurrence.

MDPE.3:4 - Worked Cases

MDPE.3:4.1 - Balboa pair, carrier, and readable event

For one partnered phrase, the pair can be the performing whole. The selected views expose bodily support, continuing movement and contact, partner connection, and discrete pressure, direction, or weight events. The question is when the weight event becomes usable through the connection. Foot contact or a count alone does not settle that question.

A short pair trial tests whether the legato carrier persists, the event is readable in the selected phrase and tempo range, and the pair can recover after redirection. The result remains limited to that pair and configuration.

For a phrase that also requires variable free-foot accents, expose the continuing support, articulating foot and scheduled change of support as different contributions. Observe pulse regularity and chosen accent placement as well as partner-readable weight arrival. MDPE.11:4.5.2 supplies the joint execution and its support exchange. Separately working parts and sustained contact leave that coordination to be established.

MDPE.3:4.2 - Shimon, marimba, control, gesture, and people

For a bounded robot-only marimba occurrence, Shimon is the performer. Generation software, controller, actuators, physical robot, marimba interaction, supplied seed, room, and human engineering Work contribute through different relations. The human team selects later development Work; it is not silently a constituent performer of every robot occurrence.

Actuator changes concern speed, dynamics, noise, and strike control. Head and arm gesture conditions concern interaction, attention, synchronization, and interpretation by human musicians. These are different views of different configurations, not one timeless robot architecture.

MDPE.3:4.3 - Jason Barnes as an equipped performer

For selected drumming Work, Barnes with a configured prosthesis can be the performing whole. Barnes, the device, sensing, autonomous-stick controller, audio input, drum kit, and relevant signals remain identifiable. The basis states which are constituents, which interact externally, and which sensing, control, actuation, audio-response, stick-to-drum, stop, and redirection relations obtain.

Neither Barnes’s prior musicianship nor the device specification establishes the whole-level capability. Later finger-control and piano Work use another configuration and reopen only the claims whose holder, connection, control, material, or conditions changed.

MDPE.3:4.4 - Separate performing arrangements in The Call

The project includes a songbook, exercises, choirs, recording protocol, datasets, choral models, spatial-audio installation, and a data-trust experiment. These contribute to different performing arrangements.

A choir-recording occurrence has one performer, recording, material, space, assignment, and protocol arrangement. An interactive installation has another model-running, spatial-audio, visitor-control, signal, response, and venue arrangement. A project description can relate them without making every System a constituent of one performing whole.

MDPE.3:4.5 - JIZAI ARMS before a Dance claim

The co-design Method can return a working wearer–device prototype and observations from embodied role-play. That configuration is useful for engineering and interaction decisions. It does not yet return a Dance performing whole capable of selected Work.

A Dance application must identify wearer, wearable base, robotic arms, partner or ensemble, sensing and control, space, timing, safety, correction, representative Work, and evidence. Until then, report the missing Dance configuration rather than treating extra limbs as capability or style.

MDPE.3:4.6 - Direct-Method stop

A solo musician already has the current instrument, room, material, monitoring, permissions, tested setup, and fallback. The direct instrument and venue Methods return the configuration and evidence needed by the performance decision. No whole-level ambiguity remains; applying MDPE.3 would add only another description.

MDPE.3:4.7 - Antiphonal ensemble: cue, late response and acoustic recovery

Continue the constructed ensemble case in the publication’s MDPE-PERFORM entry. A singer, clarinettist, cellist and electronics performer are preparing a short antiphonal passage. Each can perform the selected part, but the generated electronic response sometimes arrives after the intended answer has begun. The present decision concerns the next studio rehearsal of that passage at 96 beats per minute, not readiness for a complete concert.

For this joint timing claim, the performing whole is the four-person ensemble with its configured instruments and electronic rig, integrated by the agreed call, cue, response and monitoring relations. The room, mains supply and later audience playback are external enabling or receiving conditions. The score and generated sound files are material used by the performers. A different room or score can change the required relations without making all those objects ensemble constituents.

The score gives the singer a four-beat call and the ensemble the following four-beat answer. The protected musical result is a clearly heard exchange with the singer’s breathing space intact. Merely delaying the entire answer until generation finishes destroys that relation. The group compares preparing all electronic answers in advance with retaining live generation and providing a timely acoustic answer when needed. It chooses the second arrangement for this passage because live variation remains useful and the acoustic answer is already performable. The first remains a simpler alternative if live variation ceases to warrant the complexity.

The group realizes these relations through rehearsal and the electronics performer’s available queue, gate and mute controls:

The stipulated joint trial contains four ordinary exchanges and two in which generation is deliberately made late. With the selected positions and monitor mix, all participants hear the call and see the ready sign. The ordinary responses enter on the intended downbeat. In both late cases the acoustic answer begins there, the late electronic sound remains muted, the singer keeps the scored breathing space, and the next call resumes together. This tests the connected relation; successful individual parts alone would not supply these observations.

Retain that cue, cutoff, mute behavior, acoustic answer and placement for the next rehearsal of the same passage. The result supports coordination under the tested tempo, players, score and setup. Audience audibility, a longer set and another venue remain untested dependencies for a concert decision; MDPE.5 addresses the receiving presentation. If a changed placement hides the ready sign, reopen that cue path and its joint test while keeping the usable score and acoustic answer. If the clarinettist cannot perform the answer even with an adequate cue, return that capability question to MDPE.10 instead of repairing the signal repeatedly.

MDPE.3:5 - Checks and Common Repairs

MDPE.3:6 - Sources and Epistemic Boundaries

Retain only views that change the configuration or its evidence. Use a direct field Method when it returns the same coordination result with less burden.

MDPE.3:7 - Relations

• MDPE.9 supplies a candidate only when it changes the configuration. Candidate generation does not establish the whole.
• MDPE.10 can supply capability evidence for one holder or configuration. Capability does not establish coordination or actual parthood.
• MDPE.3 uses applicable system and architecture results from SYSE.5 and other Systems Engineering patterns; the music, movement, partner, ensemble, timing, and performance specialization remains here.
• MDPE.11 and MDPE.5 can use the configuration in later Work. Availability of the whole produces neither an interpretation nor a performance occurrence.
• MDPE.14 can use a current conflict among part–whole relations, overlapping Work, a stated scale order, a slower constraint, or a representation use; it returns a bounded practice-conflict decision rather than performing the selected change.
• A.1 governs System admission; A.22 selected structures; C.30 architecture; C.29 representation use; and the direct Method, Work, capability, assignment, evidence, and measurement patterns govern their own claims.

MDPE.3:End