The phrase names a design
The appliance is designed for air-gapped operation. Self-hosted deployment is the assumption behind the console and the services. The console is built so that fonts and scripts are bundled with it, rather than fetched from an external origin when a page opens. A reviewer can inspect that choice in the build. It is the content of the phrase before anyone talks about a measurement.
Capable is an aim, and aims are smaller than results. The word says the design is arranged so that isolated operation is possible. A diagram with an outside network crossed out illustrates the aim. The diagram is not a packet capture, and this page does not treat the illustration as one. Measurement, where it exists, is named in the next two sections as a build proof and as an unverified runtime.
The build can finish when the machine has no route out
A build proof shows that the build can complete with no route out. The doubt it answers is specific: whether producing the build itself depends on reaching a network. In that proof, the build finishes without the route. The result belongs in the air-gap paragraph because a build that secretly fetched pieces would make the design sentence hollow.
The subject of the proof is the build. It is not the appliance after someone has started it, and it is not a later day of ordinary operation. Using the build proof as a stand-in for a runtime result changes the subject. This page keeps the build sentence and the runtime sentence in different sections so that a summary cannot accidentally weld them together.
Runtime egress has not been verified
Egress from a running appliance has not been verified. The private-AI surface says so in the product, and this primer repeats it because the phrase air-gap-capable is easy to over-read. An evaluation may adopt “no egress while running” as an objective it intends to test. The objective is a test that this build has not already recorded as passed.
A written report has room for three clauses and needs all three. The design is for air-gapped operation. The build can finish with no route out. Runtime egress is unverified. Dropping the third clause changes the claim into one this POC does not support. Until a runtime measurement exists, the third clause stays, and no icon on a slide replaces it.
The production profile refuses an external-dev-only model provider
A model provider marked external-dev-only is refused when the deployment profile is production. The loader performs the refusal. The refusal matters to the air-gap design because a production profile that placed a call to an external model API would put a route back into a configuration that is supposed to be able to live without one. The loader, not a comment beside the profile, is what stops that class of provider.
Scope follows the profile. Development that an owner has allowed, on a profile other than production, may still use such a provider, and the content on that path is limited to synthetic fixtures. A shortcut that called a provider while bypassing the model router would sit outside the loader’s refusal. The design does not permit that shortcut, because a path built around it would have to be torn out when a local model is the only one a production profile will hold.
Bundles, hardware roots, and today’s sign-in stay in their own boxes
This primer does not present an offline update bundle as a thing the POC ships, and it does not present a hardware root of trust as present. Time sync, software update, and machine identity still have to be designed for a network that does not phone outward. Those are production-phase designs. Writing them into this page as if they were already here would turn a recorded gap into a feature the build does not contain.
What the POC does contain has to stay labelled even on a machine with no route. People sign in by checking a password against a hash on a local account, which stands in for directory single sign-on. Keys that unwrap evidence are software keys, and the hardware tokens that would hold them are not in this build. Service hops authenticate with certificates from a software development CA, and the actor named in a request header is not bound to that certificate. Isolation of the network does not convert those stand-ins into directory SSO, hardware custody, or a hardware machine identity.
How to read this
| Read it as | Which means | Do not read it as |
|---|---|---|
| Design | Self-hosted, no font or script CDN | A measured runtime with no egress |
| Build | Can complete with no route out | The running appliance |
| Production profile | Refuses an external-dev-only model provider | A comment that says “air gap” |