Library / Music and Dance Practice Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:20:20 UTC

MDPE.8:0 - Use This When

Use this pattern when a project says it will create, improve, teach, perform, preserve, spread, or modernize music, dance, a style, a school, or a scene, but the next decision still has no clear subject.

This ambiguity is expensive. A team can improve a recording while the performance Method remains unusable, train one dancer while the partnered configuration remains broken, publish a course while no learner transfers the capability, or promote a style name while the practice that made it recognizable disappears.

The first useful result is a bounded development focus. It contains a current characterization, the live alternatives that could still change the work or one material uncertainty that prevents forming them, and the smallest decision that matters. It names:

  • the deciding Agent and the decision now waiting;
  • the Music-or-Dance Work that matters;
  • the subject expected to change and what is known about its current state;
  • the competing subjects, Methods, explanations, or change questions that remain live;
  • the uncertainty or observation that can change which alternative is current;
  • the capable Agent, bounded Work, and Method that the Work will enact to make or test the selected change; and
  • the nearest stop, return, or unresolved dependency.

Stop when the deciding Agent can select the next bounded question or name the observation needed before that selection. Do not use this pattern when a direct composition, choreography, improvisation, rehearsal, teaching, production, event, preservation, ethnographic, historical, or Systems Engineering Method already names the subject and returns the result needed by the current decision.