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 13:50:10 UTC

MDPE.11:5 - Checks and Common Repairs

CheckFailure it preventsRepair
Material, description, and occurrence stay distinct“The choreography was performed, so choreography is the performance.”Name material, bearer, performer, Work, realized result, and occurrence separately.
Proposed and obtaining constraints stay distinctA rule card creates the duet relation by wording.Observe whether the stated relation obtained among named participants.
Preservation and variation are explicit“Improvised freely” hides the Method and boundary.State preserved distinctions, allowed change, current facts, performer authority, and stop.
Direct domain Method remains primaryA generic pattern replaces music, dance, live-coding, partnering, or control practice.Use MDPE.11 only for material–Work integration.
Simultaneous Methods are not a lifecycleMulti-scale enactment becomes a fictitious sequence.Keep simultaneous Methods separate from any teaching or Work unfolding.
Performer and practice developer stay distinctA robot or performer gets authority over later development by grammar.Name who performed and who chose later Work.
Trace matches the claimVideo is used as evidence of pressure, felt control, or audience response.State what each trace can support and obtain the missing observation.
Recording burden is boundedEvery micro-choice becomes paperwork.Preserve only information that can change the receiving decision.