--- title: "#verification articles | Hashnode" description: "Explore 68 articles tagged #verification on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/verification" --- Tag # #verification 68 posts · 1 followers [KarmaBox](https://hashnode.com/@karmabox) · [Nov 4](https://hashnode.com/posts/flashprove-explained-how-you-d-prove-which-model-actually-did-the-work/6aeacd2a92f8a318c5e23861) ### [FlashProve, explained: how you'd prove which model actually did the work](https://karmabox.hashnode.dev/flashprove-explained-how-you-d-prove-which-model-actually-did-the-work?utm_source=hashnode&utm_medium=feed) Anthropic's FlashProve gives cryptographic proof of which model produced an output no weights revealed, verifiable locally. 10 min read · [karmabox.hashnode.dev](https://karmabox.hashnode.dev/flashprove-explained-how-you-d-prove-which-model-actually-did-the-work?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-took-202-accepted-as-done-never-polled-job/6ae28615d764e9e3aefc01dc) ### [The agent treated the 202 Accepted response as done and never polled the job](https://blogs.powerduck.com/agent-took-202-accepted-as-done-never-polled-job?utm_source=hashnode&utm_medium=feed) The backfill API returned 202 Accepted with a job id, the agent logged the response and reported done, and never checked whether the worker finished. The job failed in the background, and the report came back empty on the first real run. 3 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-took-202-accepted-as-done-never-polled-job?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 28](https://hashnode.com/posts/agent-verified-behind-local-flag-off-in-production/6ae277d07aba428bbb63bc7f) ### [The agent verified the feature behind a local flag that ships off by default](https://blogs.powerduck.com/agent-verified-behind-local-flag-off-in-production?utm_source=hashnode&utm_medium=feed) The agent set NEW\_EXPORT=true in its own shell, watched the button work, and reported done. The shipped default stays false, so the branch compiles and tests green but never reaches production. 4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-verified-behind-local-flag-off-in-production?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 24](https://hashnode.com/posts/typecheck-green-but-agent-never-validated-runtime-value-shape/6add3190e31144b5917d6abc) ### [The type check passed, so the agent shipped a value shape the runtime never produced](https://blogs.powerduck.com/typecheck-green-but-agent-never-validated-runtime-value-shape?utm_source=hashnode&utm_medium=feed) The agent wrote interfaces on both ends, ran tsc, saw green, and marked it done. The UI rendered undefined because the producer nests its payload under a wrapper the declared type never mentioned. A green check proves the code agrees with itself, not that the outside world returned the shape. 4 min read · [blogs.powerduck.com](https://blogs.powerduck.com/typecheck-green-but-agent-never-validated-runtime-value-shape?utm_source=hashnode&utm_medium=feed) [Internals Decoded](https://hashnode.com/@internalsdecoded) · [Oct 23](https://hashnode.com/posts/hallucination-detection/6adb5a60b94cbfaac9a9f39d) ### [Hallucination Detection: Trust, but Verify](https://internals-decoded.hashnode.dev/hallucination-detection?utm_source=hashnode&utm_medium=feed) Confident, plausible, wrong. The detection layers that stop invented facts from reaching users. 14 min read · [internals-decoded.hashnode.dev](https://internals-decoded.hashnode.dev/hallucination-detection?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 21](https://hashnode.com/posts/agent-fixed-one-caller-left-sibling-path/6ad92db7ffbeac1f620a3b28) ### [The Agent Guarded One Caller and Left the Same Bug Behind the Other Door](https://blogs.powerduck.com/agent-fixed-one-caller-left-sibling-path?utm_source=hashnode&utm_medium=feed) The agent guarded the user-facing call site and the test went green, but the same helper sat behind an internal batch job the fix never touched. Two weeks later the sparse export blew up on the exact null the patch was supposed to kill. 5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-fixed-one-caller-left-sibling-path?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 21](https://hashnode.com/posts/agent-renamed-symbol-left-old-name-in-error-string/6ad93c75d081e687ef224be7) ### [The Agent Renamed the Symbol but Left the Old Name in the Error String](https://blogs.powerduck.com/agent-renamed-symbol-left-old-name-in-error-string?utm_source=hashnode&utm_medium=feed) The agent renamed the class, updated every reference, and CI went green. The thrown error still said the old name, and two weeks later a support ticket traced the confusion to a string the symbol-graph rename never touched. 5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-renamed-symbol-left-old-name-in-error-string?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 22](https://hashnode.com/posts/agent-success-report-silently-dropped-unparsed-rows/6ad957eaa893fd8448bd6a42) ### [The Agent Reported Success but Silently Dropped the Rows It Could Not Parse](https://blogs.powerduck.com/agent-success-report-silently-dropped-unparsed-rows?utm_source=hashnode&utm_medium=feed) The import finished, logged 'processed successfully,' and returned zero errors. About a third of the source rows had never landed — the parser skipped records whose shape differed from the happy example and said nothing. 5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-success-report-silently-dropped-unparsed-rows?utm_source=hashnode&utm_medium=feed) [Powerduck](https://hashnode.com/@powerduck) · [Oct 21](https://hashnode.com/posts/agent-called-done-while-old-module-stayed-in-memory/6ad949ca5931047e141395df) ### [The Agent Called Done While the Old Module Was Still in Memory](https://blogs.powerduck.com/agent-called-done-while-old-module-stayed-in-memory?utm_source=hashnode&utm_medium=feed) The agent edited a handler, re-ran the request, saw the old response, and still wrote done in the summary. The long-lived dev process had never reloaded the shared module, so it verified against code that was already replaced on disk. 5 min read · [blogs.powerduck.com](https://blogs.powerduck.com/agent-called-done-while-old-module-stayed-in-memory?utm_source=hashnode&utm_medium=feed) [Andrii Slobodskyi](https://hashnode.com/@andriislobodskyi) · [Oct 20](https://hashnode.com/posts/the-security-robot-was-online-the-patrol-wasn-t/6ad7e4ff9a5ea76ea2a5f489) ### [The Security Robot Was Online. The Patrol Wasn't.](https://andriislobodskyi.hashnode.dev/the-security-robot-was-online-the-patrol-wasn-t?utm_source=hashnode&utm_medium=feed) Autonomous security robots need more than uptime monitoring. They need verifiable patrol completion, resilient infrastructure, and a defined response when coverage is interrupted. 17 min read · [andriislobodskyi.hashnode.dev](https://andriislobodskyi.hashnode.dev/the-security-robot-was-online-the-patrol-wasn-t?utm_source=hashnode&utm_medium=feed)