Control Deck

Scope is the boundary; blast radius is the consequence.

Agent work should know what it may touch, what it must avoid, and what review is required before changes leave a contained workspace.

Dimensions of scope

Code and files

Modules, paths, packages, services, and generated artifacts that a run is allowed to inspect or modify.

Data

Datasets, regulated information, production records, exported files, and synthetic or redacted alternatives.

Credentials

Which environment-provided credentials are present, absent, or deliberately unavailable for this run.

External effects

Pushes, deploys, ticket writes, cloud mutations, notifications, billing changes, and other effects outside local state.

Containment

LexRunner's contained execution direction is about keeping blast radius small while allowing parallel agent work. Promotion out of containment should be gated, receipted, and easy to review.