Resolve Fusion
Thin router; depth stays in the kernel.
- Live tool mechanics —
docs/kernels/fusion-composition-kernel.md(thefusion_compboundary). - Offline authoring —
resolve-advanced/README.md→ thefusiontool.
Two servers — author offline, apply live
| Job | Server | Tools |
|---|---|---|
| Build/edit a comp on a running timeline item | davinci-resolve (Python, live) |
fusion_comp (probe_fusion_comp, safe_add_tool, safe_set_inputs, safe_connect_tools, fusion_boundary_report) |
Author a .comp from a spec/template with no Resolve open |
davinci-resolve-advanced (Node) |
fusion (generate, generate_from_template, list_templates, to_api_calls) |
Flow
- Author/verify offline:
fusion(action="generate"|"generate_from_template")→ a.comp, orfusion(action="to_api_calls")→ the ordered tool/input/ connection calls. - Apply live:
fusion_compsafe_add_tool→safe_set_inputs→safe_connect_tools. Theto_api_callsoutput maps directly onto those. - Probe first (
probe_fusion_comp/probe_fusion_tool) — tool availability and input readability vary by Resolve/Fusion build; some inputs coerce or are write-only. Bulk mutation needs timeline scope, not the active Fusion page.
Never modify/transcode/derive source media (AGENTS.md).