Version control is one of software engineering's most transformative practices, but systems engineering — the discipline that coordinates requirements, interfaces, architecture diagrams, and verification plans across mechanical, electrical, and software domains — has been remarkably slow to adopt it. Most systems teams still ship Word documents over email or wrestle with Requirements Management tools that don't diff, don't branch, and don't merge. This video from Dalus (a tiny 21-subscriber channel) walks through what a Git-style workflow actually looks like when applied to systems engineering artifacts rather than source code.

What makes this worth watching is the translation problem it tackles: systems engineering data is structured (requirements have IDs, traceability links, verification status), so naive text-diffing doesn't work. The video shows how Dalus models branching, merging, and change review for requirements and architecture — the same primitives that made Git indispensable to software teams, adapted for a domain where a "merge conflict" might mean two engineers changed the same interface spec.

Even if you never touch systems engineering tooling, the video is a useful case study in domain-specific version control design. Anyone who has thought about diffing JSON, YAML, or database schemas will recognize the same challenges here, and the solutions transfer.