Judge - AwareXone Docs

Judge is the verification stage after hunters run on candidates from scan / dataflow. It assigns a structured verdict AXguard owns — agents should not “declare vulnerable” without this path.

CLI

axguard verify .
# .findings/axguard/verification.json
# .findings/axguard/verification.md

Soft-run during axguard audit. Diagnostic exit 0.

Verdicts

Status	Meaning
`VERIFIED`	Supported by analysis evidence
`LIKELY`	Strong signal, incomplete proof
`UNVERIFIED`	Insufficient support to claim
`FALSE_POSITIVE`	Counter-evidence / invalid candidate
`REQUIRES_REVIEW`	Needs human or deeper investigation

MCP

axguard_verify_finding — Hunter→Judge style check for one candidate
axguard_verify_fix — after a fix: RESOLVED / STILL_PRESENT / REGRESSED by fingerprint (approval-gated; never resolve on path rename alone)

Pipeline position

app model → dataflow → hunters → Judge → Adversary → Evidence → Attack paths

Slash command: /axguard-verify. Next stage: False Positive Adversary.