21. One door, on your own machine
Everything above the SDK talks to one HTTP server on loopback; the machine is the trust boundary, so every local process can call it; one read path, one write shape.

21. One door, on your own machine

Everything above the SDK talks to one HTTP server on loopback; the machine is the trust boundary, so every local process can call it; one read path, one write shape.

It is the surface every client, script and agent uses, and the honest edge of the privacy story.

Everything above the SDK talks to one HTTP server, on your own machine. The app, the command line, a script, the agent. All through the same door.

It binds only to loopback. No TLS. No login. The trust boundary is the machine. Anyone with a shell on it, and every process on it, can call the door.

Every dataset is read the same two ways. Query, or subscribe. Same filter. Same sort. Same stream.

Every write returns one shape. A version, a change id, the record ids. Never the record. Read it back through a query, where everyone else's writes arrive too.

One read path. One write shape. Strict bodies. A local-first system has as many copies as devices. Consistent behaviour keeps the copies consistent.

Check yourself. What does a write return, and what does it never return?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Connections0

Connections show where other documents or comments link to this document.

Related documents

Loading connections…