Independence

Independent AI verification means the check is not the vendor's own model.

When the tool that produced the work also grades it, agreement is the expected outcome. Independence is what turns a second look into a second opinion, and it is a property you can check rather than a claim you have to trust.

Why self-review fails silently

Two models trained on similar material share blind spots, and a review prompt invites agreement. The output looks approving, lists a few cosmetic suggestions, and misses the invented statistic sitting in the second paragraph because the same distribution that produced it would also produce the review.

The failure is quiet. There is no error, no warning and no disagreement to investigate. A team that asked a model to check a model's work gets a document that says it was checked.

Replacing the second model with a deterministic rule engine changes the failure mode entirely: the rules were written before the output existed, and they do not know what the output was trying to say.

What independence requires in practice

Independence is a set of testable properties rather than a stance. If a verification process has them, its agreement means something; if it lacks them, the agreement is decoration.

  • A rule set that exists independently of the work being checked, written down, with severities you can read.
  • Determinism, so the same input produces the same findings and a re-run cannot quietly disagree with the report you shipped.
  • A stated scope, so a pass is evidence about known defect classes and not a general blessing.
  • A human layer with a name attached, drawn from outside the generating pipeline.
  • Separation of interest: nobody earns the result the work needs, and no approval feeds the tool that produced it.

Determinism is the mechanism, not the marketing

A deterministic check can be argued with. Each finding names a rule and the line that triggered it, so a disagreement has a location: the rule is too strict, the pattern is in a test fixture, the severity is wrong for this codebase.

That argument is impossible against a model score, where the number is produced by a process nobody can inspect and may change when the vendor updates a weight. You cannot appeal to a judgement that has no reasons.

Determinism also makes external audit cheap. An auditor can take the text, run the same version, and see the same page, which turns a claim about quality into a reproducible experiment.

The independence of the human layer

A named reviewer is independent when you can see who they are, what they review, what they charge and when they are available, and when they are accountable for the verdict they sign.

That rules out the anonymous pool, the reviewer who exists only as a first name and an avatar, and the marketplace that assigns work behind a curtain. It also rules out a reviewer whose incentive is to approve quickly, which is why the scope and rate are agreed before the file is opened.

The record keeps the reviewer's discipline and the changes they requested, so months later the question who signed this has an answer with a person and a date.

What the two artefacts prove together

The automated report proves the absence of specific known defects, with coverage listed. The human sign-off proves that someone competent in the discipline read the work in context and accepted it.

Alone, each is weak. A green report with no reviewer is a machine saying it found nothing in the places it looked. A review with no automated pass is a specialist spending their hour reading for credentials that a regex finds in a second.

Together they are what a delivery or an audit actually needs: a mechanical baseline and an attributed judgement on top of it.

Where independence stops being useful

Independence does not mean detached from your context. A reviewer who does not know your product, your regulator or your audience will produce a general opinion, and general opinions are cheap.

It also does not mean infallible. A named specialist can miss something, which is why the report keeps the findings, the scope and the version rather than a single badge that says approved.

The realistic goal is a process where every claim has an owner, every finding has a rule, and the places nobody checked are written down rather than assumed away.

How to test an independence claim before you rely on it

Claims of independence are cheap, so test the properties rather than reading the paragraph. Four checks take an afternoon and tell you more than a sales call.

Run the same input twice. A deterministic checker returns the same findings, the same severities and the same score. A model-judged one drifts, and the drift is the tell: if a re-run can disagree with the report you filed, the report was never evidence.

Read one rule end to end. You should be able to see what it matches, why the severity is what it is, and what it will miss. A vendor who cannot show you a rule is asking you to accept a verdict on the strength of their branding.

Ask who signs, and look for a name. A review that resolves to a pool, an avatar and a first name is not an attributed judgement, and it will not survive the first time somebody asks who approved the work. The same question applies to the record: does it keep the reviewer, the scope and the findings, or only a green badge?

Then compare the coverage against your own risk. Independence from the generator is necessary and not sufficient; a rule set that checks nothing you care about is independent and useless.

What this covers

  • Rules before output

    The rule set is written independently of the work it grades.

  • Repeatable verdict

    The same input yields the same findings, so a result can be re-derived later.

  • Attributed signature

    A reviewer with a name, discipline, rate and turnaround signs the judgement.

  • Scope on record

    The report states what ran and what it could not see.

  • No self-approval

    The grader is not the generator, and approval does not feed back into it.

Questions this page usually raises

Isn't a second AI model an independent check?
Only in the narrow sense that it is a different program. Models trained on similar material share blind spots, and a review prompt invites agreement, so the check tends to confirm rather than test.
What makes the rules independent?
They are written down before the work exists, they are applied by code rather than judgement, and each one can be read by anyone who wants to dispute a finding.
How do I know the reviewer is qualified?
Reviewers are listed by discipline, years of experience, region, rate, turnaround and a completed-review count, and the request asks for a specific discipline rather than a general review.
Is a human review required for a passing report?
No. Most work only needs the automated pass. A person is worth the cost where a wrong answer is expensive, public or regulatory.
Can a previous report be re-checked?
Yes. Re-running the same text through the same rules reproduces the findings, which is the practical test of whether a score was evidence or an impression.

Independent AI verification

Run the checks, then decide who has to sign it.

The automated pass is free, needs no account and uploads nothing. Escalate to a named reviewer only where being wrong is expensive.