03-external-systems

To identify external systems a codebase communicates with, scan package manifests, configuration files, and HTTP client patterns for references, then classify each connection by system type and access direction.

Auto-discovery of external dependencies from configuration files extracts connection strings and config keys to map system boundaries, providing the foundation for validating project boundaries and architecture diagrams.

Scanning package manifests and HTTP clients extracts evidence of external API calls and data store connections, classifying systems by type and access direction to validate architectural boundary definitions.

You need to map external systems for a C4 Context diagram after completing initial codebase reconnaissance and boundary analysis to visually represent all data stores, messaging, and API gateways the application interacts with.

Yes, you can classify external integrations by access direction by extracting evidence from package manifests, connection strings, and API clients to determine whether the codebase reads from or writes to each external system.