The document is the app.
One portable file carrying your data, your logic, and your interface. It works offline, survives every platform shift, and belongs to whoever holds it — not to a cloud account.
pill-tracker.brix
one SQLite file · the whole app
Anatomy of a .brix file
state_events · attachments · device_keys
Data — an append-only truth
Every action is an immutable event: Ed25519-signed by the device that made it, ordered by Lamport clocks, merged CRDT-style without conflicts. Heavy blobs live in content-addressable storage, deduplicated by SHA-256.
State in. Patch out.
Bricks never touch your device. The host hands in a slice of state; the brick hands back a declarative patch; the host applies it and appends a signed event to the log.
Any agent understands the file in one call.
brix inspect emits a compact manifest — modules with their typed contracts, data schemas, views, and the event-log summary — budgeted to 8 KB so it fits any model’s context without ceremony.
# pill-tracker.brix — manifest (7.2 KB)
## modules
- local-vault@0.1 · world: brick
execute(list<u8>) → result<list<u8>, string>
- scheduler@0.1 · world: brick
## schemas
- medications { name, dose, schedule, taken-log }
## views
- grandma-ui@v3 (default) · caregiver-dashboard@v2
## events
- 1,204 signed events · 2 devices · lamport 3,481
✓ agent context ready — no docs, no onboarding
The Family Pill Tracker
A real .brix app: local-vault + scheduler bricks, an elder-friendly UI, state that survives restarts — running in the reference viewer today.
Saturday · 08:00
Morning pills
reference viewer v0.1 · the production Brixel viewer is in development
Copy the file. That’s the sync protocol.
Fully offline-capable — the network is optional, not required.
Every event signed by a registered device key. Edits are attributable forever.
Move it on a USB stick, an air-gap, or any sync folder — the file is the app.
No account. Whoever holds the file holds the software.
Make one thing yours again.
Join the first people turning everyday requests into useful tools they can keep. No technical background required — just something you wish worked better.