Loom replaces commit ceremony with an append-only operation log, live streams, named checkpoints, and hub sync for code, docs, design, data, configs, and AI-adjacent work.
Light mode keeps architecture diagrams, schema pages, and CLI references crisp. Dark mode drops the chrome back for longer reading sessions without flattening the Loom palette.
Loom is the versioning engine, the sync layer, and the timeline model for a project that spans more than a source tree.
Loom versions code, docs, design, data, config, and notes in one model instead of pushing every asset through a code-only mental frame.
Your history lives on your machine first. Hubs extend Loom with send and receive, but the timeline remains local and browsable.
Operations, checkpoints, streams, and sync state are explicit structures, which makes Loom easier to inspect, query, and automate.
Start with the operation log, streams, checkpoints, storage layout, and where each layer stops.
See negotiate, send, receive, object transfer, and how Loom talks to LoomHub without Git-era vocabulary.
Read the structured interfaces and AI context instead of reverse-engineering behavior from CLI strings.
loom init
loom status
loom checkpoint "before auth refactor"
loom log
loom stream create feature/auth
loom hub add origin https://loomhub.dev/flakerimi/my-app
loom send
loom receiveRead the argument for operations, streams, checkpoints, and a multi-space history model.
Initialize a loom, inspect detected spaces, and understand the local vault shape.
Use the current command surface for checkpoints, streams, hubs, send, and receive.
See the core engine, storage model, and sync boundaries before touching the implementation.
See operations, streams, checkpoints, entities, objects, remotes, and sync state.
Review negotiate, send, receive, transport types, and hub interaction patterns.