The failure you would never have found

One page from a supplier document. One architecture diagram. Watch what a standard pipeline does with it — and note that nothing anywhere reports a problem.

This is not a hypothetical built to make a point. It is a real failure mode from a production document pipeline, found after it had already been shipping damaged evidence for months. The document below is fictional; the failure is not.

The page · fictional supplier response pack, page 72

two engines, same page

Standard pipeline text-OCR first

Press run.

idle

Routed pipeline page classified first

Press run.

idle

Look at what the left-hand validator actually measured. It counted characters. The mangled diagram produced plenty of them — more than the text layer — so recall looked healthy and the page passed. The glyphs in red are what a character counter cannot see.

Now the part that costs you. That page was the evidence for the controls covering network segregation, encryption in transit, and privileged access. An assessment built on the left-hand output reports them as satisfied, because the words it needed were technically present somewhere in the noise. Nobody is lying. Nobody is careless. The report is confident, complete, well formatted — and wrong in a way that surfaces the day an auditor opens page 72 for themselves.

The fix is not a better threshold. It is refusing to let a page reach an engine that cannot read it: detect the embedded raster up front, route it to a vision model, and validate by looking for garble rather than by counting. Even then the right-hand pane does not claim the backup encryption is missing — the diagram simply does not state it, so that becomes a gap for a human rather than a finding.

This is one failure of a class that all share a property: they do not announce themselves. A model silently resolving to a fraction of its context window. A control that was never assessed looking identical to one that passed. A version number read from template debris in a footer. Nothing errors. Everything looks fine.

This is a demonstration of the platform. The practice that designs, builds and hands it over lives on cplt.tech.

Back to cplt.tech ↗