verify

To fact-check claims, you cross-reference specific assertions with source code, documentation, and external resources. The verification process gathers concrete evidence using search and read tools to confirm the statement's factual accuracy.

Code audit claim verification validates statements by searching the codebase and git history. It operates in serial or fan-out modes to handle varying claim loads, providing concrete evidence citations like code snippets and commits for each result.

You validate assertions by running a verification process that searches source code and documentation for matching evidence. It returns concrete citations including code snippets, commits, and URLs that prove or disprove the original claim.

Yes, you can verify multiple claims simultaneously using fan-out verification mode. This mode handles varying claim loads by distributing the evidence gathering process across multiple assertions, rather than processing them sequentially in serial mode.

Yes, fact-checking statements requires tools like Grep, Read, Glob, Bash, WebSearch, and WebFetch for evidence gathering. These tools search the codebase, read files, execute commands, and fetch external documentation to validate claims.

Use automated assertion checking when validating specific factual claims post-audit, such as confirming if a service handles invalid input. It provides concrete evidence citations faster than manual review, especially when processing high claim loads in fan-out mode.