AER-1 corpus vectors / Test vectors: invalid

non-utf8-bytes

Family: Test vectors: invalid. Source: base/test-vectors/invalid/non-utf8-bytes.json in the AER-1 corpus published at zambo.dev/aer1/corpus.json (kit 1.5.7, draft-zambo-aer1-26), file SHA-256 de44cf86810753d96eacbc20b07693f27759661921da1f3d6233fbbed31d57dd. Receipt id recorded in the vector: b6c63ac5-f324-4fa7-ad58-c4bf83faa86a.

Input

The vector input, exactly as published in the corpus:

{
  "id": "b6c63ac5-f324-4fa7-ad58-c4bf83faa86a",
  "receipt_schema_version": "0.3",
  "created_at": "2026-09-27T09:00:00.000Z",
  "tool": {
    "name": "live_price",
    "version": "4.0.0",
    "scope": "public"
  },
  "provenance_class": "EXECUTED BY ZAMBO",
  "canonical_bytes": "/w==",
  "output_hash": "sha256:a8100ae6aa1940d0b663bb31cd466142ebbdbd5187131b92d93818987832eb89",
  "verification_status": "verified",
  "rejected_by": "canonical_bytes is not valid UTF-8"
}

Expected result

• expected verdict (corpus path): invalid: the receipt must fail
• rejected_by: canonical_bytes is not valid UTF-8

Checks it exercises

Try Zambo free: add Zambo to your AI to run this kind of check on your own agent work, with 20 free calls per day and a Day Pass at $0.99 for 24h when you need more. Every call returns a verifiable receipt, and a receipt proves the saved result was not changed.

See the full set in the AER-1 corpus vectors index and the AER-1 corpus checks index, or read the standard itself: draft-zambo-aer1-26.