Questions about StackScopes.

It is a living operational model that connects resources, configuration, dependencies, time, and evidence. It differs from a static diagram because the model is designed to update and support analysis.

No. Monitoring remains essential for metrics, logs, traces, and alerts. StackScopes connects that evidence to infrastructure topology, changes, dependencies, simulation, and recovery context.

The discovery model is designed around a read-only cross-account role. A separate and more restricted execution role is required only for approved controlled-recovery workflows.

Model-based simulations run against the digital twin rather than intentionally disrupting a production resource. Results depend on the quality of topology, evidence, assumptions, and fallback information.

A relationship can include source, timestamp, evidence, and confidence. Confirmed and explicitly referenced dependencies remain distinct from probable or inferred relationships.

Blast radius is the direct and transitive impact that a failure or change could have across resources, workloads, applications, customer paths, teams, and recovery constraints.

AI assistance is designed to investigate, explain, simulate, and prepare recommendations. Production-impacting actions remain restricted by policy, deterministic validation, and human approval.

The initial product focus is AWS infrastructure and its operational ecosystem. The underlying product model is designed around general resource, relationship, time, evidence, and simulation concepts.