LegacyTrace · Engineering candidate
Evidence before replacement.
Recover useful knowledge about undocumented Windows software without pretending every behavior is known.
The problem
Replacing an old application starts with understanding its behavior, dependencies, and gaps. LegacyTrace treats observations as evidence to investigate rather than an automatically complete specification.
Decisions that matter
Separate capture from analysis
The capture client records authorized observations. A separate analyzer organizes imported evidence into a case workspace.
Retain provenance
Evidence-linked annotations and reconstruction briefs preserve the connection between a conclusion and the observation behind it.
Represent missing coverage
Collector availability and loss information matter. An unavailable observation should remain unknown instead of becoming a confident claim.
Follow the workflow
- Define the authorized observation scope.
- Capture a controlled application session.
- Import and organize the evidence.
- Write findings with links and explicit unknowns.
What is implemented
Project records describe a milestone-complete engineering candidate with capture, analysis, packaging, and validation work. The current release is unsigned and records productionReady=false.
Scope and current limits
Not a customer-ready release. Signing, issuer trust, clean-machine qualification, and other release gates remain. No automatic complete reconstruction is claimed.