Verify Checks

Verify is where you see what verification says across the stack. It does not run agents of its own: it collates what the Definition of Done’s agents found on every package in delivery, by concern, by pull request next to your own CI, and finding by finding.

By concern

Every Definition of Done item is counted under one concern — security, accessibility, performance, compliance, tests, documentation or code quality — as met, not met, blocked, stale or pending, with the agents’ findings and any open coding actions. An item counts under the concern set on it in Checklists; otherwise under its agent’s role (the security scanner’s items under security, the test architect’s under tests); otherwise under what its wording says.

By pull request

Each package’s pull request, with its merge hold and the check runs and commit statuses GitHub reports for its head — the first time your own CI sits next to the Definition of Done. CI is read on the server with the repository connection’s read token and kept for a minute. The token needs Checks: Read and Commit statuses: Read; if it lacks one, the page names it rather than showing no CI.

Findings ledger

Every time an agent found an item not met or blocked, newest first, with the package, item, concern, agent and the pull request head it was found on. Superseded findings stay listed and are marked as such, so you can see how an item got to where it is.