Skip to content

Conformance

Three conformance classes. Each class includes everything above it.

Software that checks SP/1 evidence. MUST:

  • Implement canonical JSON and reproduce its test vector byte-for-byte.
  • Recompute and match both fingerprint test vectors.
  • Verify audit-chain slices, including the genesis rule, and reproduce the chain test vectors.
  • Verify anchor inclusion and consistency proofs locally against a pinned public key — never by asking the ledger to attest to itself.

Class V needs no account and no relationship with any hub. An auditor’s toolkit is a Class V implementation.

Software integrating on the recipient side. MUST additionally:

  • Request grants only through the authorization flow (PKCE S256, single-use codes) with registry-listed fields, a purpose, and a finite duration.
  • Stop using values on expired / revoked / ceased and process events idempotently with signature verification.
  • Acknowledge cease-contact notices within the obligation window.
  • Honor the embed contract on any page-level capture, including fail-open.

An operator implementing the full protocol. MUST additionally:

  • Enforce origin verification for grants and certificate capture.
  • Maintain the append-only audit chain with serialized appends and storage-level append-only protection.
  • Keep all PII out of audit rows, anchor payloads, and public verification surfaces (masked subject only).
  • Provide public certificate verification (JSON + human page) with anchor receipts.
  • Anchor per-event and checkpoint the chain head on a fixed cadence, with pinned-key local proof verification, and surface consistency failures as first-class audit events.
  • Capture policy snapshots at issuance, content-hash-deduplicated.
  • Run the cease-obligation clock (10 business days) with escalation records.
  • Encrypt subject values with per-record keys (envelope encryption) bound to the record id via AAD.

State the class and spec version: “SP/1 Class V verifier”, “implements SP/1 (Class H)”. The test vectors in this specification are normative; a claim that fails a vector is false. A public conformance test-suite repository is planned — see governance.