Skip to main content

Layer 6 · Environment

Infrastructure Architecture

The environment and topology layer: how the same architecture runs across cloud, hybrid, on-premise, air-gapped, and sovereign environments without an application rewrite.

Last updated Version 2.4

The environment layer

The Infrastructure layer is the foundation of the stack — the physical and virtual environment and topology everything else runs on. Where the Technology layer above it decides how inference and compute behave, the Infrastructure layer decides where they live and under what trust and residency guarantees.

Its central promise is portability: the same architecture must run across radically different environments — managed cloud, hybrid, on-premise, air-gapped, and sovereign — without the layers above it changing.

Topology & building blocks

Infrastructure is composed from a small set of building blocks that recur across every environment:

Environments
The isolated boundaries — cloud region, data center, enclave, or sovereign jurisdiction — within which the architecture runs. Each has its own residency and trust guarantees.
Clusters & orchestration
The compute fabric that schedules workloads and inference. Orchestration is uniform across environments so operational patterns transfer between them.
Networking & connectivity
How systems of record, inference, and surfaces reach each other — including the deliberate absence of egress in air-gapped deployments.
Storage & residency
Where knowledge objects and evidence physically live, governed so data never crosses a boundary its classification forbids.

Portability without rewrite

Because the layers above depend on stable interfaces rather than a specific environment, moving from cloud to on-premise — or standing up a new sovereign enclave — is an infrastructure decision, not an application rewrite. A regulated program can start in managed cloud and migrate to an air-gapped enclave while the knowledge model, reasoning, and applications carry over unchanged.

Resilience & continuity

This layer also owns availability, backup, and disaster recovery. Institutional memory is only valuable if it survives failure, so continuity is designed into the topology: redundancy within an environment and recoverable state across environments, without compromising the residency rules each one enforces.

Deployment & security

The Infrastructure layer defines the building blocks; two companion references show how they are chosen and governed in practice.