Validate an implementation

Conformance is evidence about a named system under test. Passing the bundled fixtures locally is useful, but is not proof of independent cross-provider interoperability.

Run the release suite

The repository command runs schema validation, positive and negative fixtures, semantic constraints, registries, Portable AI History checks, assertion-row validation, and publication QA.

npm ci
npm run spec:test

from pathlib import Path
import json
from jsonschema import Draft202012Validator

root = Path("specification/ocp-0.4-working-draft")
schema = json.loads((root / "schemas/core/context-request.schema.json").read_text())
instance = json.loads((root / "examples/positive/context-request.json").read_text())

Draft202012Validator.check_schema(schema)
# The release conformance runner also resolves canonical https://opencontinuity.org refs.
print(instance["schema_uri"])

BASHLocal validation

Name the evidence class

Evidence	Supports	Does not prove
Release self-test	The package is internally consistent	An implementation conforms
Named system-under-test run	That build passed declared assertions	A different provider or client passes
Independent adapter/provider/client run	Cross-implementation behavior for tested paths	Universal interoperability
Live human acceptance	The user experience worked in the observed scenario	Normative completeness

Current package results

37 of 37 schemas catalogued
32 positive fixtures pass
45 negative fixtures are rejected
243 semantic checks pass
29 registry checks pass
25 Portable AI History checks pass
134 assertion rows validate
35 publication checks pass

See release status Download conformance data

Was this page useful?

Your response is emailed to the Open Continuity maintainers. No account or email address is required.