open-standards/map/conformance/README.md
Transaction Science ba1212361f Add aac, map, sandbox standards; catalog the standards family
Commit the previously-untracked standard directories and catalog them in the
root README alongside proof:

- aac/    — communication cargo class: portable boards + a ten-level
            offline-first cascade (Apache-2.0 code / CC-BY-4.0 spec).
- map/    — geospatial cargo class: range-requestable signed tilesets +
            an F0–F4 fidelity cascade (Apache-2.0 code / CC-BY-4.0 spec).
- sandbox/— isolated, metered, attested execution across the heterogeneous
            compute fabric (Apache-2.0 code / CC-BY-4.0 spec).
- jouleclaw-otel-authz, jouleclaw-trust — new jouleclaw reference crates.

Root README now lists aac, map, sandbox, and proof in the catalog, the tree,
and the contribution guide.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-07 17:04:36 -04:00

26 lines
1.3 KiB
Markdown

# 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.