# Joule Code Conformance

A Joule Code implementation is **conformant at v0.1** if it round-trips the wire vectors in [`v1/`](v1/). The vectors — not any brand — define what is correct ([`../CHARTER.md`](../CHARTER.md) sense).

- [`v1/`](v1/) — the v0.1 vector pack (suites C1–C5, [`../SPEC.md`](../SPEC.md) §8). C5 (`gated_cascade_vectors.json`) applies only to implementations claiming the optional §5.1 JCP binding; its fixture identities (issuer `[1;32]`, agent `[2;32]`, steward `[7;32]` / `did:example:joule-code`, resource `b"repo:joule-code"`, request `{"tree-hash", "rename the function"}`) and per-tier µJ costs (1 / 10 / 10³ / 10⁶ / 10⁷) are fixed so runs are deterministic end to end.
- [`VERSIONS.md`](VERSIONS.md) — vector-pack ↔ spec-version matrix and compatibility rules.

Each pack is canonical for exactly one spec major version. Historical packs are never removed: an implementation pinned to an older spec version must be able to look up that version's pack indefinitely.

Reference implementations are conformant by construction. Third-party implementations certify themselves by running the public suite (`cargo run -p joule-code-conformance -- verify conformance/v1`).