Hi HN — I built Loom to facilitate swapping workflows within agentic orchestration systems: workflows are central to how they operate, but modifying them usually means either forking the system or wrestling with deeply coupled config. Loom treats workflows as a first-class concern with their own language and compiler. You define states, steps, phases, and ownership profiles, and it generates code in Go, Python, Rust, or TOML. It also includes visualization (Mermaid diagrams), interactive simulation, and diffing between workflow versions. Would love feedback on the language design and whether the abstraction level feels right.