MDPE.7 - Choose the Next Music-or-Dance Development Work

Type: DPF pattern body

Primary working result: a next Music-or-Dance development decision account. It cites one lawful C.11 ChoiceResult or a direct domain decision and identifies the DecisionSubject and the independently supported authority for that bounded choice. For choose now, it identifies the intended development Work and its conditions. For probe again, it identifies the bounded probe Work. For reject the current set, it records why no current option survives. When another question is current, it names that question and the Method or pattern that can answer it rather than inventing Work that was not selected. It also states protected conditions, affected Systems, and the revisit or retry condition.

MDPE.7:0 - Use This When

Use this pattern when Music-or-Dance observations have accumulated but the next bounded development Work is still unclear. A new artifact, performance, class, event, intervention, tool, or growing scene may have succeeded or failed, yet that result alone does not say whether to:

• generate or compare another material or performance candidate;
• develop performer capability;
• reconfigure a performing whole or choose a response to a supported practice conflict;
• make and test one local practice change;
• keep several alternatives open;
• obtain receiving enactment or improve a teaching and receiving-enactment arrangement;
• repair a cultural-memory or lineage account;
• perform bounded reconstruction, teaching, archival, or retirement Work after the applicable continuation result;
• run one discriminating observation or trajectory probe;
• perform or present one bounded Music-or-Dance occurrence under its direct Method;
• make one selected episteme edition available for a named use under E.24.PUB;
• stabilize an identified practice subject in a named configuration, or make that subject available for a named use under the applicable direct Method and relation.

Reject current set, probe again, and another question is current are possible ChoiceResult forms. The last form says that the present issue is not resolved by choosing among this OptionSet; it names the question that now needs an answer. Refusal of the present set and waiting for a stated revisit condition are not additional development-Work options merely because they can be written in the same list.

Start with one current DecisionSubject and only the live options that answer the same development question. Bring in results from other MDPE patterns or direct Methods only when they can change this choice. The pattern is not a final checklist over the whole DPF.

A compact first-use mantra begins by stating:

[DecisionSubject] must now choose among [bounded development options] for [named Music-or-Dance practice subject and use]. The choice can change only if [named evidence, conflict, capability, authority, or consequence] changes.

Then apply an explicit ChoiceRule and obtain one lawful ChoiceResult. This walkthrough is a teaching aid. A live comparison may revisit its options, basis, and probe as observations change. If the Agent carrying out the comparison lacks authority to make the bounded choice, return a recommendation to the named DecisionSubject; if no current DecisionSubject and supporting authority relation can be identified, return an unavailable-decision statement. Keep permission and the other Work-entry conditions separate from the choice.

The practical gain is a bounded next-development decision. For selected Work, the account identifies one intended occurrence, a capable Agent, and stated authority, permission, resources, and entry conditions, or names the missing condition that makes the Work unavailable. A successful performance no longer silently becomes a decision to scale, canonize, or preserve. A failed trial no longer silently becomes abandonment.

Use A.15.7 rather than this pattern when an already-admitted Method is being enacted and current facts merely require one bounded next action inside its live branch. Use a direct Music, Dance, teaching, curation, event, production, strategy, or engineering decision Method when it already returns the complete result. Do not use this pattern when:

• the development subject and question are still hidden—use MDPE.8;
• candidate generation is still the current question—use MDPE.9, C.18, or the direct generator;
• one fixed C.11 OptionSet already has a complete domain choice rule and result—use that result directly;
• a chosen option only needs a WorkPlan or tool/call sequence—use A.15.2 or C.24;
• one selected local change must be performed—use MDPE.15;
• the current task is to establish cultural recognition, transmission, retention, or loss rather than choose project Work—use C.36 and the applicable domain Method.

MDPE.7:0.1 - Precision Restoration

A development decision can concern an episteme, material, Method, capability, System, arrangement, or later Work. Name the governed subject rather than saying develop the dance, improve the music, or grow the culture. When the subject or chooser changes scale, reidentify it and its relations.

MDPE.7:1 - Problem Frame

Music and Dance projects produce heterogeneous evidence. A performer feels more fluent, a partner can read a cue, a technical metric improves, an audience responds, a judge recognizes a style, a platform amplifies a clip, a class reproduces a phrase, or an archive preserves a source. These are not interchangeable results and do not imply the same next Work.

Without a bounded choice, projects either repeat the most recent activity or jump to a grand cultural intervention. A good performance triggers publication and scaling before capability and transfer are understood. A failed rehearsal kills a branch that only needed another performer or context. A visible trend displaces local repertoire. An interesting lineage claim consumes effort even though it cannot change the next creation decision.

The pattern connects current domain results to one accountable choice.

MDPE.7:2 - Problem

Five shortcuts repeatedly waste development effort.

1. Latest-result rule. The most recent success, failure, metric, or opinion selects the next Work.
2. Whole-suite checklist. Every available pattern result is gathered even when most cannot change the choice.
3. Performer-for-chooser substitution. The person or robot that performed is assumed to own the practice-development decision.
4. Choice-for-authority substitution. A technically preferred option is reported as a decision made under authority although the supporting relation is missing.
5. Project-for-culture substitution. A local team chooses Work as though it could directly make a population recognize, select, retain, or spread a variant.

The result is either unbounded planning, premature scaling, analysis without action, or action whose authority and intended consequence cannot be recovered.

MDPE.7:3 - Forces

MDPE.7:4 - Solution

Construct a small Music-or-Dance development OptionSet, compare it under one explicit domain ChoiceRule, obtain a lawful ChoiceResult, and relate that result to independently supported authority, permission, capability, and intended Work. The sections below present an ordinary first-use walkthrough of the MethodDescription. They expose the main relations and decision branches. A ChoiceResult depends on the current OptionSet and ChoiceRule from which it was obtained; other checks can overlap or recur. When the branching and return structure itself must be selected, persisted, or compared, represent it under A.22.CGUS.

MDPE.7:4.1 - Name the chooser, subject, and decision extent

Identify:

• the DecisionSubject and DecisionSubjectGranularity;
• the Agent expected to perform later development Work, when different from the DecisionSubject, and any assignment that changes the decision or that Work’s attribution;
• the Music-or-Dance practice subject and current configuration;
• the current intended consequence and affected Systems;
• the decision horizon and resource limit; and
• the authority, permission, consent, safety, and refusal relations that obtain or remain missing.

Use local system-role kinds and assignments when attribution matters. Do not infer that a dancer decides for a pair, a bandleader for an ensemble, a teacher for a scene, a founder for a style, a robot for its development team, a platform for its users, or a statistical majority for a community.

MDPE.7:4.2 - Recover only results that can change this choice

Possible inputs include:

No row is mandatory. A direct Method result can supply the needed input. If a result is unavailable and cannot change the choice, omit it rather than open a research project.

MDPE.7:4.3 - Construct a finite domain OptionSet

Build only options that the current DecisionSubject can actually choose or probe now. Useful option families include:

• continue or vary creation Work;
• run one performer-involving trial or observation;
• develop a named capability for representative Work;
• reconfigure a performing whole, Method relation, interface, or event arrangement;
• make one selected local change;
• retain, repair, suspend, or remove a development alternative;
• teach or obtain receiving enactment;
• improve a recognition or selection arrangement;
• repair a lineage or continuation account;
• perform bounded reconstruction, teaching, archival, or retirement Work after the applicable later result;
• run one trajectory-discriminating probe;
• perform or present one bounded Music-or-Dance occurrence under its direct Method;
• make one selected episteme edition available for a named use under E.24.PUB;
• stabilize an identified practice subject in a named configuration, or make that subject available for a named use under the applicable direct Method and relation.

These are families, not a compulsory menu. Define each concrete option by its intended Work, performing Agent, supporting non-agent Systems when needed, direct Method, intended result, conditions, resource demand, affected Systems, and stop or rollback condition. A concrete inquiry or problem-framing option names its bounded Work and intended result; the question to be answered is not itself Work. Options that belong to different choosers or decisions go into different OptionSet instances. Rejecting the current set is a ChoiceResult; another question is current identifies a different question and its applicable Method; a revisit condition says when to open the choice again. None is silently added as another Work option.

MDPE.7:4.4 - State the Music-or-Dance comparison basis

Use the characteristics and consequences that can reverse the present choice. Depending on the case, these can include:

• musical or movement value for the intended use;
• performer, partner, ensemble, audience, or participant effects;
• rhythmic, bodily, instrumental, spatial, interactive, or expressive constraints;
• safety, consent, accessibility, injury, fatigue, and refusal;
• capability, transfer, setup, venue, tool, latency, production, and resource demands;
• source continuity, attribution, rights, repertoire loss, and alternative-space value;
• recognition, participation, transmission, continuation, and cultural uncertainty; and
• information value of the next feasible trial or observation.

Use A.19.CPM when a formal comparison relation is needed. Keep incomparability, ties, must-constraints, and missing evidence visible. Do not make one score, applause count, follower count, standard, publication volume, or institutional claim stand for all consequences.

MDPE.7:4.5 - Apply one explicit ChoiceRule

Use C.11 to state the rule by which the current basis supports one of four results:

• choose now — one option or lawful tie-set survives and no further feasible probe is worth its cost;
• reject the current set — no current option survives; when more Work follows, name the question that becomes current;
• probe again — one feasible observation can still change which option survives or whether the set is rejected; or
• another question is current — the present issue is generation, pool policy, selected-set declaration, planning, enactment, cultural inquiry, or another named problem rather than local choice among the current options.

The domain ChoiceRule should say how protected Music-or-Dance characteristics, affected Systems, live alternatives, transfer horizon, cultural uncertainty, and present resource limits bear on the result. Expert judgement is allowed; hidden judgement is not.

MDPE.7:4.6 - Connect the choice to authority and intended Work

A ChoiceResult does not authorize or plan Work. Relate it to the conditions needed for use:

• the direct authority relation that independently supports the bounded choice; if no current direct governor exists, return the A.6.RCD missing-governor result rather than inferring authority from a job title or assignment;
• the practice-developing Agent and, when different, the Agent that can perform the intended Work, with supporting non-agent Systems named separately;
• permission or non-prohibition through A.2.8.PER when applicable, without treating it as authority, capability, readiness, or success;
• the intended bounded Work and result, without claiming that the Work occurred;
• a U.WorkPlan under A.15.2 only when planning is current; and
• a tool or call plan under C.24 only when that planning is current.

This is a relation inventory, not a first–then Work sequence. Some relations may already obtain before the comparison; others can remain missing after a lawful choice.

If the System that compared the options lacks decision authority, return a recommendation to the named DecisionSubject. If no current authority relation supports the bounded choice, return an unavailable-decision account with the blocked decision and retry condition. If a decision under supported authority exists but permission, capability, resources, or another Work-entry condition is missing, keep the choice and return the unavailable-Work condition separately. Do not widen the chooser label to make either gap disappear.

MDPE.7:4.7 - State revisit, stop, and rollback conditions

Name observations that can reopen the decision, such as:

• a representative performer or pair cannot perform the representative Work under the selected branch;
• safety, consent, accessibility, effort, partner readability, musical plausibility, or another must-constraint fails;
• a changed configuration invalidates evidence;
• a retained alternative becomes feasible or a selected one loses source return;
• the receiving population or event conditions change;
• another bounded probe can now reverse the choice;
• authority, permission, capability, or resources change; or
• the question crosses from local project Work to transmission, retention, loss, or trajectory inquiry.

State rollback or safe-stop treatment when the selected Work can damage a bearer, performer, repertoire, event, or relationship.

MDPE.7:4.8 - Return the next-development decision account

Return a readable account containing:

Next Music-or-Dance development decision account:
  DecisionSubject and granularity:
  practice subject, configuration, use, and affected Systems:
  current OptionSet:
  admitted source results and limits:
  comparison basis and domain ChoiceRule:
  lawful ChoiceResult and reason:
  another current question and applicable Method, when needed:
  authority, permission, consent, and refusal boundary:
  practice-developing Agent or intended Work performer:
  intended bounded Work and result:
  protected characteristics and retained alternatives:
  resource, capability, safety, and evidence limits:
  revisit, stop, rollback, or retry condition:

If ChoiceResult = probe again, the next bounded development Work can be the named probe when authority and capability obtain. If ChoiceResult = another question is current, name that question and its applicable pattern or direct Method; do not wrap the question change in an invented Work decision.

MDPE.7:4.9 - What Changes in Practice

Before this pattern, a project reacts to the latest performance, metric, opinion, or trend. After it, the DecisionSubject can show the bounded options, the domain rule, the evidence that matters, the authority boundary, the intended Work, and the condition that would reopen the choice. The next step becomes small enough to perform and informative enough to develop the named practice.

MDPE.7:5 - Worked Cases and Boundaries

MDPE.7:5.1 - Music arrangement: presentation or another rehearsal

Suppose MDPE.15 reports that an arrangement artifact was revised to restore an antiphonal relation and that one bounded rehearsal supports improved clarity while one articulation judgement remains uncertain. The current DecisionSubject is the production team. Performing in the ensemble does not by itself establish authority for this decision.

The live options may be: present under the tested conditions, run one additional rehearsal with the intended room and singer, revise articulation first, or perform maintenance Work that retains the acoustic branch and suspends the electronic branch. The current set can instead be rejected for the present concert use. If the room-and-singer rehearsal can still reverse whether presentation is safe and musically plausible, ChoiceResult = probe again can select that rehearsal as the next bounded Work. If it cannot change the survivor relation, choose now rather than demand more analysis.

The rehearsal schedule, venue permission, and any WorkPlan remain separate from the choice.

For a completed choice, see the constructed social-dance and live-music application. Its organizing team selects an unfamiliar-partner transfer trial and keeps the current event block for one month; the observations do not yet support the larger festival investment.

MDPE.7:5.2 - Social dance: do not scale a phrase after one fluent pair trial

A pair trial reports that one Urban Kiz phrase is fluent for the participating dancers but partner readability degrades at a faster tempo and in denser floor traffic. A teacher or event team should not infer that the phrase is ready for a general class or party programme.

For a teaching-development decision, live options can include another varied-partner transfer trial, a slower-tempo cue repair, a branch for advanced participants, or a teaching format limited to lower floor density. The current set can instead be rejected for the proposed crowded-floor use. The deciding teacher or school, participating dancers, pair, venue, and scene remain different Systems. A bounded varied-partner trial may be the next Work when it can change whether the branch remains live.

This is a constructed application; it does not report a named class, pair, or event.

MDPE.7:5.3 - Movement-generation project: return to practitioner comparison, not platform release

The Chédin et al. case supports high- and low-fidelity movement-generation outputs having different practitioner uses, while a middling compromise was rejected in that setting. A maintained alternative account can record the branches, their proposed uses, and the evidence about availability.

Before choosing another dancer-involving comparison, a model or interface repair, or maintenance Work for the low-fidelity stimulus branch, establish that the relevant branch is available for the named practitioner use: its output or bearer can be obtained; a capable and permitted Agent can use it; and the required model, interface, configuration, access, and upkeep relations obtain. If only the account survives, choose reconstruction or upkeep Work, or let C.11 return reject current set; stopping is not disguised as another development-Work option.

The project team or other named DecisionSubject makes the next decision only under an independently supported authority relation. Release, cultural recognition, and transmission need separate results. A new model score that cannot change the performer-facing decision is not a reason to postpone the choice.

MDPE.7:5.4 - Shimon: the team chooses a configured trial; the robot performs it

After a changing-tempo performance trial, the human project team may compare: adjust gesture timing, change sensing, accept a bounded synchronization loss, run another observer task, or perform the documentation and configuration Work needed to retire the present branch. Shimon can perform Music Work autonomously within the demonstrated configuration. The human team is the reported practice-developing Agent; this account names it as DecisionSubject only for project-local choices covered by an independently supported authority relation.

The selected next Work identifies its robot configuration, tempo conditions, observer task, musical criteria, noise and gesture constraints, authority, and stop rule. A technical speed result from another configuration enters only if it changes this comparison. One trial does not establish cultural adoption or robot-held authority.

MDPE.7:5.5 - Cultural continuation is a different question, not invented project authority

A group of organizers observes that a social-dance variant appears less often at their event and considers declaring it lost or launching a restoration programme. Their event trace does not establish population-level loss, and their organizational authority may not extend beyond the event.

The lawful local result can identify MDPE.19 for a qualified account of the supported continuation and its limits, including a decision to continue only the current event or retire that local arrangement. A representative continuation test, probe again with a receiving-enactment observation, or a local event experiment is a separate choice when the Work is obtainable and its contribution warrants the full burden under the organizers’ actual authority. The result cannot be “the community will restore the style” unless a named chooser, authority, Work, population and later cultural relations support that claim.

MDPE.7:5.6 - Direct-decision and live-branch stops

Use a direct artistic, rehearsal, teaching, event, curation, operations, strategy, or engineering decision Method when it already supplies the bounded options, comparison, chooser, authority, intended Work, and revisit condition. Use A.15.7 when a current fact changes only the next action inside ongoing Work under an admitted Method. MDPE.7 adds no value by renaming either result as practice development.

MDPE.7:6 - Bias Annotation

MDPE.7:7 - Conformance Checklist

MDPE.7:8 - Common Failures and Repairs

MDPE.7:9 - Consequences

The pattern turns heterogeneous Music-or-Dance evidence into one bounded, accountable next-development choice. It prevents recent success, institutional visibility, performer skill, or cultural rhetoric from silently selecting Work. It also lets practitioners use expert judgement with visible evidence gaps.

The cost is a disciplined stop. Some results remain unavailable because the chooser, authority, capability, safe option, or discriminating evidence is missing. Some interesting observations are omitted because they cannot change the choice. That reduction protects attention and keeps the next Work small enough to perform and learn from.

MDPE.7:10 - Rationale

Developing practices do not follow one lifecycle. Composition, capability, configuration, performance, teaching, event operation, cultural memory, transmission, retention, and inquiry can proceed, overlap, pause, or recur under different Methods and authorities. The shared need is one decision that selects the next bounded Work from the present situation.

Music and Dance choices must preserve body, instrument, partner, ensemble, rhythm, material, performance, event, repertoire, style, and cultural distinctions that change which Work is informative or harmful. C.11 supplies the general choice result; this pattern constructs and interprets the Music-or-Dance development options and return.

MDPE.7:11 - SoTA and Source Use

Mutable web-source claims are dated to 2026-08-26. Recheck the affected choice only when a source, configuration, direct result, option, authority relation, or intended use on which it relies changes.

MDPE.7:12 - Relations

• C.11 supplies the local ChoiceResult. A.19.CPM supplies comparison relations when needed. Neither grants authority, commits, plans, or performs Work.
• A.15.7 is the preferred entry for bounded next-action steering inside ongoing Work when current facts change a live branch under an already-admitted Method. It does not replace the broader development choice here.
• MDPE.12, MDPE.15, MDPE.16, and later MDPE.20 are common conditional inputs. The full result table in MDPE.7:4.2 is a selection aid, not a required unfolding or Work order.
• MDPE.15 → MDPE.7 is evidence input only when the local changed subject, failed attempt, direct result, or bounded observations change the next decision.
• MDPE.16 → MDPE.7 is decision input only when live branches, stepping stones, repair needs, tests, or removal reasons change the current OptionSet or comparison.
• MDPE.7 → MDPE.15 occurs only when the ChoiceResult selects one feasible local change. The decision authority supporting that choice, the practice-developing Agent, an assignment when Work attribution needs it, applicable permission, capability, resources, and other Work-entry conditions remain separate; the chosen Work remains unperformed.
• A.2.8 governs obligations and prohibitions; A.2.8.PER governs permission and non-prohibition. E.10.ROLE only recovers ambiguous role wording; A.2.1 governs an obtaining assignment occurrence and its declared species; F.6 governs attribution when an Agent later performs Work under that assignment. Decision authority uses its applicable direct governor or an A.6.RCD missing-governor result. A recommendation is not silently upgraded to a decision under authority.
• A.15.2 governs a WorkPlan after choice when one is needed. C.24 governs tool or call planning. A.15.1 governs any later Work occurrence.
• C.36 and MDPE.17–MDPE.20 govern receiving and cultural claims. The project chooses only Work within its supported authority.

MDPE.7:End