Every automated gate solves the gatekeeper's problem and bills the person being judged. We already ran this experiment on hiring.
A few weeks ago we argued that Anthropic's decision to watermark Claude's output marks the wrong layer. The mark certifies that a machine touched the words, which is about to be true of nearly every professional document, and it cannot certify the thing that actually matters, which is the human judgment behind them. We stand by that. If you want the watermark mechanics, that earlier piece has them.
Then a comment on that post took it somewhere sharper, and it turned out the watermark was never the real subject. It is one instance of a pattern we have all lived through before, in a different room, with a different machine. The pattern is automated gatekeeping, and we already know how it ends, because we ran the experiment on hiring and it went badly.
That is the argument of this piece. The watermark is ATS for writing.
Here is the shape, stripped of the specific technology.
An institution faces more volume than it has judgment to spend. Too many applicants, too many documents, too many submissions to actually read. So it installs an automated proxy to stand in for the judgment it cannot afford to apply at that scale. The proxy is cheap, it runs at volume, and it reads for a surface signal, because a surface signal is the only thing a machine can read without understanding.
The applicant tracking system was the landmark version. Faced with hundreds of resumes per opening, employers bought software to score resumes for keyword matches instead of reading candidates for competence. The proxy had real power over who got seen, but no actual judgment, so people did the rational thing: they learned to feed it. Keyword stuffing. White text hidden behind white background. Resume language reverse-engineered to clear the filter rather than to describe the work. The gaming degraded the signal, so employers layered on more filters, and the arms race settled into a stable, useless equilibrium where the resume that wins is the one best tuned to the machine, not the candidate best suited to the job. The one thing that ever actually worked, a person exercising judgment, is exactly what got automated away in step one.
Now look at the mark with that pattern in hand.
The watermark reads for one surface signal: did a machine touch this text. It cannot read the thing that matters, whether the work is any good and who is accountable for it. By Anthropic's own account the mark cannot even tell "Claude wrote this" from "Claude heavily edited this," because that distinction is not a property of the words. It is a dumb proxy by design, the way a keyword scan is a dumb proxy by design.
The misfire is the same too, and this is where that comment sharpened it. A proposal strategist in architecture and engineering pointed out that her firm's proposals are built on twenty years of their own delivered projects, real histories and proof points sitting in a database. An AI tool retrieves that material and reshapes it into a draft, and the output comes back wearing an "AI involved" tag, as if the origin were the machine. The mark flags the tool and says nothing about the two decades of human work underneath. The provenance reads exactly backwards, the same way an ATS throws out the strong candidate who described their work in plain language instead of the required keywords.
And the arms race has already started. Watermark removers and full-rewrite laundering on one side, stronger detection on the other. We have seen this movie. We know the ending. Everyone spends their energy defeating the filter, the signal trends to zero, and the machine still cannot tell good from bad.
This is the question worth asking every time a gate appears, because the answer is almost never "the people doing the judging."
Hiring managers did not ask for ATS. HR bought it to survive application volume. It solved the employer's cost problem, not the candidate's truth problem, and it solved that problem by pushing the cost onto the candidate, who now has to beat the software before a human ever sees the resume.
The watermark has the same shape with a different buyer. A regulator, the EU with its AI Act transparency rules, asked for a machine-readable signal at continental scale, and the platforms built one because compliance is not optional. That is a legitimate thing for a regulator to want, and the engineering is honest work. But notice what it optimizes for: the gatekeeper's cost and liability problem, a way to satisfy a mandate at scale without paying for judgment. It does not answer whether any given document is good or who stands behind it. And, like the ATS, it externalizes the cost. The writer now has to think about beating or explaining a mark, spending effort on not being filtered instead of on being good.
It is worth being precise about the fear, because part of it is real and part of it dissolves.
The part that dissolves: a mark on your prose does not un-happen your work. Twenty years of delivered projects is a fact about the world, and no watermark reaches back and erases it. A buyer who sees "AI involved" and concludes the expertise is manufactured is confusing who arranged the words with who earned the knowledge, and a buyer who lets a tag override two decades of track record was never really weighing the track record. That is worth knowing early about a buyer, not worth fearing.
The part that is real: the danger is not that a discerning client thinks less of you. It is that a client never reaches your work at all, because the mark becomes a gate applied before any judgment happens. A procurement filter, a committee checkbox, an automated first pass that flags or discards before a human reads a word. That is the ATS failure exactly: not a bad judgment of your work, but no judgment of your work, because a machine screened it out first. And even that, on inspection, is a gatekeeper problem wearing a mark's clothing. A buyer who auto-filters before reading is telling you how they evaluate. The gate did not create that. It just made it visible sooner.
You do not beat an automated gate by building a better mark. You beat it by refusing to let the proxy stand in for the judgment.
For the person being judged, that means owning the work out loud. The watermark, like the ATS, only has power over people who are hiding. Say it plainly and it becomes a non-event: we did this, an AI helped arrange it, the years and the judgment and the accountability are ours. That sentence does everything the mark pretends to do and the one thing it cannot. It names who is responsible. The real signature was never the watermark or the keyword match. It is a named person, with a reputation, willing to stand behind the result and answer for it when it is wrong. You cannot automate someone being willing to sign their name.
For the institution, it means the harder, more expensive thing: build the record that actually carries accountability instead of the flag that dodges it. What was the work grounded in. What did the machine propose that a person threw out. Where did a human catch it being confidently wrong. Whose name is on the output. That is the layer we build for clients, because it is the only version of provenance that survives contact with the pattern. Build it, and the watermark is irrelevant, because you have already answered the only question worth asking. Skip it, and no mark in the world will save you, because you never established who stood behind the result.
This is not a criticism of Anthropic. Marking AI output to satisfy a transparency law is defensible, and the mark has real uses against outright synthetic media. Our point is about what a surface-signal gate can and cannot do once it is loose in the world.
This is not a claim that provenance does not matter. It matters enormously. We are arguing for the real version over the cheap one.
This is not anti-automation. Automation is how small teams do large work, and we build it constantly. The failure is not automating a task. It is automating the judgment and keeping only the gate.
If your team is deciding how to handle AI provenance in your own product or your own work, the useful question is not "how do we detect the machine." It is "how do we prove who is accountable and what the AI was grounded in." That is the layer we build: grounded answers, real guardrails, and a record of who stood behind the output. If that question is open for you right now, we are happy to walk through how we would frame it for your business.
We do not take every engagement, and we will tell you on the call whether we are the right partner.