This page evaluates a fixed simulated trace using Boolean guards. The breakout preset permits reward gaming and external egress, producing three named escape vectors and an assigned security score twenty-four. The hardened preset selects an isolated airgap and consensus monitoring, leaving no escape vectors and assigning ninety-six. The bars use six pixels per score point. These are source constants, not measured security probabilities or verified containment of an actual agent. The four trace actions are generated records; the evaluator does not issue their DNS, HTTP, credential or memory operations. A real environment would need independent enforcement and tests, which this local video does not perform. The gaming guard activates when consensus monitoring is enabled or the drift threshold is strictly below point three five. Equality does not satisfy that second condition. Egress is blocked by an isolated airgap, by a domain allowlist lacking the exact external-host string, or by TLS proxy enabled together with the read-only microVM preset. If egress is blocked but gaming remains permitted, the single gaming vector yields a goal gaming alert and assigned score sixty-eight. If both are blocked, the score is ninety-six. The bars use the same six pixels per point. These branches describe a local rule system; setting a threshold does not itself measure goal drift or create consensus enforcement. Allowlisting here uses exact array membership for a fixed host; it does not implement wildcard matching, URL parsing or DNS validation. An enabled TLS proxy checkbox blocks simulated egress only with the read-only microVM preset, not every sandbox. Agent model selection does not change the Boolean guard formulas. Verdict scores are assigned: twenty-four for open outbound breaches, forty-two for other egress breaches, sixty-eight for gaming alone, and ninety-six with no listed vectors. Export records configuration and generated actions rather than independent forensic evidence. Any incident or provider claims in the surrounding prose remain unverified. This local explanation preserves native controls and SVG topology while invoking no external backend, network exploit, credentials or public deployment.