Remedy AI-generated ≠ fixed.
A candidate becomes a verified software repair only when its configured deterministic verification succeeds.
Why code generation is not proof
A plausible patch can compile and still miss the original defect, introduce a regression or never reach the affected production service. Remedy keeps candidate generation separate from repair status.
Layered deterministic verification
Configured evidence may include a clean build, unit and integration tests, static analysis, API response assertions, a targeted reproduction check and post-deployment health probes. Projects decide which gates are required for each repair class.
Verification follows deployment identity
Remedy is designed to associate the approved repair with branch, commit and deployed source identity. The final check runs against the environment where the incident matters, creating an auditable link from failure to verified outcome.
Frequently asked questions
What does verified mean in Remedy?
It means the configured deterministic checks for the incident succeeded after the approved repair reached the target environment.
Can a merged pull request still be unverified?
Yes. Merge status describes source control; verification describes whether the original defect was resolved in the configured environment.
From bug report to verified fix.
See how Remedy connects evidence, diagnosis, repair, deterministic checks and production verification.
Explore the complete workflow →