# Map conformance

An implementation is **conformant** if it round-trips the published wire vectors
in [`v1/`](v1/). The reference harness is `map-conformance` in
[`../map-rs/`](../map-rs/):

```
cargo run -p map-conformance --bin map-conformance   # run the suites (exit 1 on any FAIL)
cargo run -p map-conformance --bin gen-vectors        # regenerate v1/*.json
```

## Suites (SPEC §8)

| Suite  | Covers |
|--------|--------|
| **C1** | Cell-key canonical CBOR + content id; the time axis distinguishes otherwise-equal cells. |
| **C2** | Directory is Hilbert-sorted; the range planner coalesces a viewport; payload hashes verify. |
| **C3** | Manifest signs/verifies; the revision chain validates back to a trusted root. |
| **C4** | The cascade closes at the highest tier ≤ the request and falls back to the F1 floor. |
| **C5** | JCR-1 receipts seal, verify, reject the wrong steward, and enforce the provenance coupling. |
| **C-neg** | Tampered manifest root, unendorsed revision, dishonest receipt, unsorted directory — all rejected. |

Vectors are deterministic (fixed Ed25519 test keys), so `gen-vectors` produces
byte-identical files and a third-party implementation in any language certifies
by reproducing them. Receipt vectors are byte-compatible with the family's
existing JCR-1 verifiers.