Investigate abandoned repositories, uncover hidden issues, propose targeted repairs, and verify every change with an AI agent that values evidence over assumptions.
The Bit-Rot Crisis
Libraries stop running not because the logic is wrong — but because Python 3.12 removed APIs, abstract base classes moved, and test runners changed.
PEP 594 purged imp, cgi, pipes, distutils in Python 3.12. Code importing them crashes instantly with ModuleNotFoundError.
Mapping, Iterable, Callable moved from collections to collections.abc. Direct access now raises AttributeError on Python 3.10+.
Standalone mock instead of unittest.mock, unpinned transitive packages — installs fail before a single line of app code runs.
8-Stage Pipeline
Evidence-driven. Never trust an AI claim alone — every repair must pass a sandboxed test before it's declared a resurrection.
Validates source, blocks SSRF, copies into isolated workspace.
Maps language, dependencies, manifests, and test suites.
Deterministic parser finds PEP 594 removals, ABC drift, syntax errors.
Runs existing test suite before any patch to confirm decay.
Open-weight LLM proposes explanations for each finding.
Unified diffs produced for each decay. Human reviews before apply.
Patch applied in ephemeral dir. Tests re-run. Exit code 0 required.
Resurrection certificate, Markdown report, and .patch export.
Real Forensics
Health: 40 → 100/100 · Post-patch exit code: 0
Epistemic Boundaries
AI explanations are always labelled as hypotheses. Only a test suite exit code 0 in an isolated sandbox can declare a resurrection.
| Tier | Nature | Source | Declares Resurrection? |
|---|---|---|---|
| Observed Facts | AST parsing, subprocess exit codes | Python AST · GitPython | No — documents baseline |
| AI Hypotheses | Plausible root-cause explanations | Open-weight LLM | No — unverified assumption |
| Proposed Repairs | Unified diff modifications | AI Engine + Patcher | No — pending execution |
| Human Approval | Developer consent to apply patch | Interactive review UI | Prerequisite to apply |
| Verified Outcome | Post-patch sandbox exit code 0 | Isolated pytest sandbox | YES — Empirical proof |
Launch the forensic dashboard, investigate a sample repo, and see the resurrection certificate in under 60 seconds.