I built Branch Forge Story OS, a filesystem-based assistant for writing and managing stories non-linearly.
Instead of treating a story as a linear document, it models story knowledge as a filesystem:
scenes, characters, rules, and constraints are nodes
navigation happens via paths, not scrolling
invariants (canon, tone, social rules) are enforced explicitly
changes are localized (patches don’t ripple unless requested)
The goal is to support long, complex narratives without re-reading or losing consistency. You can write scenes out of order, branch timelines, and mount only the parts of the story relevant to the current operation.
This started as an experiment in applying systems design ideas (filesystems, invariants, mounts, diffs) to narrative writing. I’m curious how people here think about non-linear authorship, constraint enforcement, and whether this model generalizes beyond fiction.
PEACEBINFLOW•1h ago
Instead of treating a story as a linear document, it models story knowledge as a filesystem:
scenes, characters, rules, and constraints are nodes
navigation happens via paths, not scrolling
invariants (canon, tone, social rules) are enforced explicitly
changes are localized (patches don’t ripple unless requested)
The goal is to support long, complex narratives without re-reading or losing consistency. You can write scenes out of order, branch timelines, and mount only the parts of the story relevant to the current operation.
This started as an experiment in applying systems design ideas (filesystems, invariants, mounts, diffs) to narrative writing. I’m curious how people here think about non-linear authorship, constraint enforcement, and whether this model generalizes beyond fiction.
Feedback welcome.