Independent Verification
A methodology in the review of AI-generated code whereby independent systems, models, static analysis tools, or human reviewers that did not participate in generation inspect changes against pre-determined and repeatably applicable criteria. It is used to break the closed loop of model self-evaluation bias.
Core Facts
Timeline (last 90 days)
Acceptance checks are an executable verification method in spec-driven development: each check describes an observable behavior that the builder must make the system actually satisfy in the browser; unlike unit tests, acceptance checks usually start from the user's perspective and cover end-to-end flows across modules, but they only verify behavior that has been written down and cannot find boundaries the spec does not mention.
When the party writing the code also controls the means of verification, independent external validation becomes a necessity.
Organizations should not rely solely on the same probabilistic system that produced a change to judge whether that change is safe to ship; independent verification is essential.
Independent verification means that the reviewing party and the generating party belong to different systems, models, or toolchains, and follow a set of criteria that are determined in advance and can be applied repeatably.
Independent verification still provides a stable baseline when the underlying model changes frequently, ensuring that changes across models and tools are evaluated consistently and preventing quality from fluctuating with tool changes.
All Facts (5)
Acceptance checks are an executable verification method in spec-driven development: each check describes an observable behavior that the builder must make the system actually satisfy in the browser; unlike unit tests, acceptance checks usually start from the user's perspective and cover end-to-end flows across modules, but they only verify behavior that has been written down and cannot find boundaries the spec does not mention.
75%UnverifiedWhen the party writing the code also controls the means of verification, independent external validation becomes a necessity.
50%UnverifiedOrganizations should not rely solely on the same probabilistic system that produced a change to judge whether that change is safe to ship; independent verification is essential.
50%UnverifiedIndependent verification means that the reviewing party and the generating party belong to different systems, models, or toolchains, and follow a set of criteria that are determined in advance and can be applied repeatably.
50%UnverifiedIndependent verification still provides a stable baseline when the underlying model changes frequently, ensuring that changes across models and tools are evaluated consistently and preventing quality from fluctuating with tool changes.
50%