MDPE.17 - Design and Test Transmission of a Music-or-Dance Method
Type: DPF pattern body
Primary working result: an identified receiving Method variant, observations from representative receiving Work, transfer limits, a separately qualified source-contribution status, and a decision to retain or change the transmission arrangement, or stop the proposed receiving use. If source contribution is not supported, preserve the receiving result and say only that the source was used; do not promote resemblance or succession to transmission.
MDPE.17:0 - Use This When
Use this pattern when a lesson, demonstration, score, choreography, recording, prompt, model, software package, or copied artifact has reached another practitioner and someone is about to say that a Music-or-Dance Method was transmitted.
The costly difficulty is easy to recognize:
- dancers reproduce one shown phrase while the teacher supplies every cue, but cannot use the Method with another partner, tempo, phrase, or music;
- musicians read one score or repeat one example, but the intended rehearsal, interpretation, improvisation, or ensemble Method does not appear in later Work;
- an event guide reaches an organizer, while the local event is run through another practice;
- code, model weights, movement traces, or a control policy are copied to a robot or AI service and the copy is called learned practice;
- the receiver creates a useful changed variant, but the project calls every difference a transmission failure; or
- one successful occurrence is reported as capability, population adoption, or long-term continuation.
The engineering question is:
What source content and receiving conditions should we arrange so that a receiving Agent can perform representative Music-or-Dance Work under a receiving Method, and what observation would show what transferred, what changed, and whether further change is needed?
A compact teaching unfolding is:
- name the receiving use and representative Work;
- identify the source content, carrier, provider Work when present, and receiving Agent;
- choose direct teaching, rehearsal, reconstruction, learning, or control Methods;
- vary the conditions that matter to the receiving claim and observe receiving Work;
- distinguish source use, receiving enactment, transfer, retention, and source contribution; and
- retain the useful received variant; keep the transmission arrangement when it suffices, or select a worthwhile change or stop.
Provider Work, receiving Work, and observation Work can overlap or occur at different times. The list is a teaching unfolding, not a universal cultural process, Work plan, or architecture view.
Use the direct Music, Dance, teaching, rehearsal, reconstruction, robotics, machine-learning, event-programming, or community Method without MDPE.17 when it already returns the receiving Method variant, representative enactment, transfer limits, source-contribution boundary, and a supported continuation decision. Use this pattern when those results remain collapsed or missing after direct Work.
Do not use this pattern merely to decide whether to reuse a result before receiving Work (MDPE.6), to recover a candidate Method from records (A.3.1.MR or MDPE.18), to develop general human capability, or to claim population continuation (MDPE.19).
MDPE.17:0.1 - Working Distinctions
| Name | Meaning here |
|---|---|
| source content | The MethodDescription, material, demonstration, example, recording, score, prompt, code, model, or other input actually used by provider or receiving Work. It is not automatically the Method. |
| provider Agent | A teacher, coach, director, developer, model-training team, organizer, or other Agent that performs provider Work. Direct self-study can have no separate provider Agent. |
| receiving Agent | The person, pair, ensemble, organization, robot, AI service, or hybrid Agent expected to perform representative receiving Work. A file, model checkpoint, webpage, or mailbox is a carrier, not the receiver. |
| receiving enactment | Representative receiving Work actually enacts an admitted receiving Method under stated conditions. A MethodDescription or candidate-Method hypothesis does not establish enactment. |
| transfer | The receiving Agent performs Work that enacts the Method under a relevant changed condition or held-out task. Immediate reproduction in the training condition may be useful without establishing transfer. |
| source contribution | A causal claim that named source content, provider Work, or a provider arrangement contributed to the receiving result. Source use and later resemblance are not enough by themselves. |
| received Method variant | The Method identified through receiving Work, including the preserved, changed, added, or absent relations that matter to the receiving use. It may be useful without being identical to the source Method. |
Use teacher, dancer, musician, partner, ensemble, organizer, robot, or AI Agent when that narrow name carries the decision. Use technical System for a model, carrier, instrument, or platform that does not itself choose or learn. A performing whole can include Agents and technical Systems without making every constituent an Agent.
MDPE.17:1 - Problem
Methods do not travel as files. Descriptions, demonstrations, scores, recordings, exercises, prompts, instruments, software, and models can support another Agent’s Work, but they remain descriptions, material, carriers, or tools. A teacher’s successful demonstration is provider Work. A learner’s receiving Work is another occurrence. A copied visible form is not the same result as an enacted Method.
The receiving Method can also change productively. A dancer with another physicality may preserve effort, timing, focus, or partner dialogue through a different visible form. A musician can preserve rhythmic or ensemble relations through another instrument, notation, control interface, or improvisational vocabulary. A robot or AI Agent may use different sensing and control while meeting the same bounded performance demand. Treating literal imitation as the only success criterion can destroy the first useful receiving variant.
At the same time, one successful performance is weak evidence. It may depend on continuous teacher cues, one memorized example, one partner, one tool version, one room, or one context that triggers recall. The performer may already have had the capability; the named source may have contributed little; delayed retention may fail; another context may elicit an old conflicting pattern.
Useful transmission therefore requires more than delivery. Provider and receiving Agents perform the required Work; the receiving Work enacts the received Method, and observation Work obtains evidence proportionate to the intended claim.
MDPE.17:2 - Forces
| Tension | What must remain visible |
|---|---|
| access ↔ enactment | Source content can be available without the receiving Agent being able to use the Method. |
| fidelity ↔ useful transformation | Literal copying can preserve appearance; a changed form can better preserve load-bearing musical, movement, interaction, or control relations. |
| support ↔ independent use | Teacher, partner, prompt, score, controller, or tool support can belong to the intended configuration; removing it matters only when the receiving use requires less support. |
| blocked success ↔ transfer | Repetition in one cue-rich condition can succeed while another partner, tempo, material, venue, or task fails. |
| capability ↔ source contribution | A receiving Agent can perform successfully without the named source causing the result; source content can be used without producing enough capability. |
| local result ↔ cultural continuation | One receiving Agent can perform Work that enacts a Method while the population never recognizes, copies, or retains it. |
| human learning ↔ other Agents | Human motor-learning evidence can guide hypotheses; robots and AI Agents require their own direct learning and control Methods. |
MDPE.17:3 - Solution
Design transmission around representative receiving Work. Select the source content and receiving conditions, arrange direct provider and receiving Methods, make support and context variation deliberate, observe the receiving Agent performing, preserve useful transformations, and decide whether the transmission arrangement can be retained or needs a worthwhile change.
MDPE.17:3.1 - Begin with the receiving use
State what later decision the result must support. For example:
- admit a movement or musical Method into one performer’s repertoire;
- let a teacher offer a class under stated conditions;
- rely on a pair or ensemble in a performance;
- program a local event under a community Method;
- use a robot, AI Agent, or equipped performer in one performance configuration; or
- choose the next repair to a teaching or reconstruction arrangement.
Then name representative Work. A workshop exercise can be representative for the next lesson without representing social dancing. A short robot test can establish one control envelope without representing a concert. A repeated phrase can show immediate reproduction without showing improvisational use. The receiving claim cannot be stronger than the Work used to test it.
MDPE.17:3.2 - Name source, provider, receiver, and carrier separately
Describe the arrangement in ordinary actor-and-action language:
- What source content is actually used, and how is it used?
- Who performs provider Work, under which direct Method, if a provider exists?
- Which receiving Agent performs which representative Work?
- Which Method should that Work enact?
- Which performing whole—bodies, instruments, partners, software, space, sensing, and control—makes the Work possible?
- Which observer or instrument returns the observations needed by the receiving decision?
The same Agent can occupy several positions, but the Work occurrences and results remain distinct. A performer can teach themself from a recording. A founder can also teach. An organizing team can receive an event-programming Method while musicians receive performance Methods. A model-development team can configure a robot while the robot later performs Music Work.
Do not draw a source-to-receiver arrow and treat it as causal transmission. A graph can display supported relations, but each relation still needs its own evidence.
MDPE.17:3.3 - Choose what should persist and what may change
Name the transmission-relevant relations for this receiving use. Examples include:
- Music: pulse, articulation, phrasing, rebound, ensemble cueing, relation to musical structure, improvisational response, or live transformation;
- Dance: weight transfer, effort, focus, timing, contact, invitation, partner readability, spatial relation, or response to music;
- human–technical performance: sensing, control, actuation, model use, correction, stop authority, or division of initiative; and
- teaching or event practice: exercise, correction, turn-taking, participation, conduct, access, programme, or feedback relations.
Do not preserve a style label instead of these relations. State which differences are acceptable, which are desired innovations, and which would make the receiving Method unsuitable for the stated use.
MDPE.17:3.4 - Design support and context variation for the claim
Choose direct teaching, rehearsal, reconstruction, learning, evaluation, or control Methods. Then design a probe proportionate to the claim.
| Claim | Useful probe family |
|---|---|
| immediate receiving enactment | representative Work under the intended support and configuration; |
| less-supported enactment | remove or reduce only the teacher, model, prompt, or partner cue whose absence matters to the intended use; |
| transfer | change one relevant partner, tempo, music, material, instrument, room, cue, source example, input distribution, or task while preserving the claim boundary; |
| retention | repeat representative Work after a delay under stated conditions; |
| source contribution | use a source-specific contrast, withdrawal, alternative source, incorrect demonstration, or other causal comparison suited to the case and qualify it through C.28; |
| correction and adaptation | introduce or observe a relevant error signal and inspect how the next action or receiving variant changes. |
Variation is not automatically better. Use it when it can reveal cue dependence, transfer, or generalization for the current decision. A constant-practice condition can be adequate for another claim. Preserve task, exposure, fatigue, order, and support differences that could explain the result.
For human motor learning, context-sensitive recall is a useful working hypothesis. If performance disappears, first test whether it returns in the learning context. Then vary one relevant context factor. A recovered action may not have been forgotten; another context may have selected another motor memory. COIN supports this hypothesis for sensorimotor repertoires, not a universal law for every kind of learning. The practical requirement is still representative Work across the contexts in which the capability must be available.
MDPE.17:3.5 - Perform receiving Work and classify the result
Observe what the receiving Agent does, not merely what was delivered. Keep these results separate:
- source available — content or a carrier can be accessed;
- source used — provider or receiving Work actually relies on named content;
- receiving enactment — representative Work enacts an admitted receiving Method under stated conditions;
- transfer — enactment occurs under the changed condition required by the use;
- retention — enactment recurs after the stated delay and conditions;
- source contribution — a suitable comparison supports the causal claim about named content or provider Work; and
- population continuation — a later cultural result owned by
MDPE.19andC.36.
Do not discard a positive receiving-enactment result merely because source contribution remains undecided. Report: “The receiving Agent performed representative Work that enacted variant V under conditions K; source S was used; S’s causal contribution was not tested.” That is more useful than either claiming transmission or calling the whole attempt a failure.
If the observed Work does not enact an admitted Method and only a candidate explanation is available, return the observations to Method recovery rather than inventing a Method from one occurrence.
MDPE.17:3.6 - Preserve the received variant and decide how to continue
Name what the receiving Method variant preserves, changes, adds, omits, or leaves unknown. Keep Method, MethodDescription, material, performing configuration, and capability changes separate. A changed movement phrase is not automatically a changed teaching Method; a changed model is not automatically a changed performer Method.
When the received variant and its supported limits suffice for the intended use, retain the arrangement. If a remaining limitation or worthwhile improvement calls for change, choose the smallest useful repair. Examples include another carrier, clearer demonstration, different exercise, reduced cueing, more representative partner or material variation, a corrected MethodDescription, changed tool or instrument configuration, added feedback, or a source-specific comparison. Select further work only when its attainable contribution warrants its cost and delay. Stop or narrow the proposed receiving use when the required conditions cannot be met.
Return:
receiving Agent, use, and representative Work:
source content and how it was used:
provider Agent and Work, when present:
receiving Method and performing whole:
support and context variation:
observed enactment, transfer, and retention limits:
received Method variant — preserved, changed, added, absent, unknown:
source contribution — supported | not supported | undecided | not needed:
continuation decision — retain arrangement | selected change | narrower use | stop:
condition that reopens the decision:
Keep the report’s claims within what the observed Work and evidence support.
A receiving observation or changed Method variant can also reopen an existing MDPE.14 conflict decision, but
only when it crosses a stated limit or changes the same conflict, candidate, comparison, residual
tension, moved burden, or representative test. If none of those decision-bearing relations changes, keep the
existing conflict result; do not rerun conflict work merely because another receiving occurrence was observed.
MDPE.17:4 - Worked Cases
MDPE.17:4.1 - A partner-Dance transmission trial
This constructed project example illustrates the returned result. Its class is illustrative, and population
effectiveness remains untested. A Tarraxo teacher must decide whether dancers P and Q can use a taught
partner-coordination Method in the next supervised social practice without continuous teacher cues. The receiving
use requires weight transfer, timing, partner-readable invitation and response, musical adaptation, and recovery
after an interrupted connection. It does not require a literal copy of the teacher’s phrase.
The source content is a current Tarraxo practitioner description, two exercises, and the teacher’s demonstration.
The teacher performs provider Work through the direct Tarraxo teaching Method. P and Q are the receiving
Agents. In the first two lessons they perform receiving Work as one pair while the teacher supplies continuous
timing and correction cues. The pair can repeat the shown phrase, but that observation supports only
teacher-assisted enactment with the original partner and music.
The receiving trial removes continuous cueing and uses three ninety-second dances: (1) the original P–Q
pair with an unheard track in the taught tempo range; (2) P with experienced changed partner R; and (3)
Q with another experienced changed partner S, with an unexpected pause and restart during the Q–S
dance. The teacher observes but does not cue.
P and Q preserve weight arrival, timing, and readable invitation and response across the changed music and
partner trials until the interruption in the Q–S dance. After that pause, Q restarts the memorized phrase
instead of first re-establishing partner information; S stops the attempt. Seven days later, the original P–Q
pair again performs Work that enacts the Method without reteaching under the changed-music condition.
The admitted receiving Method variant therefore preserves the timing, weight-transfer, and partner-dialogue
relations, allows a changed visible phrase, and transfers across the tested music and experienced-partner changes.
Retention is supported only for seven days with the original pair. Recovery after an interrupted connection
remains absent for Q with changed partner S; unfamiliar novice partners, a wider tempo range, and an
unsupervised party were not tested. The source content and provider Work were used. No source-specific comparison
was run, so their causal contribution is not tested rather than inferred from improvement.
The next transmission change is one exercise in stopping, re-sensing the partner, and rebuilding the invitation
before restarting. The next trial repeats the failed interruption condition for Q with two changed partners.
Reopen the result if that trial fails, if the intended social setting requires a wider partner or music range, or
if a later receiving observation crosses one of the stated transfer or retention limits. Source access,
phrase copying, one successful dance, and seven-day recurrence each support a narrower claim than the complete
receiving-Method result above.
MDPE.17:4.2 - Music: distinguish receiving performer Work from event-organizer Work
A live-coding performer studies Live Coding: A User’s Manual, examples, and tools. An organizing team separately uses the Algorave guidelines for programme, access, conduct, technological diversity, visible process, and community contact.
At one event, two receiving claims are possible:
- the performer changes code or an algorithmic process during a bounded Music performance under the selected live-coding Method; and
- the organizing team programs and runs the event under the selected event-programming Method.
One successful set does not establish that the organizing team can perform event-programming Work under the Method in changed conditions, and a well-run event does not establish performer capability. Test each through representative Work. For performer transfer, change a relevant musical material, tool, or venue condition. For organizer transfer, change a programme or access condition while preserving the community requirements. Record source use separately; the causal contribution of the manual and guidelines still needs its own evidence.
MDPE.17:4.3 - Robot or AI Agent: copied values are inputs, not transmission results
A team copies code, weights, movement data, or a control policy to another robot or AI system. The copied values configure the technical system. They do not establish that an Agent can perform the intended Music-or-Dance Work under a Method.
When the configured receiver has enough agency to act as the receiving Agent, test representative Work. Adapt source-removal, held-out-task, alternative-demonstration, and incorrect-demonstration probes when the direct machine-learning Method supports them. Bhoopchand and colleagues used such distinctions to separate following, within-episode recall, generalization, and source-specific information use. Their GoalCycle3D tasks and metric are not a universal Music-or-Dance test.
If the technical system merely produces output under another Agent’s control, name it as part of the performing whole.
MDPE.17:4.4 - Stop when source material does not yet yield a reusable Method
The Call provides a songbook, exercises, recordings, datasets, choral AI models, an installation, and governance experiments. These are valuable source materials and project results. The project page does not by itself supply one complete reusable Method for a later choir–model project.
Recover or select the needed candidate Method first through direct inquiry or A.3.1.MR/MDPE.18. Then use MDPE.17 only when a receiving choir, organizer, model-development team, or configured performing whole performs representative Work under an admitted receiving Method.
MDPE.17:5 - Recognition and Assurance
The transmission test result is usable when a cold reader can answer:
- What receiving use and representative Work are being tested?
- Who is the receiving Agent, and what performing whole supports the Work?
- What source content was actually used?
- Did a provider Agent perform separate Work, or was this direct self-use?
- Which direct Methods govern teaching, rehearsal, reconstruction, learning, control, and observation?
- Which musical, movement, interaction, control, or participation relations should persist?
- Which context and support changes make the test representative?
- What was observed: access, source use, receiving enactment, transfer, retention, or source contribution?
- What receiving Method variant now exists or remains only a candidate?
- Does the supported result suffice, or is a change, narrower use or stop warranted? What later observation can reopen that decision?
Assure only the claim the probe can support. A delivered lesson, copied artifact, one repeated example, one concert, or one model checkpoint is not sufficient for a stronger claim. Human motor studies, robot-learning experiments, practitioner sources, and project pages contribute hypotheses and probes within their own populations and tasks; none supplies universal prevalence or effectiveness.
MDPE.17:6 - Common Failures and Repairs
| Failure | Repair |
|---|---|
| “The lesson was delivered, so the Method was transmitted.” | Observe representative receiving Work under an admitted receiving Method. |
| “The learner copied the example, so transfer succeeded.” | Test the relevant changed partner, material, cue, tempo, instrument, task, or context. |
| “The receiver needed support, so transmission failed.” | Decide whether that support belongs to the intended performing whole; remove it only when the receiving use requires less support. |
| “The receiving version differs, so it is wrong.” | Compare load-bearing relations and preserve a useful received variant with its derivation and limits. |
| “The result appeared after teaching, so teaching caused it.” | Report source use and receiving enactment; add a source-specific comparison only when the causal contribution matters. |
| “The model or file was copied, so the practice was learned.” | Treat copied values as inputs or configuration; test the receiving Agent’s representative Work. |
| “One receiver succeeded, so the culture retained the practice.” | Send the bounded receiving evidence to MDPE.19; do not infer population continuation. |
MDPE.17:7 - Consequences
| Benefit | Cost or caution |
|---|---|
| Delivery is replaced by evidence of receiving Work. | Representative tests cost more than checking attendance or file transfer. |
| Useful transformations survive instead of being rejected as imperfect copies. | Variant identity and limits must be maintained. |
| Context-bound performance is distinguished from transfer and retention. | More than one condition or time point may be needed. |
| Source use and source contribution remain distinct and evidence-bounded. | A causal comparison can be expensive or unnecessary for the local decision. |
| Human, robotic, AI, ensemble, and hybrid cases share one result boundary. | Their direct learning, control, safety, and capability-development Methods can differ sharply. |
MDPE.17:8 - Rationale and Source Use
FPF C.36 already distinguishes cultural generation, transmission, recognition, selection, retention, loss, and deliberate intervention. The remaining Music-and-Dance engineering problem is how to arrange carriers, provider Work, receiving Work, embodied or technical performance conditions, context variation, and representative probes so another Agent can perform Work that enacts a received Method variant.
| Source or maintained result | Use here | Boundary |
|---|---|---|
C.36, C.36.P, A.15.1, A.3.1, A.3.2, A.10, C.28 | Separate cultural relations, Work, Method, MethodDescription, evidence use, and causal source contribution. | They do not supply the domain receiving Work or transmission design. |
| Crone et al., synchronous versus non-synchronous imitation | Supports separating continuously model-supported Dance Work from later less-supported Work. | One short choreography with novice participants does not select a universal Dance teaching Method. |
| Loria et al., dyad practice in Music motor learning | Supports keeping acquisition, delayed retention, and transfer as different claims. | Observation, total exposure, distributed practice, and mallet-specific transfer limits remain. |
| Bhoopchand et al., few-shot imitation as cultural transmission | Supplies adaptable support-removal, held-out-task, alternative-demonstration, and incorrect-demonstration probes for artificial Agents. | Its tasks, metric, agents, and demonstrators are not universal Music-or-Dance tests. |
| Ranganathan et al., variability versus specificity in motor-skill retention | Prevents a universal “more varied practice is better” rule. | One bimanual task and 24-hour retention result do not settle other tasks or transfer questions. |
| Heald, Lengyel, and Wolpert, COIN and cross-domain review | Supports return-to-context and context-variation probes for human sensorimotor memory. | Wider learning and cultural-transmission use remains a testable hypothesis. |
| Tarraxo Agency, TOCA Method | Supply source-local teaching and practice descriptions for the Dance case. | They do not establish the constructed receiving result, population effectiveness, lineage completeness, or continuation. |
| Blackwell et al., Live Coding: A User’s Manual and Algorave guidelines | Supply heterogeneous live-coding source content and one event-programming MethodDescription. | They do not establish receiving enactment, one sound style, source contribution, prevalence, or continuation. |
| Serpentine, The Call | Supplies named source materials and project relations for a human–AI Music boundary case. | The page does not supply a complete reusable Method or later receiving result. |
Iterated-reproduction studies of rhythm show that repeated reconstruction can regularize and transform material. Use that as a hypothesis about receiving variants, not as a universal teaching Method or proof of why one receiver changed.
Recheck the result when the receiving use, Agent, Method, performing configuration, source content, provider Work, context, support, probe, observation, contribution question, or later continuation decision changes enough to alter the conclusion.
MDPE.17:9 - Relations
| Relation | Use in this pattern |
|---|---|
MDPE.6 | May supply a receiving-use choice and acceptable variation; it does not establish receiving enactment. |
MDPE.18, A.3.1.MR | Supply source and candidate-Method recovery when the Method is not yet admitted. |
MDPE.10, MDPE.3 | Supply performer capability and the configured performing whole when those results change the test. |
MDPE.11, MDPE.5, MDPE.12 | May supply receiving Work, performance occurrence, observation, and comparison results. |
| Method Engineering or an applicable direct Music-or-Dance Method | May supply a changed Method, MethodDescription, material, or configuration intended for another receiving Agent and guide the Work that makes the change. |
MDPE.19 and MDPE.20 | May use bounded transmission evidence when it changes continuation or trajectory. |
MDPE.14 | May use a receiving observation or changed Method variant only when it changes the same conflict, candidate, comparison, residual tension, moved burden, or representative test. Otherwise its existing conflict decision remains usable. |
A.15.7 and C.11 | May use bounded transmission evidence when it changes the next action during current Work or one already formed bounded choice. |
C.28 | Governs the source-contribution claim when that stronger causal conclusion matters. |
| applicable direct domain Methods | Use them for teaching, rehearsal, reconstruction, learning, control, event-programming, and evaluation Work; capable Agents perform that Work. |
No relation above imposes one teaching sequence or claims that provider, receiving, and observation Work must be separate in time.