0438267d

docs: networking stays minimal — just enough to be usable

a73x 2026-08-09 17:11

Commit message

docs: networking stays minimal — just enough to be usable

docs/decisions.md

Old		New
@@ -80,6 +80,17 @@ it. A host whose OS owns the guest network sits on a subnet no allocation of
80	ours can contain—so the fleet can only be told, which is also why a value it did	80	ours can contain—so the fleet can only be told, which is also why a value it did
81	not choose is never recycled back into the pool.	81	not choose is never recycled back into the pool.
82		82
		83	### Networking stays minimal: just enough to be usable
		84
		85	A guest gets an address, a way out, and the ports its tenant chose to publish—
		86	embedded DHCP, the host as NAT gateway, and a userspace port-forward table—any
		87	of which could be deleted with the VM still booting, syncing, and taking SSH.
		88	Instead of growing the agent toward a virtual router (guest DNS, ACLs,
		89	east-west, in-path policy). Network machinery that basic lifecycle would come
		90	to depend on is the mesh mistake again—a binding point taxing every feature
		91	before the basics stood—and anything the site's network already does better
		92	arrives with bridged networking, not inside the proxy.
		93
83	### No superuser principal	94	### No superuser principal
84		95
85	Every API principal is `{Tenant, Fleet}`; fleet-level endpoints are gated	96	Every API principal is `{Tenant, Fleet}`; fleet-level endpoints are gated