vean

vean studio — Video Editor, Agent Native · vean.studio

The agent-native video editing core. A typed document, edit algebra, and diagnostics layer for video editing on top of MLT — a language server for video.

Status: active development. The headless core, action runtime, React/Remotion viewer, and local Tauri app are implemented behind verification gates. Package, release, and remaining breadth work is tracked in ROADMAP.md.

Why

Video editors maintain timeline validity implicitly, inside carefully-written command code, and never tell anyone why an edit is or isn’t valid. That’s fine for a human dragging clips; it’s hostile to an agent — and to anyone who wants to build a different UI on top.

vean inverts that. It is a frame-exact, rationally-timed model of a timeline that an agent (or a UI, or a human) mutates through a closed set of operations, each of which reports its consequences before a single frame renders:

• a typed IR for an MLT timeline — multi-track, audio, keyframes, filters, transitions — that round-trips losslessly to .mlt XML (the format Shotcut and Kdenlive read/write);
• a pure edit algebra — op(state) → {state', consequences, inverse} — so every edit is legible, reversible, and identical whether a human or an agent issues it;
• a diagnostics layer (the “LSP”): gaps/overlaps, out-of-bounds keyframes, A/V-sync hazards, dial-range violations, plus go-to-definition (resolve a param’s value at a frame, through clip → track → tractor → transition) and find-references (what uses this source, what ripples if I move this).

vean’s core is not a renderer, a motion-graphics engine, or a GUI. It delegates:

• Render → melt (MLT/FFmpeg), driven as a separate process. The CLI/source install uses system deps; the Mac app can bundle pinned renderer sidecars.
• Motion graphics → Remotion, as a producer (pre-rendered alpha clips for export; @remotion/player for live preview).
• UI → the local Tauri Mac app in app/, built on this core. The website is for download/docs, not a web editor.

The timeline core is stateless: files in, files out. Product coordination state is local-only: CLI/LSP/MCP/app metadata lives in gitignored .vean/vean.db and never replaces committed timeline files.

Architecture

Four layers:

1. Core (headless) — the typed document + serialize/parse + keyframes + edit algebra + diagnostics + the melt/ffmpeg driver.
2. Action runtime — one typed registry for product behaviors, projected to Commander CLI, MCP tools, deterministic LSP code actions, and the Tauri app. Every public action is available through ergonomic commands or vean action run --input-json ....
3. Agent bridge — vean-lsp for ambient diagnostics/navigation/code