Inventory evidence and questions
Preserve source, executables, installers, configuration, data, logs and a working environment. Map dependencies, storage, protocols and startup behavior. Use static analysis for imports, resources and strings; use controlled runtime observation for actual files, registry, network and device interaction.
Deliver useful findings
| Continuity | Dependency and recovery documentation. |
|---|---|
| Migration | Behavior, data and integration specifications. |
| Repair | Evidence isolating the failing boundary. |
Exact source reconstruction is not a normal outcome from binaries; comments, names and original design can be absent.
See behavior analysis, dependency mapping, documentation and the pillar.