# KNOBE Protocol v1 — Interpretation Set

Six additional `.knobe.md` files pinning the documented interpretations in [ERRATA.md](../../ERRATA.md): places where an implementer building from the specification text alone reported a genuine ambiguity, and the steward has ruled which reading is authoritative. These are **not** part of the canonical-compatibility bar (an implementation is canonically compatible if it reproduces the nine core results in the parent directory), but a verifier that matches the reference on all six is following the published rulings, and each ruling cites its vector here.

Every expected result below was produced by both reference implementations (`lens.py` and `knobe-core.js`) in agreement before publication. Verify each from the repository root with:

```
python3 lens.py test-vectors/interpretation/<file>
```

## Expected results

| file | expected status | body_verified | conformance | ruling it pins |
|------|----------------|---------------|-------------|----------------|
| `boolean-null-values.knobe.md` | verified | omitted | valid | `true`, `false`, and `null` are lawful scalar values; the numeric restriction of spec §5 applies to numbers only ([E6](../../ERRATA.md)) |
| `spec-version-frontmatter-mismatch.knobe.md` | verified | omitted | warnings | frontmatter `spec_version` disagreeing with the sealed payload is a warning; the sealed value is authoritative. Issue text: `frontmatter spec_version '1.1' does not match sealed payload spec_version '1.0'` ([E5](../../ERRATA.md)) |
| `begin-marker-mid-line.knobe.md` | verified | yes | valid | payload markers are line-anchored; marker text mid-line is ordinary body content, covered by the sealed `body_hash` ([E2](../../ERRATA.md)) |
| `base64-unpadded.knobe.md` | unreadable | — | invalid | RFC 4648 §4 padding is required; a payload block whose trailing `=` characters are missing cannot be decoded and the file is unreadable ([E7](../../ERRATA.md)) |
| `attribution-missing.knobe.md` | verified | omitted | invalid | a wholly absent `attribution` reports exactly one issue (`required field missing: attribution`), not a cascade into `attribution.sources` ([E9](../../ERRATA.md)) |
| `astral-unicode-literal.knobe.md` | verified | omitted | valid | code points above U+FFFF serialize as literal UTF-8 in the canonical form, never as `\uXXXX` escape pairs ([E8](../../ERRATA.md)) |

A `—` in the body_verified column is the mandated `omitted` of spec §7 for unreadable files, which machine output may spell as the string `omitted` or as JSON `null`; either spelling is conforming (see [E11](../../ERRATA.md)).

KNOBE Protocol v1 · Test vectors: [CC0-1.0](../LICENSE) (public domain, no attribution required) · David Kyle (UC Davis)