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:30:20 UTC

MDPE.1:1 - The Recurring Difficulty

Music-and-Dance projects often begin with a compact phrase: “make a piece”, “launch a dance style”, “build an AI music practice”, “run a festival”, or “preserve the tradition”. The phrase can coordinate enthusiasm while leaving different Agents committed to different results.

Four project subjects recur:

Project subjectWhat the project changesEvidence that begins to matter
Artifact or performance occurrenceMusical or movement material, production, and one bounded performance or artifact.The occurrence happened or the artifact was produced and used under the stated conditions.
Performance practiceA repeatable Method, performing capability, configured whole, teaching and receiving conditions.Representative Work can be performed again with stated continuity and variation.
Style-development lineHow variants are produced, recognized, selected, transmitted, retained, and fed back into later production.The proposed architecture changes those relations locally; later distributed uptake remains a separate claim.
Medium or support SystemInstruments, software, venue, platform, school, archive, event series, provider, or another enabling System.The realized System enables the named Music-or-Dance Work and meets its use and assurance conditions.

The four subjects can be connected and developed together, but they are not one object and do not share one success test. A project may need several linked briefs rather than one ambiguous brief.