Project study / Developer Tools
Prototype
Loom
A local-first long-form writing environment where the manuscript remains sovereign while structure and context gather around it.
Loom keeps book-length work in a local project package, with authoring surfaces for structure and context and optional connected intelligence that never owns the manuscript.
System portrait / documented flow
Diagram routes and groups
Canonical state
- Local project package
- Manuscript content
- Stable revisioning
Authoring surfaces
- Editor
- Binder / Corkboard
- Inspector / Timeline / Entities
Optional assistance
- Ollama or OpenAI-compatible
- Connected Chat
- Reply-only writes
- EditorLocal manuscript
- Corkboard / BinderLocal project
- Timeline / EntitiesLocal project
- Connected ChatOptional, reply-only
02 / Problem and response
Keep the manuscript sovereign while structure gathers around it.
Constraint
Long-form writing needs structure without turning prose into data owned by a cloud service or an AI assistant.
Approach
Loom keeps manuscript content local and uses Binder, Editor, Inspector, Corkboard, Entities, Constellation, and Timeline to organize work around it.
Optional AI features can assist through bounded context and reply-only writes while writing, organizing, and export remain useful without AI.
03 / Architecture and boundaries
Authoring surfaces and optional intelligence orbit a local source of truth.
A Tauri desktop shell joins a React and TypeScript interface to a Rust/native boundary for a local-first writing environment.
Project metadata and HTML content files form a local package with stable identities and revisioning; optional direct AI and Connected Chat sit outside the canonical manuscript.
Manuscript sovereignty
The local project package and its content files remain the canonical source of truth.
Authoring surfaces
Editor, Binder, Corkboard, Inspector, Entities, Constellation, and Timeline expose different views of the same work.
Optional intelligence
Ollama, OpenAI-compatible models, and bounded Connected Chat assist without mutating the manuscript.
- 01
Writing, organizing, and export do not require an account or an AI provider.
- 02
The current release candidate targets Apple Silicon arm64; source remains private during the RC cycle.
04 / Current state and next work
What exists, and what follows.
Prototype
The current release candidate targets Apple Silicon while the native shell and bounded assistance continue to harden.
Started 2026 · Last updated September 2026
Next direction
- Continue hardening the Apple Silicon release candidate and native-shell validation.
- Broaden bounded AI and editorial workflows only through author-controlled boundaries.
- Keep cross-format interchange separate from canonical project storage.
Local ownership is a product boundary, not just a storage choice.
Working lesson / Loom