Adaptive Change Harness
Adaptive Change Harness is a self-evolving verification and repair system for real codebases.
Core trick
Replays a saved failing case before and after an LLM patch, then stores validated repairs as reusable skill entries.
Description
Adaptive Change Harness is a self-evolving verification and repair system for real codebases. Its core value is not just that it can call a model to suggest a patch, but that it wraps models inside a reproducible evidence loop: ingest a repo, discover a real latent failure, save the exact repro, repair it with grounded context, rerun deterministic validation, and then convert validated fixes into reusable repair skills. The product gets stronger over time because each successful repair becomes structured runtime knowledge that can be matched, reused, and improved on future failures.
The most eye-catching part is that it turns model output into hard operational proof. Instead of stopping at “the AI thinks this bug is fixed,” it shows failure before repair, no failure after repair, and passing baseline tests, all inside an operator-facing run console. It can capture latent bugs that baseline tests missed, replay them deterministically, generate and apply a patch, and end with a safe or unsafe verdict backed by evidence. On top of that, it automatically creates or updates a skill library from validated repairs, making the system visibly self-evolving rather than a one-off patch generator.
Standout features:
•
Real repo intake and profiling from uploaded zip files
•
Latent failure discovery with saved reproducible failure cases
•
Deterministic replay-based repair validation
•
OpenAI-powered grounded diagnosis and patch generation
•
Evidence-first verdicts instead of confidence-only outputs
•
Automatic creation, reuse, and revision of repair skills in skill_assets/
•
A run console that makes the full discover -> repair -> validate -> learn loop visible end to end
README excerpt
# Adaptive Change Harness Adaptive Change Harness is a verification and repair system for code changes and external codebases. It is built to discover real failures, reproduce them deterministically, repair them with model assistance, validate the result with hard gates, and learn reusable repair skills from validated fixes. This is not a generic agent shell. The durable product value is: - codebase intake and profiling - reproducible failure-case capture - deterministic validation and evidence - patch orchestration - a self-evolving repair-skill library ## Why It Gets Stronger Over Time The product is designed to compound. When a repair succeeds, the harness does not just return a patch. It also turns the validated result into a structured repair skill: - `created` when no prior skill covers the failure - `reused` when an existing skill already matches well - `updated` when a matched skill was useful but needed refinement That means each successful run can improve future runs. The harness gets stronger because it accumulates grounded repair knowledge tied to real failure cases and deterministic evidence, not because it stores generic chat transcripts. ## Product Loop The main V2 loop is: 1. Upload a real Python service repository zip. 2. Profile the codebase and infer how to run it. 3. Run baseline deterministic checks. 4. Execute adaptive discovery probes. 5. Capture a reproducible `FailureCase`. 6. Replay the saved repro as the deterministic repair gate. 7. Ask