mixer-scene-contract

What problem does it solve?

Designs a structured, auditable contract for mixer scene changes to prevent ambiguous or unsafe operations. It defines required identifiers (show_name, snapshot_name, cue_name, scene_id, setlist_ref) and an explicit approval workflow, plus an auditable trail for decisions and actions.

Core Features & Use Cases

• Explicit naming and identity fields for scenes and cues (show_name, snapshot_name, cue_name, scene_id, setlist_ref).
• Audit-ready workflow: approvals, decision logging, and operator attribution.
• Schema-driven guidance for CLI dry-runs, show-director updates, and test coverage.
• Use Case: a show director requests a mixer scene change, the contract enforces approvals, logs actions, and yields a verifiable audit entry.

Quick Start

Draft the initial mixer-scene contract with required fields, approval flow, and audit entries.