Key concepts
One shared model connects your cloud, a proposed change, and the consequences your agent needs to understand.
Base snapshot
A completed analysis captures the collected infrastructure of an AWS account and region. This is the baseline for a branch. A snapshot reflects collection time; it is not a continuously synchronized view of production.
Branch
A branch stores a base snapshot and an ordered list of changes. The engine rebuilds the hypothetical state by replaying those changes. Separate branches let you explore alternatives from the same baseline.
A branch models resources and relationships. It is not a running environment, a Git checkout, or a production deployment.
Change
A change adds, modifies, or deletes a supported resource in the model. Its fields must match the resource schema. Changing a resource can affect relationships and findings elsewhere in the collected cloud.
Lens
A lens evaluates one aspect of the model. Emfirge’s focused set covers Security and reachability, Configuration checks, Provisioned-cost estimates, Availability and recovery, and What needs a real run; each has its own coverage limits. See Lenses and coverage.
Diff and verdict
The diff explains what changed compared with the base: resources, edges, findings, and reachability. The verdict summarizes selected consequences as pass, warn, or block.
A pass means the current checks did not trigger a warning or block. It does not prove that a change is safe in a running application.