---
title: "Verify AI-generated application changes before merging"
description: "Select regression checks from a generated diff, preserve acceptance criteria and collect completed run evidence before deciding a change is ready to merge."
canonical_url: "https://vostride.com/agent-library/software-factory/verify-ai-generated-code-before-merge.md"
md_url: "https://vostride.com/agent-library/software-factory/verify-ai-generated-code-before-merge.md"
content_kind: "guide"
topic: "software-factory"
---

# Verify AI-generated application changes before merging

Start from the diff and the requirement. List the user journeys whose inputs, permissions, persistence or navigation changed. A generated implementation may compile while sending the wrong record identifier or silently removing an authorization check; those risks need different assertions.

## Map the change to checks

For a role-editor change, pair an allowed administrator update with a denied member update and an unchanged unrelated account. For a cart change, verify the selected variant, quantity and independently calculated total. Use the [authorization](/agent-library/authorization.md) or [shopping cart](/agent-library/shopping-cart.md) recipes to expand the precise risk introduced by the diff.

Run the repository's required checks first. Add a real-interface test when the change affects behavior those checks do not observe. Keep existing regression coverage unless the requirement itself changed and the new contract was reviewed.

## Execute against the candidate revision

Start the candidate build in a known environment and seed test-owned data. Confirm the visible application revision or another reliable build identifier so a passing test cannot accidentally refer to an older running server. Validate the focused agent-qa file, execute it, then inspect the completed result. The [coding-agent workflow](/docs/agent-qa/guides/coding-agent-workflow.md) explains commands and evidence retrieval.

If a failure requires repair, keep the initial artifacts. Explain whether the cause was application logic, test intent, configuration or execution environment. Rerun after the relevant change; a result obtained before the fix cannot verify the fix.

## Produce the merge evidence

Report the tested revision, target, test file, run identifier and assertions that passed or failed. List blocked checks with their missing prerequisites. A short evidence table can distinguish “role update observed,” “permission denial observed” and “audit record checked by hook.” It should not collapse all three into a single green label.

Use the team's normal merge policy. A coding agent's narration, successful validation command or dry run does not establish that the application satisfied the acceptance criteria.

[Release evidence contract](/agent-library/software-factory/release-evidence-contract.md) · [Recorded evidence examples](/docs/agent-qa/guides/recorded-evidence.md)