The verification layer for AI output

AI doesn't have to hallucinate
to get it wrong.

Plumb compares what entered an AI step with what came out. One summary you pasted in, or the third step of an automated workflow. It shows whether the claims, people, quantities, certainty, conditions, timing, attribution, and relationships still hold together the same way.

Simple to add Independent of the model One output or an entire workflow
Scroll

Know what the transformation actually did.

Most AI tools help produce the output.
Plumb takes the transformation apart.

After any AI step, send Plumb two things:

  • 01 what went into the step
  • 02 what came out

Plumb reconstructs the claims on both sides and shows where their meaning still corresponds and where it moved.

Not just whether words changed.
Whether the message changed.

Meaning can move without looking wrong.

An AI output can be polished, plausible, and factually familiar while still changing what the source said.

A possibility can become a commitment.
A condition can disappear.
A number can attach to the wrong action.
An attributed claim can become a direct assertion.
A sequence can become a cause.
A limited conclusion can become a general one.

Each output may still read cleanly. Plumb makes those changes visible before they become the basis for another action.

What Plumb examines.

The claims

What was preserved, introduced, removed, combined, or split apart.

Who and what are involved

The people, organizations, objects, and groups participating in each claim, including who acted and what was affected.

The force of the statement

Negation, possibility, obligation, qualification, conditions, exceptions, and the scope they apply to.

The concrete details

Quantities, dates, durations, comparisons, states, and the other specifics a decision turns on.

The relationships

Cause, consequence, contrast, sequence, purpose, attribution, and the direction between related claims.

The framing

What was emphasized, narrowed, generalized, softened, strengthened, or presented with a different level of specificity when the evidence supports that determination.

Plumb keeps unresolved or ambiguous evidence visible rather than quietly guessing.

One call after any step you already run.

01

What went in

Take what entered an AI step.

02

What came out

Take what the step produced.

03

Both sides decomposed

Plumb turns each side into comparable claim structures.

04

The comparison

It shows where those structures correspond, differ, conflict, or cannot yet be resolved.

Plumb does not rewrite the output.
It does not decide whether the source is realistic.
It does not rely on surface similarity to declare the meaning preserved.
It gives you an independent account of what the step did.

No single step looks wrong. The distance still adds up.

Most real AI work runs longer than one step. Source material becomes an extraction. The extraction becomes an analysis. The analysis becomes a recommendation. The recommendation becomes an action.

Meaning can move a little at each step. By the end, the version being acted on may be materially different from the source even though no individual output looked obviously broken.

OriginSource material
Plumb
compares
Step 1Extraction
Plumb
compares
Step 2Analysis
Plumb
compares
Step 3Recommendation
Plumb compares every step against the one before it, and the final output against where it started. You see where the movement began, what changed afterward, and whether the final result still has support.

A traceable account of the transformation.

Not a similarity score. Not a spellcheck report. Not a generic list of possible errors.

Which claims still correspond.
What changed inside those claims.
What no longer has a counterpart.
What appeared without source support.
Which differences are structurally clear.
Which conclusions remain ambiguous or unsupported.

Enough to decide whether the output is ready to move forward, or needs review first.

Built to sit outside the model.

Plumb does not require you to replace the model, prompt, agent, or workflow you already use. Place it after the steps that matter. Run it on one transformation. Run it on every transformation. Or run it on the final result against the source you started with.

What it sees

Only what you send it for a step: what went in, and what came out. Not your systems, databases, or prompts.

Where it sits

Outside how the output gets made. It reads after the fact and never changes how your workflow runs.

What it returns

The account of that transformation, and nothing else. Your material stays yours.

The workflow stays yours.
Plumb makes its effect on meaning visible.

See what each step actually did.

15 minutes. We run Plumb on a real output, yours or one of ours, and show you the transformation. No deck. No pitch. Just the layer working.

See it on your own work 15 min · No commitment · See it work first