The Verification Engine

The verification engine is the core product boundary shared by the CLI (agentic-go verify), GitHub Action, and MCP server (go_verify_change).

CLI Usage

Terminal 
$ agentic-go verify --base origin/main --package ./... --format text

Exit Codes

  • 0 (Pass): All requested packages compiled, tests passed without regressions, and no policy-blocking findings were introduced.
  • 1 (Policy Findings): Tests passed or were evaluated, but policy checks detected blocking findings (concurrency bugs, unhandled errors, scope drift).
  • 2 (Incomplete / Error): Compilation failure, unhandled runtime exception, or execution timeout prevented complete evaluation.

Verification Pipeline Stages

  1. Snapshot & Impact Analysis: Computes the diff against --base, identifies modified declarations, and resolves all downstream impacted packages.
  2. Whole-Package Testing: Executes full package test suites without cherry-picking individual methods.
  3. Changed-Statement Coverage: Tracks coverage specifically across statements touched in the diff.
  4. Calibrated Static Analyzers: Concurrency and error analyzers run with a 0% false positive target.
  5. Uncertainty Calibration: Explicitly reports unexercised branches, skipped suites, and environment constraints.
Previous: MCP Client Setup Next: Safety & Containment