Confidential compute belongs in the sealed lane (in testing).

Privacy belongs to a specific lane

The sealed lane is designed for confidential-compute GPUs in an eligible TDX environment. The node decrypts the request inside that environment and returns the response with an attested receipt. The host operator sees ciphertext rather than the prompt body in this flow.

Route the encrypted request

An OHTTP relay sits between the buyer and the sealed gateway. Attestation checks cover the environment, GPU evidence and allowed measurements. These steps describe the privacy architecture in the specification; they are not a blanket claim that every GPU or every job is confidential.

Distinguish the open lane clearly

Consumer GPUs and non-confidential hardware serve non-sensitive open-lane work. Operators may see open-lane prompts. Public-model batch inference, embeddings, evaluations and image generation are examples of work that can fit that lane when the inputs are suitable.

Understand the attestation boundary

The specification discloses limitations, including absent TDISP device binding and physical attacks outside its scope. Signed receipts show that work ran on a measured stack; they do not certify that a generated answer is correct. These boundaries remain part of the product explanation.