Current-State Map

A current-state map gives everyone the same view of systems, ownership, dependencies, and risk. It should be accurate enough to guide decisions, not beautiful enough to hide uncertainty.

What to include

Capture:

• Critical business workflows.
• Applications, services, jobs, and integrations.
• Runtime platforms, environments, accounts, and regions.
• Datastores, queues, buckets, and external services.
• Ingress, egress, DNS, and major network boundaries.
• Source repositories, pipelines, and artifact registries.
• Owners, support paths, and escalation routes.
• Known risks, unknowns, and evidence gaps.

Map structure

Evidence

Support the map with links to systems of record:

• Cloud inventory.
• Service catalog.
• Repositories.
• Pipeline runs.
• Dashboards and alerts.
• Incident records.
• Architecture diagrams.
• Access and ownership records.

Quality bar

A useful current-state map makes disagreement visible. Mark unknown owners, unverified dependencies, and suspected risks instead of pretending the picture is complete.

Watchouts

• Diagrams go stale quickly without ownership.
• Infrastructure diagrams alone miss delivery and operational risk.
• Critical dependencies often live outside the cloud account inventory.
• Treat the map as a decision aid, not an audit artifact by itself.