MDPE.Preface:9 - Architectural Rationale

MDPE keeps performance and style development in one language because the same project repeatedly crosses their boundary. The sound or movement produced today depends on learned capability, tools, selection, and support; changing that production can alter what later participants can learn or retain. Individually addressable patterns let the practitioner enter at the costly difficulty and stop when the waiting decision has a useful answer. Their publication groups make the field readable without requiring a complete end-to-end project.

Music and Dance share embodied timing, variation, coordination, recognition, and transmission, so a shared pattern can preserve a reusable move across both. The narrower profiles supply musical or movement material, specialist Methods, relevant observers, and tests. Shared membership earns its place only while the same recognizable problem, action, result, and stop remain useful. Separate Music and Dance frameworks become preferable if their recurring problems or maintenance needs diverge enough that readers repeatedly have to undo the shared account.

Several other architectural choices are consequential for use:

Serious alternative	Why this language uses another arrangement	When the alternative serves the reader
Direct FPF and Systems Engineering, specialist Methods, and a guide	Those sources can identify Systems, choices, and evidence while still leaving the practitioner to assemble the Music-or-Dance brief, performing-whole trial, receiving-use decision, or style-reproduction architecture. MDPE supplies the recurring domain integration.	Use the direct result when it already answers the same working question with the same practical result and limits. Keep only the MDPE contribution that still changes the action.
One broad style-engineering pattern	Configuration, recognition capability, support, local change, and continuation have different entry problems and independently useful results. Distinct patterns make each result reachable.	Use one direct Method when the present work has one coherent result and its complete move is already described. A broad chapter can explain shared reasons without absorbing the individual Methods.
Separate performance-engineering and style-engineering DPFs	Their frequent result exchange would make one project reconstruct connections between performance, capability, recognition, teaching, and later reproduction.	Reconsider the split when recurring uses and source changes mostly stay within one side and separate maintenance improves those uses.
One cross-domain Style Engineering DPF covering other cultures as well	FPF already supplies the transferable cultural-evolution distinctions. The constructive Methods and evidence for Music and Dance remain domain-specific.	Use FPF and the appropriate inquiry or domain Method for another culture. A new domain language needs its own connected practical contributions.
Organize the language primarily by body, phrase, performance, event, scene, and style levels	A working difficulty often crosses several simultaneous structures. Beginning from a level would hide the conflict or integration that the practitioner needs to address.	Use a scale or part-whole view inside a question that depends on that relation, particularly with `MDPE.14` or `MDPE.24`.

The Systems Engineering specialization concerns selected Systems: performers and equipment, production organizations, venues, schools, archives, or platforms. A project names what each change must enable for Music or Dance; it may need several System descriptions at once. Cultural style remains a subject of production, recognition, transmission, and inquiry through those relations. Method Engineering contributes when the changed subject is a Method, MethodDescription, family of Methods, or enactment support. Human capability-development, organization-change, and operations contributions enter when their results are needed by the selected use. External result use states the framework-edition reliance; a useful specialization relation does not by itself establish a dependency on a sibling edition.

Use MDPE.7 to form a next-development choice from heterogeneous domain results, and MDPE.15 to perform and test an already selected local change. A choice can be useful before the change is performed, and a failed attempt can inform another choice. Preserving both results makes that return clear. Similarly, generation, recognition, selection, transmission, and continuation keep distinct evidence demands. Their connections support an inquiry or development decision without making one success stand for the whole cultural process.