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.