| One Work and performer boundary are selected | The project configures an abstract show or one enormous System. | Name the occurrence or Work family and choose the smallest whole that carries it. |
| Constituents and external enablers stay distinct | Every venue, service, audience, or platform becomes a part. | State actual constructive and interaction relations. |
| Several views answer different concerns | Function, construction, timing, control, and placement collapse into one tree or process. | Select each view for the failure it exposes and maintain correspondences only where needed. |
| Descriptions stay separate from configuration | A score, diagram, stage plot, or approval makes relations obtain. | Name realization Work, actual participants, relations, and evidence. |
| Interface wording is recovered | A line or noun hides the load-bearing relation. | Identify the connector, port, protocol description, signal, representation, or direct interaction meant. |
| Timing is grounded | Count, timestamp, or onset substitutes for rhythm and coordination. | Name the actual carrier, event, perception, cue, and observation used by the decision. |
| Whole-level coordination is tested | Component success is generalized to the performance. | Challenge one load-bearing relation in representative Work. |
| Correction and safe stop are explicit | Readiness assumes a perfect run. | Name sensing, feedback, recovery, refusal, and stop conditions. |
| Agent and decision holder are not inferred from signal production | Robot, controller, conductor, or platform gets unintended authority. | Attribute Work and decisions to the Agent or System that actually performs them. |