Local-First Needs Egress Proof

If prompts, files, embeddings, or provider calls can leave the machine, the system needs to say where they go and under what authorization. ‘Local-first’ does not mean ‘local-only,’ and the distinction should be visible.

Document default endpoints, permitted exceptions, and the switch that enables external routing. Then verify the running configuration, not just the intended configuration, because environment files and provider defaults drift.

A useful release receipt includes a captured request path or network check showing that the supported local workflow stays inside the declared boundary.