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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:20:15 UTC

MDPE.16:3.1 - Bound the development question and later use

Name:

  • the Music-or-Dance practice subject and present configuration;
  • the question for which several answers remain useful;
  • the later performance, teaching, reconstruction, comparison, source-return, or combination use that makes each branch worth keeping;
  • the horizon and next decision;
  • the practice-developing Agent responsible for the branch set;
  • the Agent authorized to spend resources or change each branch’s availability arrangement;
  • affected Agents and Systems;
  • safety, consent, permission, source, access, and other protected conditions; and
  • the attention, rehearsal, equipment, venue, compute, rights, or maintenance budget.

A useful question is narrower than “preserve dance diversity.” For example: “Which partner-readable timing variants must remain usable while this Balboa phrase family is developed for social dancing at three tempo ranges?”

The practice-developing Agent need not own the alternatives, control the culture, perform every branch, or have authority to change every dependency. If required access, capability, permission or configuration does not obtain, a plan to restore it does not make the branch live. Retain a supported existing arrangement or report the affected branch as suspended or archive-only; any selected restoration still needs a capable, authorized performer.