MDPE.3:2.4 - Name load-bearing relations and interfaces

For every relation whose failure can defeat the Work, state the participants, condition, direction or reciprocity, and observation that matters. Examples include partner contact and weight exchange, musician-to-musician cueing, instrument-to-audio signal, model-to-control display, controller-to-actuator command, performer-to-device sensing, venue-to-listener audibility, or emergency-stop access.

Treat interface as a prompt to recover the concrete object or relation. In one case it is a connector or physical boundary; in another a functional port; in another a protocol or API description; in another a direct interaction predicate. The shared word does not make them instances of one useful kind.

Keep proposals and actual relations separate. A score can describe timing, a rule card can describe contact, and a protocol can describe messages. Only actual Work and observation can establish that performers used them and the stated relations obtained.