fpf.tools
Library / Music and Dance Practice Engineering Principles Framework
Jump to passage
In this reading
Source · lines 855–875

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:20:15 UTC

MDPE.1:0 - Use This When

Use this pattern when a project is ready to commit people, equipment, venues, money, teaching, publication, or engineering effort, but its “creative brief” still moves silently among four different ambitions:

  • produce one artifact or performance occurrence;
  • establish or change a repeatable performance practice;
  • deliberately develop a style line across several variants and generations; or
  • build or change a medium or support System through which Music or Dance is produced, learned, presented, recognized, or retained.

Choosing the wrong subject can let one local output satisfy its acceptance criteria while the intended project result remains absent. A good concert does not establish a reproducible practice. A course does not establish learner capability. A platform does not establish a style. A manifesto does not establish that the proposed Method is enacted.

The first useful result is a project brief that states the selected subject and scale, intended Work and use, what must be preserved and may vary, the material conflict or unresolved live choice, whose recognition matters, which Agent can decide, what Work is expected to realize the proposal, and which observation reopens the decision. When two commitments cannot both be satisfied, keep the conflict visible in the brief and state which decision it changes. Do not use this pattern when a commission, choreography, production, co-creation, event, Systems Engineering, or other direct Method has already settled those questions and returns the project basis needed by the next Work.