MDPE.16:4.3 - Constructed Music case: restore a live-electronic branch before calling it available

A small ensemble wants to keep both a sparse acoustic-response arrangement and a live-generated-response arrangement for a spring performance. The electronic branch was used only once in four recent events. That trace alone does not show whether equipment access, venue rules, performer readiness, latency, curation, audience response, or sampling variation is narrowing use.

The ensemble initially reports the electronic branch as suspended, not live: its old plugin no longer runs on the replacement laptop and the venue has not approved the networked setup. The production lead has authority over the approved equipment budget and assigns direct configuration and rehearsal Work. An audio engineer restores the project from source stems in a supported environment, documents the changed plugin and its audible limits, obtains the venue’s equipment permission, and prepares the acoustic branch as fallback. The musicians then perform a twenty-minute representative rehearsal with the replacement laptop, expected monitoring, response timing, and one simulated network failure.

The rehearsal record, measured latency trace, successful fallback, musician report, and venue permission are evidence only for this configuration and performance window. They change the electronic branch from suspended to live for the spring performance. They do not prove audience preference or cultural retention. If the same setup cannot be restored on a second machine before the stated date, the branch returns to repair before trial; if the rights or source project become unavailable, it becomes archive only. A later venue rejection would establish an access constraint, while a claim that latency causes curators to reject the branch would still need a bounded causal-use basis or a reversible trial.

In the paired unchanged case, the same musicians, restored configuration, venue permission and spring performance window remain supported, and no new relevant problem has appeared. The rehearsal record is older, but remains applicable; the electronic branch stays live without another rehearsal. If venue permission ends or the plugin again becomes incompatible, the corresponding availability fails even if that record was produced yesterday.