How the practice works inside your posture

Every site has already decided how connected it is willing to be. Some have no path out at all. Some connect, but only to systems they run and secure themselves. Many estates have both kinds of building and intend to keep it that way.

E31 Consulting takes that decision as given. The practice does not ask a site to loosen its posture for an engagement, and it does not build in a way that would make the site want to. This article describes what working inside each posture looks like.

Posture is confirmed first and not negotiated

The posture of the site is one of the first things established at the start of an engagement, alongside what done means. It shapes where the engineers sit, how material reaches the appliance, how versions are published, and how the handoff happens.

It is confirmed, not discussed. The practice does not have a preferred posture it steers customers toward. It has a stack that works in all of them and engineers trained to work inside all of them, and it builds whatever the customer needs inside whatever the customer has.

Air-gapped: built with no path out

On an air-gapped site, the use case is built on the appliance from the first day with nothing reaching outward. Substrate provides inference, retrieval over the site's documents, memory, adaptation on the site's own material, evaluation, and integrity verification, all on the Czar in the rack. Agency provides the agent layer, the versions, and the run record on the same appliance.

Material enters the site by the site's own media procedures. Signed updates for the platform arrive the same way. The engineers follow those procedures and do not bring a channel of their own.

The practice does not build connected and disconnect at the end. A use case that ever depended on an outside path carries that dependency in its shape, and the point of an air-gapped site is that nothing does. Forward-deployed on an air-gapped site describes this in the forward-deployed form.

Connected: only what the site already secures

On a connected site, the use case reaches on-premise systems through declared routes. Each route is named in the scope, set in the version, and reaches a system the customer already runs and secures: the ticketing system, the records system, the planning system, the warehouse system.

What the use case does not do is reach anything the customer does not secure. There is no route to a vendor's cloud, no dependency on an outside service, no call the scope did not name. The customer's connected posture is the limit of what the version may touch, and the version is held inside it.

The site team can read the routes in the version afterward, which is how they know exactly what the use case reaches and how they change it when a system changes.

Mixed estates stay mixed

Many customers run several buildings in several postures, and have good reasons for each. The practice does not treat this as a problem to solve. It treats it as the shape of the estate.

Each building's use case is built for that building's posture. A version built for the air-gapped site is scoped and published for that site. If the connected site wants something similar, it gets its own scope and its own version, built for a connected posture. The two may share a starting point, but they are not the same version, and the practice does not push the estate toward uniformity to make its own work simpler.

Forward-deployed engineers on a mixed estate work inside whichever posture the building they are in has. A project for a mixed estate is scoped building by building.

Why this matters beyond the engagement

Working inside the posture is what makes it possible to leave cleanly. If the engineers never needed a path the site did not control, there is nothing to close when they go. If the use case never depended on something outside the posture, there is nothing that will stop working when the engineers are gone.

It also means the site team inherits a use case that fits the building they run. They do not have to maintain an exception made for the engagement, and they do not have to explain to their own security people why something reaches out that did not before.

Working inside sovereign and connected sites is part of what E31 certification covers. An engineer who needs an outside path to build is not ready for the practice. What E31-certified means describes the certification, and engineers who leave no path out describes the discipline at the end. The practice page at /practice covers how the practice approaches a site as a whole.