Verifier Output Examples

These examples show the shape verifier authors and assistant runtimes should expect. The exact wording may differ, but the compact report and JSON output must come from the same evidence.

For a guide file, Level 4 is the highest score. A level5_ready value means the Level 4 guide is prepared for a separate runtime enforcement check; it is not an achieved Level 5 claim.

Hosted-verifier product telemetry is separate from verifier output. It may record sanitized operational fields such as target host, path category, selected agent category, expected level, achieved level, outcome, failure category, and coarse duration, but those fields are not part of the normative verifier report consumed by an assistant runtime.

Passing Level 3 Compact Report

Verifier: guidecheck-reference-local 0.7.0
Guide: assistant-guide.txt
Level: 3
SHA-256: 65a90dd704b26aa856ff91bc1ebb524829c41546bd78f3b33b1dfa2efedb2b09
Blocking findings: 0
Warnings: 0
Hash pinned: no
Proceed? yes

Local-File Level 4 Evidence Check (caps at Level 3)

The local reference CLI confirms that sidecar manifest and anchor evidence is internally consistent, but it does not fetch that evidence from its real location, so it caps the achieved level at 3 and reports level4.requires-fetch. Level 4 is asserted only by the hosted verifier, which fetches the manifest and anchors.

Verifier: guidecheck-reference-local 0.7.0
Guide: fixtures/valid/level-4/guide.txt
Level: 3
SHA-256: 720c8933dc0684220e8d75a145f84b56591e67f16847a48b626f9de4991acfd1
Blocking findings: 0
Warnings: 0
Hash pinned: no
Proceed? yes

Failing Compact Report

Verifier: guidecheck-reference-local 0.7.0
Guide: fixtures/invalid/missing-verification/guide.txt
Level: 0
SHA-256: 4a0d...
Blocking findings: 1
Warnings: 0
Hash pinned: no
Proceed? no

Machine-Readable Shape

{
  "verifier": {
    "name": "guidecheck-reference-local",
    "version": "0.7.0",
    "verifier_profile": "human-verifiable-assistant-guide-verifier",
    "verifier_profile_version": "0.7.0",
    "guide_profile": "human-verifiable-assistant-guide",
    "guide_profile_version": "0.7.0"
  },
  "input": {
    "evaluation_mode": "local-file",
    "path": "fixtures/valid/level-4/guide.txt",
    "manifest_path": "fixtures/valid/level-4/manifest.txt",
    "anchor_paths": {
      "dns-txt": "fixtures/valid/level-4/anchors/dns-txt.txt"
    }
  },
  "guide": {
    "bytes": 3367,
    "sha256": "720c8933dc0684220e8d75a145f84b56591e67f16847a48b626f9de4991acfd1",
    "achieved_level": 3,
    "level5_ready": false
  },
  "manifest": {
    "hash_match": true,
    "bytes_match": true,
    "valid": true
  },
  "cross_channel_anchors": [
    {
      "channel": "dns-txt",
      "status": "present-matches",
      "observed_sha256": "720c8933dc0684220e8d75a145f84b56591e67f16847a48b626f9de4991acfd1"
    }
  ],
  "summary": {
    "blocking_findings": 0,
    "warnings": 0,
    "infos": 2
  },
  "findings": [
    {
      "id": "metadata.last-reviewed.age",
      "severity": "info",
      "message": "last-reviewed is 3 days old"
    },
    {
      "id": "level4.requires-fetch",
      "severity": "info",
      "message": "Level 4 evidence is internally consistent but was not fetched; local-file mode caps the achieved level at 3"
    }
  ]
}

Hosted Not-a-Guide Response

{
  "outcome": "not-a-guide",
  "input": {
    "evaluation_mode": "public-web",
    "url": "https://example.com/.well-known/assistant-guide.txt",
    "submitted_url": "https://example.com/",
    "auto_resolved": true
  },
  "fetch": {
    "http_status": 200,
    "headers": {
      "content-type": "text/html"
    }
  },
  "message": "The target returned an HTML web page, not a plain-text assistant-guide.txt."
}

Normative output fields are defined in verifier-output.schema.json. Fixture expectations live in the fixture corpus.