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

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:

Concern	What to make visible
Functional contribution	Who or what produces sound or movement, senses timing, supports weight, generates material, cues another performer, presents the result, or recovers from failure.
Construction and physical connection	Bodies, instruments, devices, effectors, props, connectors, rooms, floors, wearables, and their actual constructive relations.
Timing and rhythm	Continuing carriers, discrete events, anticipated or perceived centres, timing tolerances, cue relations, and recovery after drift.
Sensing, control, and feedback	What state each performer or controller can sense, which action it can change, what feedback returns, and who corrects failure.
Placement, access, and safety	Spatial reach, visibility, audibility, movement paths, audience and performer access, collision, load, fatigue, and exit.
Participation and decision rights	Who performs, leads, follows, conducts, controls, authorizes, refuses, interrupts, or changes the Method.
Material and description use	How scores, choreography, recordings, prompts, generated material, rule cards, and cue sheets enter Work without becoming performers.

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.

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:5 - Checks and Common Repairs

Check	Failure it prevents	Repair
One Work and performer boundary are selected	The project configures an abstract show or one enormous System.	Name the occurrence or Work family and choose the smallest whole that carries it.
Constituents and external enablers stay distinct	Every venue, service, audience, or platform becomes a part.	State actual constructive and interaction relations.
Several views answer different concerns	Function, construction, timing, control, and placement collapse into one tree or process.	Select each view for the failure it exposes and maintain correspondences only where needed.
Descriptions stay separate from configuration	A score, diagram, stage plot, or approval makes relations obtain.	Name realization Work, actual participants, relations, and evidence.
Interface wording is recovered	A line or noun hides the load-bearing relation.	Identify the connector, port, protocol description, signal, representation, or direct interaction meant.
Timing is grounded	Count, timestamp, or onset substitutes for rhythm and coordination.	Name the actual carrier, event, perception, cue, and observation used by the decision.
Whole-level coordination is tested	Component success is generalized to the performance.	Challenge one load-bearing relation in representative Work.
Correction and safe stop are explicit	Readiness assumes a perfect run.	Name sensing, feedback, recovery, refusal, and stop conditions.
Agent and decision holder are not inferred from signal production	Robot, controller, conductor, or platform gets unintended authority.	Attribute Work and decisions to the Agent or System that actually performs them.

MDPE.3:6 - Sources and Epistemic Boundaries

Source or maintained result	Contribution used here	Boundary
FPF `A.1`, `A.22`, `A.6.F`, `A.6.M`, `A.6.RSIR`, `A.2`, `A.2.1`, `A.2.2`, `A.15.1`, and `F.6`	System admission, selected structures, function, module and interface-claim recovery, assignment, capability, Work, and attribution.	They do not supply Music-or-Dance material, performer, carrier, articulation, partner, ensemble, or performance use.
SYSE.5 — Develop an Engineered System’s Functional Organization and Bearer Alternatives	General engineered-System functional organization, bearer, allocation, interface, feasibility, and conflict alternatives.	A possible architecture is distinct from the configuration that exists; MDPE specifies the performance relations.
Timing examples in the Dance profile and the local Balboa cases	Continuing carrier, discrete articulation, several event locations, pair boundary, partner feedback, and layered coordination.	Method-design input, not one historical definition, universal teaching Method, or capability result.
Georgia Tech Shimon project, 2017 account, actuator study, and gesture study	Robotic generation, performance, actuation, gesture, timing, interaction, and performer/developer separation.	The sources do not establish one timeless configuration, robot-held development authority, or cultural retention.
Georgia Tech Barnes prosthesis account, finger-control account, and Drumming Arm study	Equipped performer, shared control, device-to-instrument interaction, representative performance, and changing configurations.	One performer/device lineage does not define every equipped performance.
Yamamura et al., JIZAI ARMS	Collaborative body-system design, prototype configuration, embodied role-play, and open interaction questions.	Prototype reachability does not establish Dance performance or capability.
Serpentine, The Call	Named choirs, recording protocol, datasets, models, installation, and participation arrangements.	The source describes distinct performing arrangements; it supplies no universal Music Method.
Whitehead et al., interpersonal coordination in Dance improvisation	Movement relation, directed influence, participant report, and other observations for human dyads.	One synchrony score does not configure a pair or prescribe a partnering Method.
Abalde et al., joint music making	Prior knowledge, social relations, goals, strategies, cueing, anticipation, correction, and mutual adaptation as ensemble concerns.	The research framework is not one ensemble configuration or Systems Engineering Method.

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.