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.