Fix and verify

Create a focused fix plan, review the proposed change, and require a new assessment before resolving a finding.

Open a confirmed finding and select Fix and verify.

A code change is not a verified fix

Resolve the finding only after a new assessment confirms the expected behavior and protected behavior.

Review the finding first

Confirm the expected behavior, observed behavior, customer impact, affected journey, and supporting evidence. If the evidence is incomplete, gather more evidence before proposing a fix.

Prepare the fix

Connect an approved repository

Use the workspace's approved GitHub App connection. The repository must be inside the authorized organization and scope.

Review the plan

The plan should identify the cause, intended code change, affected tests, verification journey, and safe rollback path. Reject unrelated changes.

Approve execution

A permitted user must approve the plan before execution. Approval is bound to the current finding revision and plan. A material finding change makes the old approval stale.

Review the result

Check changed files, test output, limitations, and the exact revision produced by the fix run. A failed or incomplete fix remains open.

Run verification

Rerun the affected journey and relevant variations. Invokeable compares the resulting product state with the original expected behavior.

Verification outcomes

Resolve the finding when the expected state and protected behavior pass with sufficient evidence.
Return the finding to confirmed when the failure remains.
Move it to needs evidence when the result cannot be observed reliably.
Reopen a resolved finding if the same problem recurs.

Manual fixes

You can fix the product outside Invokeable. Keep the finding open until you run the same verification journey. Record enough context for reviewers to understand which product revision was tested.

See Evidence and findings and Review results.

A newer successful run of the same test can automatically resolve its finding when the environment, agent, and variation match, the previously failing checks pass with objective evidence, and cleanup is verified. Resolved findings stop appearing under Issues to fix and stop affecting readiness. Open Resolved to review the original finding and its verification.

If the original test assertion was incorrect, first correct the test and rerun the affected journey. Open the finding and choose Resolve with verification. Select the successful run and explain what was wrong with the original assertion and how the corrected test still proves the intended result. Invokeable records this as Assessment corrected, with the original outcome, verification, and reviewer preserved. Changing a test alone does not resolve a finding.