Seventeen fields written, zero delivered: why "done" has to come from outside the agent

The mechanism deserves naming precisely, because nothing about it is specific to hiring. The agent wrote values into the fields it could see, then verified by reading those same fields back ^[3]. The values the form actually submits sat elsewhere and stayed empty, so the verification step could not fail as long as the typing worked ^[3]. Seventeen of seventeen fields passed the check and none of them reached the employer, which is a self-check pass rate of 100 percent against a delivery rate of zero ^[15].

That is a test with no failure path, and it is the cheapest kind to write. The developer is blunt about why the defect survives review: the code is simpler, the tests are green, the dashboard fills up, and their own first version shipped with it ^[13]. Reading back your own input is the one operation in an agent that always succeeds.

Which is why the fourth kind of evidence, the on-screen confirmation, matters more than the other three ^[4] and still does not close the question. The same team watched a hiring system return a clean success page while separately recording a refusal, on the same request, for the same posting ^[5]. If the strongest evidence available inside the session can be contradicted by the system that produced it, then every artifact of that session, including screenshots and status codes, is testimony from an interested party. The post's line for this is a receipt the shop wrote for itself ^[9].

The interesting consequence is financial rather than architectural. Because state changes only when an acknowledgement arrives at an address the vendor controls and is matched to a specific application ^[7], the vendor cannot write its own success metric ^[8]. Unconfirmed submissions do not count against the customer's plan, and the author is explicit that this pricing rule can only exist because the confirmation exists ^[10]. You cannot bill against a number your own code produces without also being tempted to produce more of it.

The load-bearing assumption is the one the post asserts fastest: that every applicant tracking system in wide use sends an automated acknowledgement, from its own domain or the vendor's, within seconds to a couple of minutes ^[6]. Everything else rests on that. It also creates an ambiguity the piece does not resolve. Missing acknowledgement after a few minutes is treated as a retryable signal about the submission ^[11], and a listing that never acknowledges anything is treated as information about the employer ^[12]. Both readings come from the same empty inbox. The instrument is honest because someone else writes to it, but it stays coarse until you can say which postings simply do not reply.