What "shipped" means on this site

Present tense on this site means shipped and exercised — not designed, not planned, not on a board. This page is that promise written down, so that every other page can be read against it.

What present tense covers

• the record and its projections;
• signed gates and proof-of-done merges;
• certificate-based machine admission;
• slots and seats with isolated profiles, locally and over SSH;
• multi-backend actors, including local models and deterministic tools;
• capped standing rules;
• the per-run cost ledger with billing classes, and the pricing registry;
• five surfaces — the command-line interface, the web console, the client API and gateway, the read-only projection an assistant reads through, and the editor extension — with the owner's inbox among the console's screens;
• refusals as recorded data;
• operating-system confinement with kernel read-deny for credentials, including kernel-enforced confinement for runs dispatched over SSH against a measured per-machine capability;
• a browser first-run wizard that configures a machine with no owner (first run);
• system packages and a macOS installer that deliver the machine payload — four binaries: the control-plane CLI, the runner-side agent, the gateway that serves the console and the first-run wizard, and the server host process.

⚠ Shipped is not the same as exercised everywhere. Which backend has been run on which platform, and what is therefore not proven, is one table: supported agents, runtimes and integrations.

The discipline this page exists to state

A control that ships opt-in is described as shipped and opt-in, never as on. That cuts both ways, and it is the reason a page here will sometimes tell you less than you hoped.

The standing example is egress control. It ships and is on by default: every run reaches the network only through a door that judges each destination against its policy, and the operating system walls off every other road — except a run explicitly opened with --egress-open, a proc run, and a container run whose class grants no network at all. Where a capability is built but not proven — the local container bridge, for example — its page says so rather than describing it as on (limits).

What this site does not carry

⛔ A roadmap. Work that is designed, ordered or in development is not listed here, and a page that named it would be inferring a promise from a design stream. Where a capability exists but has not been exercised, the page that owns it says so in its own row; where one does not exist, the page says that instead.

⇒ If you need to know whether something specific is coming, ask — the answer is a conversation, not a page that ages badly.