Skip to content

Blog

No hype, only what's real.

How the platform works and why it was built this way. Each post is long-form with a summary at the top, so you can read the whole argument or just the claim.

How it works

Short films, one noun at a time: what a Host is, the machine it runs on, the network it lives on, and where a request goes. Each post is the film plus the claims it draws, written down.

  1. · Part 1 · Film

    What a Host is

    A Host is one pod on a network: three containers, its own disk and database, two addresses, a certificate, no open port, and one outbound line to the platform.

    Read

  2. · Part 2 · Film

    Your machine

    Inside the pod: the three containers, the two disks and what is on each, where the certificate lives, and the rooms beside the pod that exist only while you use them.

    Read

  3. · Part 3 · Film

    The network you own

    Who may join a Host's network, how a home machine reaches a pod with no public port, which way traffic leaves and under whose name, the three lanes, and Host to Host.

    Read

  4. · Part 4 · Film

    How the Host handles a request

    Four kinds of agent on a Host, why the Host is not one, and where one request goes: a deterministic call, a scoped agent, or a coding harness.

    Read

  5. · Part 5 · Film

    What it remembers

    A row per turn, threads instead of sessions, entries derived on a schedule and superseded rather than overwritten, and a search that names its own gaps.

    Read

  6. · Part 6 · Film

    What it cannot do

    Five walls in code: a zero floor for agents, a gate at the operation, a refusal at the door, a widen that waits for your second factor, and no code outside the Host's own door.

    Read

  7. · Part 7 · Film

    Building with it

    The Workbench: a project that is a conversation and a workflow, seven coding engines running on your own keys, one rolling pull request, and the licence that travels with an app.

    Read

  8. · Part 8 · Film

    Data that stays home

    Your own computer joins the network by running one program. It keeps its folders, answers questions about them on your hardware, and can serve the model that does the thinking.

    Read

  9. · Part 9 · Film

    The Distributed Context Network

    Your files stay where they are. The Host holds a route map — what exists, where it lives, who may touch it — and every read travels to the data.

    Read

Subscribe: RSS.

Blog — Privatae