MDPE.24:4 - Worked Cases

MDPE.24:4.1 - One choreo-camp versus a persistent network

One camp brings teachers and learners together, records classes, and publishes videos. That can be an event and a set of Work occurrences inside an existing dance scene. Visibility, international attendance, and repeated branding do not yet require a new whole.

A persistent network becomes a serious candidate when recurring teaching, travel, status, booking, publication, and learner-migration relations hold it together; it retains repertoire and memory across individual camps; teacher and phrase selection changes over time; and the network changes how dancers train and choreographers create material in several cities. The project then compares two practical choices: improve one event/provider, or treat the network’s boundary, architecture, persistence, access, and downward effects as the engineering subject. If persistence and cross-city effects are only asserted, the result stays open and names the observation.

MDPE.24:4.2 - A short-video platform and a dance practice

A recommendation algorithm, camera convention, or viral phrase can mediate visibility and selection without becoming a dance practice or cultural whole. Engineer the mediating System and relation when that explanation is enough.

A platform-mediated practice becomes a candidate new whole only if actual production, imitation, publication, recognition, trend memory, participant relations, and recurring selection form an identifiable boundary and persist beyond individual trends, while also changing lower-scale phrase construction and training. Even then, the software platform, the wider participant practice, and a particular style remain different candidates. The project must select which one carries its current claim.

MDPE.24:4.3 - Annual social-dance festival editions

One festival edition is bounded event Work. A continuing festival series may be an enduring System if it retains identity, commitments, providers, participant relations, memory, operating capability, and interfaces across changing editions and organizers. Recognizing the series changes Systems Engineering and Operations Management: the project now addresses the series’ architecture, recurrence capability, records, supplier and community relations, and failure modes rather than treating each edition as an isolated event.

If only the name and archive persist while no recurring organization, capability, commitment, or constructive relation obtains, keep the editions and records separate.

MDPE.24:4.4 - A new genre label

A label can coordinate discovery, criticism, teaching, marketing, or community talk. Use those relations directly. Do not infer a new whole until the candidate has grounded construction, identity, states, memory, transitions, selection, persistence, and project consequences that the existing-whole explanation cannot carry.