FableCut keeps its timeline in a JSON file, which is the design decision everything else follows from. A person cuts and arranges in the browser while an agent reads and rewrites the same JSON, and a REST API exposes the same operations for anything scripted. The UI live-reloads, so a change made from either side shows up immediately rather than after a rebuild. It ships with zero dependencies and runs in the browser, meaning there is no runtime to install before the first edit.
