system-cartography

Maps the internal and external structure of a legacy system for a migration or due-diligence assessment: components, dependency edges, entry points, end-to-end flows, integration contracts, data ownership, and runtime topology. Use as the cartography phase of legacy-code-discovery, or standalone during a migration or due-diligence assessment when asked what depends on what, where requests and events go, or what data is shared. Prefer legacy-code-discovery when the request spans more than one phase or needs a durable bundle. Works from source, build metadata, and contracts without assuming a tech stack. Not for routine code navigation or single-feature analysis.

Compatibility

Requires read access to the target repositories and write access only to the discovery bundle. Consumes the shard plan from legacy-code-discovery and repo-reconnaissance; bundle conventions live in legacy-code-discovery/references/okf-bundle.md.