MDPE.11 - Interpret or Shape Music-or-Dance Material While Performing

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

Public result: the interpretation realized, or material generated or changed, during performance Work

MDPE.11:0 - Use This When

Use this pattern when prepared material, a score, choreography, generative rule, prompt, task, rehearsal result, or configured performer is being treated as though it were the performed result.

The pattern covers cases in which a musician interprets a score, a social dancer combines learned coordinations with partner response, an improviser generates material inside a form, a live coder changes running code, or a robot uses generated material in performance. The direct Methods differ; the shared difficulty is knowing what existed before Work, what the performer could change during Work, and what interpretation was realized or material generated during that Work. The first useful result names the prepared material and constraints, the performer and domain Method, the interpretation or material generated or changed during Work, and the smallest trace needed by the next decision. It keeps the material, its descriptions, the Work, direct artifacts, and the performance occurrence distinct.

Use the direct interpretation, improvisation, live-coding, partnering, conducting, instrumental, vocal, robotic- control, or co-performance Method first. Do not use this pattern when that Method already returns the same material–Work result and useful traces; when alternatives still need comparison (MDPE.9); when capability or configuration is missing (MDPE.10, MDPE.3); or when the current need is to produce and present the occurrence (MDPE.5) or observe it (MDPE.12).

MDPE.11:1 - The Recurring Difficulty

Prepared and responsive performance coexist across Music and Dance. A classical musician realizes notated material differently on each occasion. A social dancer draws on learned coordinations while responding to music, partner, floor, and surrounding dancers. Jazz, improvised Dance, and live coding can generate material while the performance is already under way.

Project language often collapses several objects:

• a score, choreography, prompt, code listing, cue, or rule describes material, a Method, constraints, or some combination;
• musical or movement material is what a performer uses or generates; its bearer is not necessarily the material;
• world-side contact, timing, safety, instrument, latency, or participation constraints obtain or fail during Work; a rule card only states proposed constraints;
• the performer performs dated Work, and that Work enacts a domain Method;
• the interpretation or generated material is a result within that Work;
• a recording, code state, changed score, sensor trace, or note preserves selected traces;
• the bounded performance occurrence and its presentation to listeners, viewers, partners, or participants remain a separate result.

When these collapse, rehearsal success becomes a performance occurrence, an improvised change is backdated into the score, a recording becomes “the performance”, or the performer’s contribution disappears. The opposite error is recording every micro-action, disrupting the Work and producing a trace no later decision can use.

MDPE.11:2 - Solution

Use a simple before–during–after account for one bounded Work. This is a temporal unfolding of the Work, not a holonic level structure and not three separate Work occurrences. Generation and performance can overlap; live branches can repeat or return.

MDPE.11:2.1 - State the receiving question and performer

Name the decision that needs the result: next rehearsal, creation revision, capability demand, production choice, comparison, teaching return, or local practice-development move. Name the performer or performing whole, the bounded Work, and the direct Method.

Use ordinary names such as dancer, musician, pair, ensemble, live coder, robot, or hybrid performer. The Agent who chooses later practice development may be different. Shimon can perform marimba Work while the human team chooses later engineering and development Work.

MDPE.11:2.2 - Recover what exists before Work

Open only positions that can change the performance or receiving decision:

A candidate from MDPE.9 remains material, a description, or a constraint specification under its actual kind. Its prior disposition neither makes it available nor makes a relation obtain.

MDPE.11:2.3 - Distinguish preservation, variation, and generation

Before Work, state only the distinctions needed by the current use:

• preserve: a rhythmic relation, melodic contour, partner cue, interaction rule, lyrical meaning, recognizability condition, or another relation must survive;
• vary: the performer may change timing nuance, ornamentation, path, dynamics, phrase order, code parameters, articulation, or partner response;
• generate or revise during Work: new movement, melodic continuation, running-code transformation, spatial response, or a new constraint may arise only as the situation develops.

These positions are decision-relative. A detail preserved for one competition, ensemble, or partner can be open to variation in another use.

MDPE.11:2.4 - Perform Work under the direct Method and steer only live branches

Perform using the applicable domain Method. Several Methods may function simultaneously at different scales: a dancer can use balance and timing, partner interaction, and an Urban Kiz performance Method in the same Work. That simultaneity is not a first–then procedure and does not show that one Method contains the others.

When current sound, movement, partner response, audience response, code behavior, equipment state, or safety can change the next action, use current FPF situation-responsive steering. The performer uses the smallest set of available actions supported by current facts, authority, and stop conditions. The performer uses a score, recommendation, signal, or audience response to inform the choice.

The subject-specific performance Method continues to govern the Work. Use the general steering result only to choose the next action when a live branch exists.

MDPE.11:2.5 - Identify what interpretation or material was realized or changed

At a useful boundary, answer:

1. Which prepared material was used or interpreted?
2. Which material or operative constraints were generated, selected, transformed, or revised during Work?
3. Which preserved distinctions survived, changed, or remain unknown?
4. Which observation or direct artifact can support the next decision, and what can it not show?

Plain language is often enough: “The pair retained pulse and partner-readable weight transfer, changed the travel path after congestion, and added one turn response; the video shows the path but not partner pressure.”

MDPE.11:2.6 - Preserve only traces with a use

A direct artifact is not automatically published, accessible, current, or sufficient evidence. Use publication, memory, and lineage patterns when those later relations matter.

MDPE.11:3 - First Useful Result

Keep the result concise:

• Receiving question: [the next rehearsal, creation, production, teaching, observation, or development decision].
• Performer and Work: [dancer, musician, pair, ensemble, robot, hybrid; bounded Work and Method].
• Before Work: [material, bearer or memory, descriptions, proposed constraints, obtaining conditions].
• Preserve / vary / generate: [the distinctions used by this occurrence].
• During Work: [current fact, choice, material or constraint generated or changed, and stop if relevant].
• Performed result: [the interpretation realized or material generated or revised during the Work].
• Direct traces: [artifacts or observations and the claim each can support].
• Unknown or unsupported: [what the traces cannot establish].
• Next use or reopen: [decision served and condition that returns the question].

Use the stated traces to support the next decision within their limits.

MDPE.11:4 - Worked Cases

MDPE.11:4.1 - NDT premiere preparation and performance

The documented NDT production developed choreography, costumes, props, light, sound, stage choices, touring constraints, and film or archive arrangements before the premiere. Those are prepared material, descriptions, configurations, and constraints; they are not the premiere occurrence.

For the performance question, identify the dancers and other performers, direct Dance Methods, prepared movement and production material, relations that obtained, and what interpretation and material the premiere Work realized. MDPE.5 identifies the occurrence and presentation; MDPE.12 handles later observation and judgement.

MDPE.11:4.2 - Live coding

In live coding, running code can be visible and changed while sound or audiovisual material is produced. A useful result names the performer’s live-coding Method, starting code and material, allowed transformations, current technical and audience conditions, code states or musical material actually produced, and trace needed by the next decision.

Field sources describe several practices, not one universal live-coding Method. An event calendar or Algorave label is neither material realized in a performance nor evidence of audience recognition or cultural retention.

MDPE.11:4.3 - Social dance

A dancer enters a song with learned coordinations and a domain Method. Partner response, floor density, phrasing, and balance can change the next contribution. The dancer may preserve pulse and readable connection while changing path, figure, timing nuance, or articulation.

The result names what was preserved, what changed, the partner relation that informed the change, and which trace or report can support the next teaching or practice question. The teacher’s later judgement is not the partner relation during Work.

MDPE.11:4.4 - Shimon generation and performance

People supplied a four-measure seed; Shimon generated the remainder and performed it on marimba. Do not assume that composition continuation happened during marimba performance. If the sources identify separate generation and performance Work, treat the generated continuation as prepared material for the later occurrence. Use in-Work shaping only when timing and evidence support that claim.

MDPE.11:4.5 - Balboa, brushes, and event timing

Continuous floor contact, audible onset, weight arrival, perceived rhythmic location, and partner-readable pressure need not coincide. In a dance trial, the pair can preserve pulse and continuing contact while changing free-leg articulation. The performed result identifies what the dancers did and which relation the partner could use. Video, audio, contact trace, performer report, and partner report bear on different claims.

MDPE.11:4.6 - Direct-Method stop

A chamber ensemble uses a maintained interpretation and rehearsal Method that already identifies the score edition, interpretive choices, performers, Work, recording, limits, and return. No cross-domain integration question remains. Use that Method directly; return to MDPE.11 only if in-Work generation or the material–description–constraint boundary becomes unclear.

MDPE.11:5 - Checks and Common Repairs

MDPE.11:6 - Sources and Epistemic Boundaries

Use a direct field Method when it supplies the same result with less burden. Keep the material–Work distinctions that change the current action or evidence.

MDPE.11:7 - Relations

• MDPE.9 can supply material, a description, or a constraint specification for the performer’s Work.
• MDPE.10 and MDPE.3 can supply capability and configuration. They do not produce the Work or realized result.
• MDPE.5 identifies and presents the performance occurrence; MDPE.12 observes and compares it. Neither is the realized interpretation or generated material.
• MDPE.18 governs usable cultural memory and lineage when direct traces enter later continuation Work.
• Direct Music and Dance Methods govern subject Work. Current FPF governs general steering, Work, Method, description, evidence, and publication distinctions.
• This specialization uses applicable Systems Engineering and Method Engineering results when Systems or Methods are changed.

MDPE.11:End