A box↑ Why · Someone checks every claim before trusting it What a box can touch is a short list, stated, and tested from inside the box.
A box sees only the files it was given
Shown when from inside a box given one folder, the node's key, its state, ~
and every other folder are absent, and writing outside the folder fails.
How The box
Not built: nothing in the code or tests names this yet.
A box reaches the network only through the node's gate
A rule that something else can dial around is a suggestion: the prototype bound its browser's HTTP to a policy, and a page's own WebRTC dialled straight past it.
Shown when a box's TCP, UDP and DNS, raw sockets included, all reach a fixture listener through the gate or not at all; the box has no network interface of its own beyond one whose other end is the node.
How The gate
Not built: nothing in the code or tests names this yet.
A box can't see or signal the node's other processes
Shown when from inside a box, the process list holds only the box's own, and signalling or tracing a pid outside it fails.
How The box
Not built: nothing in the code or tests names this yet.
A box can't take the node down
Shown when a box that allocates without end, forks without end or fills its disk is stopped at its limits, and the node and every other box carry on.
How The box
Not built: nothing in the code or tests names this yet.
Making a box needs no root↑ Why · Alex reaches the laptop at home from a café The machine Alex pairs in a minute, as an ordinary user, can run a browser box.
The first minute is one line run as an ordinary user, and a box must not add a second line that isn't.
Shown when on a fresh Ubuntu and a fresh Debian with the node installed by its one line, without sudo, the box tests above pass.
How The box
Not built: nothing in the code or tests names this yet.
The gate↑ Why · Someone checks every claim before trusting it Every connection a box made is there to read, with what the gate decided.↑ Why · Sam lets an AI help, and decides what it sees Sam can see every host the agent's browser dialled.
A box's reach is stated, and checked at each dial
Names resolve to whatever their owner likes, so the address is what's checked, at the moment of each dial.
Shown when a box allowed only the internet is refused a name that resolves to a LAN address, and a name that changes to one between two dials is refused the second time.
How The gate
Not built: nothing in the code or tests names this yet.
Every connection is in the audit, allowed or not
A box's own record of what it did is worth nothing; the node's is written outside it.
Shown when after a fixture box dials ten hosts and is refused three, the node's audit for it holds thirteen entries, each with time, name, address, port, protocol, bytes each way and the gate's answer.
How The gate
Not built: nothing in the code or tests names this yet.
A box's audit reaches your devices, sealed
Shown when an entry written on a node appears on another device of the account, and a capture at the relay holds none of it in the clear.
Not built: nothing in the code or tests names this yet.
Behaviour no rule allowed for is raised, not only logged
A log nobody reads catches nothing. A burst of refused dials, the first connection to an address on the node's own network, a host never seen before for an extension that names its hosts, or more sent than received past a limit, each tells the account's devices.
Shown when a fixture box that scans twenty LAN ports raises one notice on another device, naming the box and what it did.
Not built: nothing in the code or tests names this yet.
Extensions↑ Why · Sam lets an AI help, and decides what it sees An agent's tool from someone else runs with the folder and hosts it was given, and nothing more.
An extension declares what it needs, and gets no more
Shown when an extension whose manifest names one folder and one host is refused, and audited, when it opens another folder or dials another host.
Not built: nothing in the code or tests names this yet.
Each instance of an extension is a box of its own
The same extension used for two things must not join them.
Shown when two instances of one extension, given different folders, can't read each other's folder or state.
Not built: nothing in the code or tests names this yet.
An extension is a service like any other, and never holds a key
Shown when the box interface has no key-bearing call; an extension's calls
reach the node as the service it is, with the caller verified
(service/verified-caller).
Not built: nothing in the code or tests names this yet.