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

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.3 - Ground each branch in use and availability

For every branch that may remain live, identify:

  • the intended Music-or-Dance Work and later receiving use;
  • the actual bearer or arrangement that must remain available;
  • the performing Agent or performing whole and the capabilities it must retain;
  • the body, partner, instrument, cue, venue, media, equipment, software, teaching, operational, or source dependencies;
  • the existing arrangement supporting availability, and the direct Music, Dance, teaching, archive, rights, capability-development, event, production, tool, operations or engineering Method when a condition needs obtaining or restoration;
  • the authorized Agent responsible for any needed upkeep or reconstruction Work;
  • the resource, consent, permission, attribution, access, and rights conditions;
  • the applicable evidence of availability for the named conditions, and a further observation only when its result is needed and worth obtaining; and
  • the premise change that would reopen availability, including a real rights, venue, calibration, resource or promised-use deadline when one applies.

A recording can support reconstruction; it is not the performance, Method, or capability. A movement animation can support a trial; it is not evidence that a dancer can use the movement with a partner. A software snapshot can support restoration; it is not evidence that licenses, hardware, performers, and venue conditions still permit use. A model score can characterize one representation; it is not performer-facing usefulness.