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:
| Before-Work position | Question |
|---|---|
| Material | Which rhythm, melody, texture, phrase, figure, coordination, code-produced structure, or other content is available, and which version matters? |
| Bearer or memory | How can the performer recover it: embodied memory, instrument configuration, score, choreography, recording, code, demonstration, or cue? |
| Description | Which indications guide action, and do they describe material, a Method, constraints, or several of these? |
| Proposed constraints | Which relations are intended to hold among which participants and under which conditions? |
| Obtaining conditions | Which body, instrument, partner, timing, space, latency, safety, access, or participation conditions actually bear on Work now? |
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:
- Which prepared material was used or interpreted?
- Which material or operative constraints were generated, selected, transformed, or revised during Work?
- Which preserved distinctions survived, changed, or remain unknown?
- 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
| Receiving use | Possible direct trace | Important limit |
|---|---|---|
| rehearsal or performer reflection | short audio/video segment, code state, cue note, performer annotation | recording or self-report can omit partner, body, or audience relations |
| creation revision | changed score, choreography note, diff, stem, take, marked phrase | the revision does not establish later enactment |
| technical diagnosis | sensor trace, latency log, actuation record, synchronized capture | measured features may not represent artistic or partner meaning |
| teaching or transmission | annotated example and conditions under which the distinction was recoverable | one example does not establish transfer or retention |
| later observation | occurrence locator, provenance, observer conditions, source return | observation and comparison belong to MDPE.12 |
A direct artifact is not automatically published, accessible, current, or sufficient evidence. Use publication, memory, and lineage patterns when those later relations matter.