@4d-id/conformance

Run the 4D-ID conformance checks against any resolver endpoint. This is a diagnostic tool, not a certification or adoption badge: the current status is exactly 15 schema-level checks passing, while functional work continues.

npx @4d-id/conformance https://resolver.example.org

What it does

It exercises a running resolver's access operations and checks the specification's semantics: that identifiers match the canonical grammar, that emitted records validate against the JSON Schemas, that the context envelope is bounded and carries no raw geometry, that snapshots and watch behave, and more. It prints a per-test report and a profile-level verdict.

4D-ID conformance 2.3  ·  https://resolver.example.org

  PASS /conf/query/operations       resolve returned a valid 4D-ID with a snapshot
  PASS /conf/core/uri-form          identifier matches the canonical grammar
  PASS /conf/core/state-fields      state validates against the schema
  PASS /conf/core/timestamps        source and publish times present
  PASS /conf/core/genesis-anchor    entity resolves; identifier is opaque and stable
  PASS /conf/query/context-envelope envelope validates, bounded, snapshot-tagged, no raw geometry
  PASS /conf/scale/snapshot         snapshot carries an id and zone generations
  PASS /conf/scale/list-then-watch  watch returns a change list

  P1 Core checks: all implemented core checks pass
  Overall: all executed tests passed
  Coverage: 9 of 107 manifest tests executed

Honest coverage

The endpoint CLI currently executes 9 of 107 manifest tests against a running resolver and reports the rest as not run. Separately, the reference implementation's data runner has 15 schema-level checks passing. Functional conformance work continues across writable lifecycle operations, partition behaviour, propagation, and security. Neither result is a certification or a claim of full specification conformance.

Options

4did-conformance <base-url> [--sample=registry:external_id] [--json]

• --sample=registry:external_id — the external identifier to resolve for the run (default asset.register:TB-WH-01, the reference sample). Point it at an identifier your endpoint actually has.
• --json — machine-readable report, for CI.

Exit code is non-zero if any executed test failed, so it drops into a pipeline.

In CI

- run: npx @4d-id/conformance https://staging.myresolver.example --json

License

Apache-2.0. The test manifest is defined by the candidate 4D-ID specification.