812 words
4 minutes

10 from AI Reviews That Read Nothing — Thirty-Four Verdicts in a Hundred

The read receipt: no AI verdict without the source it read

By Docker Captain · CNCF Ambassador · IBM Champion
Blank cyan-lit monolith, an AI review that read nothing

The model was the most reliable part of that pipeline. It read what it was handed and said what it could not read. Everything that failed happened before the prompt and after the response.

That is ordinary software, and it is tested like ordinary software: the lookup that picks the document, the envelope nobody opened, and the authority the verdict is given.

  1. 1

    Prove the source before the prompt

    A mapping from an image to a repository is accepted only when the version the fleet pins exists as a tag in that repository. Take the address from the image's own source label where there is one and from a table where there is not, and run the check on every address on a schedule. The label is the publisher's claim; the tag is the proof.

  2. 2

    Make the lookup able to say no

    Its test plants a repository that does not exist and requires “absent” back, not an error and not an answer. “This publisher keeps its notes elsewhere” is a third answer, kept in a short table with the reason beside each entry.

  3. 3

    Name a missing source in a field, not in the last paragraph

    No source, no verdict. A review that could not read the notes says so where the verdict would be.

  4. 4

    Open the envelope before using the answer

    Check how generation stopped, treat a response with no text blocks as a failure rather than an empty answer, and put the token counts in the error.

  5. 5

    Hand the model facts, and let them win

    The registry's image configurations sit beside the release notes, so a renamed user is read from the image, not guessed from a sentence.

  6. 6

    Bound what the verdict can do

    A verdict can slow a change down and never wave one through. Inside a major version a bump proceeds on the CI-gated path; DO NOT APPLY UNATTENDED reroutes it to a prepared branch for a person; a review that cannot run leaves the CI gate alone in charge. Owner: platform engineer.

The failure modes, by what the reviewer was holding

What it was holdingWhat it looks likeWhat settles it
NothingA verdict on an upgrade nobody readProve the source before the prompt
The wrong projectConfident notes about somebody else's softwareThe pinned version must exist as a tag under that name
A blankA clean report with nothing in itRaise on zero text blocks, with the token counts
A descriptionNEEDS ATTENTION on a renameGive the model the image configuration, and let it win
A third of the fleetA smaller fleet, published as the wholeRead everything before writing anything
Another workflow's answerGood changes revertedJudge a change only by the workflow that verifies it; skipped is not red

What shows it works

Three findings with the rules they produced, and the code that enforces them.

A reviewer that cannot show what it read is a fluent guess.

The long version is the post AI Reviews That Read Nothing. Anthropic, Messages API reference (stop reasons); OCI Image Format Specification, Annotations (the standard source label); OWASP, Top 10 for LLM Applications 2025, Misinformation; ISMS.online on SOC 2 CC8.1 and ISO 27001 8.32.


Vladimir Mikhalev

Docker CaptainCNCF AmbassadorIBM Champion

The Verdict — production-tested analysis on YouTube.

The Verdict

Inconvenient truths about shipping in the AI era

Container security, platform engineering, and the agentic shift — tested in production, argued without the hype. The verdict reaches your inbox the moment there's one worth sending.

Related Posts

Same category
  1. 1
    AI Reviews That Read Nothing — Thirty-Four Verdicts in a Hundred
    AI & MLOps · A third of the images my fleet pins would have had their next AI review written against nothing. How to prove what an AI review read before anyone acts on it.
  2. 2
    AI-BOM at Admission — The Cluster Refused a Signed Model for Its Licence
    AI & MLOps · An AI-BOM read at admission. Everything crosses the air gap as one signed file, and a signed model is refused for its licence. CycloneDX, Kyverno, cosign.
  3. 3
    Prompt Injection Evals — Six Models, One Boundary, Nothing Left the Company
    AI & MLOps · Prompt injection evals on six small models. They acted on hidden instructions from never to half the time, and zero data left. Gate the boundary.
  4. 4
    AI Agent Governance — One Engineer, Over a Hundred Repositories and the Decisions No Agent Makes
    AI & MLOps · AI agent governance for one engineer and 100+ repositories. What the agents decide, what they never do, and the documented auto-merge that merges red checks.

More Blueprints

All 12
  1. 11
    The apply gate
    Signal, 11 June 2026 · Keep the Terraform MCP server's operations flag off, pin what it can reach, gate every agent-reachable workspace with policy, and keep the approval and its record with a person.
  2. 12
    The evidence join
    Signal, 11 August 2026 · Bind each agent to its governance use case, give every run a span with the same id, keep the spans for the longest obligation, and alert when a run has no evidence to match.
  3. 01
    The blast radius assessment
    Signal, 23 February 2026 · Map what an AI agent can break, and how fast a person can undo it, before it gets a single key: six steps, a worksheet and the repositories that measure the same rules.
  4. 02
    The AI intake gate
    Signal, 12 March 2026 · Find every AI tool in use, ask for its backend's access rules instead of a questionnaire, and block what cannot use SSO and central logging, before the first prompt.
The read receipt: no AI verdict without the source it read
https://heyvaldemar.com/blueprints/read-receipt/
Author
Vladimir Mikhalev
Published
2026-11-14
License
CC BY-NC-SA 4.0