What problem does it solve? Coordinating commercial film hero renders across WitnessBC and SourceA lanes involves fragile manual steps: choosing the right wrapper versus the core compiler, enforcing one-render-at-a-time machine gates, validating routing SSOT, and tracking receipts. This Skill centralizes those rules so renders run consistently without resource conflicts or skipped validations. ## Core Features & Use Cases - Lane-based render orchestration: Run WitnessBC hero films or SourceA 32s proof cuts through wrappers that ensure local servers (:8090, :5180) and default beats, or call the core compiler directly with custom beats JSON. - Render law enforcement (R1–R14): Machine gate checks for RAM, CPU, disk, thermal/GPU, and zombie processes via the render guard script, with lock acquire/release, full logging, and checkpoint resume. - Beats and routing SSOT management: Author or upgrade beats JSON (v1 linear to v5 cinematic finish), validate routing and sync requirements before publish, and produce receipts plus Desktop MP4 outputs. - Use Case: A founder asks for the WitnessBC v5 cinematic render. The Skill validates routing, checks the Mac Guard status, runs the wrapper with explicit v5 beats, and verifies the receipt and MP4 before clearing the queued flag. ## Quick Start Ask the agent to run the WitnessBC commercial film render with the default v1 beats and confirm the receipt JSON and Desktop MP4 were produced.
