A reactive, typed, cellular runtime. The same model, in many places. From microcontroller to cloud, from text to visual, from reactive to verifiable.
The reference implementation. 8 cell kinds, reactive DAG, MCP server, CLI, 30 tests. The most-tested Quilt. The starting point for everything.
Edit a value. The formulas recompute. The listener fires when status changes. The engine handles all the propagation.
Same model, compiled to native. Sync core with async cell evaluators bridged via Tokio. 68 tests, zero warnings. Two front-ends: quilt-tui (terminal) and quilt-web (browser via Axum + SSE).
Use the Rust runtime as a library, embed it in a TUI, expose it as a web service. The cell model is the API.
Full Quilt in one HTML file. 70KB. No build, no deps, no network. 54 working examples across 8+ domains. Save state as a cookie or download the whole app with your data baked in.
Try them all. Edit a value, watch formulas propagate. Save your work as a cookie or download. Open offline — it just works.
Every cell gets history. Fork the engine like git, rewind to a fork, replay events, merge two engines. The killer feature that makes Quilt a database, not just a reactive system.
at(t) — value at any past timediff(from, to) — per-cell change summaryfork(), rewind(), replay(), merge()Every set is a new version. Every cell has a history. The engine is undoable, branchable, replayable.
Every cell wrapped in an encryption envelope. The owner holds the master key. Each viewer in the access list gets a wrapped content key. The server only sees ciphertext.
Two devices, no server, no internet, no account — share cells. The mesh is the network. Lamport clocks + per-peer version vectors. Offline-then-sync. Conflict-free merge.
No cloud. No account. The peers are the network. Cells flow directly.
A no_std Rust port for ESP32-class chips. Sensors as cells. Actuators as cells. 3KB flash. WiFi + BLE mesh. Deep sleep for battery life. The cell model, scaled down to a $3 chip.
no_std, no allocator — everything in a static memory blockMemory is values. Tools are API cells. Reasoning is a chain of program cells. The agent is a sheet. Multiple agents share cells. The graph is the team.
The agent is just a Quilt sheet. Memory cells persist, tool cells are APIs, the reasoning chain is data flow.
An image is a value cell. Computer vision is a formula on the image cell. Eight built-in kinds: caption, OCR, faces, objects, tags, embed, segment, depth. Local or remote models.
A cell is also a statement you can prove. "My bank balance ≥ $50k" without revealing the balance. "I voted" without revealing how. 6 pre-built circuits. Real ZK backend (Noir) plugs in later.
value_at_least — prove ≥ thresholdvalue_at_most — prove ≤ thresholdvalue_in_set — prove membershipsum_equals — prove sum equalsgroup_membership — Merkle proof of membershipcredential_present — prove a credential claimDrag-and-drop cell wiring, like Scratch but for cells. The data model is stable, the UI is a single-page web app. The editor itself is a Quilt sheet — cells all the way down.
Pick the repos you need. Compose them. The cell model is the API.