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.

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:

1. source available — content or a carrier can be accessed;
2. source used — provider or receiving Work actually relies on named content;
3. receiving enactment — representative Work enacts an admitted receiving Method under stated conditions;
4. transfer — enactment occurs under the changed condition required by the use;
5. retention — enactment recurs after the stated delay and conditions;
6. source contribution — a suitable comparison supports the causal claim about named content or provider Work; and
7. population continuation — a later cultural result owned by MDPE.19 and C.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.