Codebase ICU — Autonomous Software Recovery

Software debugging often stops at “the tests failed.” Developers still have to manually determine what broke, which change introduced the regression, how to safely repair it, and whether the repair actually works. This process can be slow, repetitive, and risky—especially when an attempted fix changes the broken environment itself. Codebase ICU is an explainable autonomous software recovery workflow designed to address this problem. The system follows a clear recovery chain: Failure → Evidence → Root Cause → Safe Repair → Verified Recovery A developer provides a local Git repository through the Codebase ICU dashboard. The system runs the project's tests, identifies failures, and gathers supporting Git evidence such as commits, diffs, file history, and execution information. The resulting evidence helps identify the change and code responsible for the failure. IBM Bob 2.0 is used as the AI investigation and repair agent. Bob reasons over the failure and repository evidence, traces the execution path to the root cause, and assists with the repair. The repair is kept isolated in a Git worktree rather than being applied directly to the main branch. Codebase ICU then runs the tests again inside the repair sandbox and compares the results with the original broken state. This provides an auditable demonstration that the repair works while the original main branch remains unchanged. The primary target users are software developers, engineering teams, and maintainers who need to diagnose regressions and safely recover working software. The project's key distinction is that it does not treat AI-generated code as the final answer. Instead, it makes the complete recovery process traceable: the failure is connected to evidence, the evidence to a root cause, the root cause to an isolated repair, and the repair to measurable verification. For the demonstration, an intentionally introduced authentication regression causes expired-token requests to return HTTP 500 instead of HTTP 401. Codebase ICU traces the failure to the responsible code change, records the IBM Bob investigation, verifies the isolated repair, and demonstrates 9 passed / 2 failed tests on the original state versus 11 passed / 0 failed after repair.