Design, build, and runtime are three sentences
The appliance is designed for air-gapped operation. The console is built so that it does not reference an external origin, and the only declared egress in the design is the forwarder sink the product names. A separate proof shows that the build can complete inside a network namespace that has no route out.
Runtime egress of a running appliance has not been verified. The private-AI surface says that in the product, and this note says it again because the design sentence is easy to slide forward until it covers the running box. An evaluation that wants the third sentence puts a test in the plan and leaves the result empty until the test has been run.
What the build proof covers
The build proof is about the build. It shows a completion with no route out of its namespace. It supports the claim that producing the software does not depend on fetching pieces at the last moment. It says nothing about what a process may open after someone starts it on a host.
Other controls sit beside that proof and should be named at their own strength. Inter-service calls in this POC present certificates from a software CA, and every service runs as one operating-system user against one material tree, so a compromise of one service process yields the identities of the others. The header that carries an actor is not bound to the certificate. Those facts belong in the same description as the air-gap design, because a closed network does not repair them.
A diagram does not add a measurement
A picture of the appliance with the cloud crossed out is a picture. If the picture is used, the caption carries the unverified runtime sentence, or the picture is doing the work of a result. Readers remember the icon, and they read only the caption the author wrote.
The same rule applies to a slide that says zero egress because the goal is zero egress. The goal is a design intent. The build proof is a result about the build. The running appliance is unmeasured on this point. Three lines, in that order, are the whole claim the current evidence can hold.
External model calls sit under a profile rule
Development use of an external model API is a separate regime from the air-gap design. A provider with the sovereignty label external-dev-only may be loaded only outside the production profile. The production profile refuses it. That refusal is how the two stories stay apart.
The verdict path does not dial out to a model. Where a development call is permitted at all, the content is a synthetic fixture and the call goes through the model router. Mentioning an external model in the same paragraph as the air gap, without the profile condition and the fixture rule, blends a development convenience into a deployment claim. An evaluation site with no route out adds a simpler constraint: the call cannot leave.
The plan column stays empty until the run
Evaluators can write the runtime check, the clock, the identity provider, and the media used for policy into the test plan. This POC includes neither a signed offline update bundle nor a hardware root of trust, so the plan should say what the team will do instead. Those sentences belong in the plan.
They move into the results only after they have been done. A report that copies the plan into the past tense has manufactured a measurement. This note is about keeping the plan column and the results column from sharing a sentence.
How to read this
| Read it as | Which means | Do not read it as |
|---|---|---|
| Sentence one | Designed for air-gapped operation | Already measured |
| Sentence two | The build can finish with no route out | The running box |
| Sentence three | Runtime egress is not yet verified | A crossed-out cloud icon |