The programming model

Once composition drops beneath the language, programming here becomes ordinary programming — processes, pipes, files, and a shell. There is no SDK to learn, because the SDK is the coreutils; there is no framework to enter, because nothing on the floor calls into your code.

That is the small half of the story, and it is the half a sceptic checks first: what does a unit of work look like, who owns the control flow, what is running when nothing is happening. The consequential half is the last page — how a whole application is modelled out of the primitives, which is where the platform stops being a convenience and starts being an architecture.

Everything below runs on a machine that has never seen an API key: the userland ships fixture devices, so every line in these pages can be typed before any account exists.

• The workload is a Unix filter Input, black box, output — the node is a process and the connector is a pipe.
• Who owns the loop Your script owns the while; llm is a single-turn filter it calls.
• Nothing is resident Born from disk, runs, emits, exits — cost proportional to compute, not to time open.
• Application architecture An application is entities and actors — a graph whose edges are armings, and nothing else.