# Joule Code v1 Conformance Vectors

The v0.1 conformance suite ([`../../SPEC.md`](../../SPEC.md) §8). Four suites:

| File | Suite | Checks |
|---|---|---|
| [`coding_op_vectors.json`](coding_op_vectors.json) | **C1 — content addressing** | reproduce `op_id` from the canonical CBOR of each `CodingOp` |
| [`signature_vectors.json`](signature_vectors.json) | **C2 — signing** | verify/reproduce each Ed25519 signature; reject every negative |
| [`receipt_vectors.json`](receipt_vectors.json) | **C3 — receipt** | reproduce/verify each receipt signature; honor the provenance↔measured coupling |
| [`cascade_vectors.json`](cascade_vectors.json) | **C4 — cascade** | given scripted stage outcomes, select the same closing tier (stop-at-first-close) |

Run against the reference library:

```bash
cargo run -p joule-code-conformance -- verify .
```

All derived fields are **real, cryptographically computed values** — the content addresses (`op_id`) are BLAKE3 over canonical CBOR, and every signature is a genuine Ed25519 signature, regenerated against `joule-code-rs` (see [`regeneration.md`](regeneration.md)). The `signature_vectors.json` known-answer cases use RFC 8032 keys. The harness passes this pack with no skipped vectors.