Knowledge products that travel with proof.

Three schemas, checked-in evidence, and one offline command. Enough structure for repositories to exchange knowledge artifacts without sharing internals—or pretending to own a universal runtime.

Inspect the release Adoption path

$npm run contract:validatedeterministic · offline · clean-tree

THE RELEASE SURFACE

Small enough to understand. Strict enough to trust.

Read the authority decision →

01Participant

module.v1

Identity, repository, knowledge profile, accepted and emitted schemas, validation, and the exact release claim.

Open contract →02Product

knowledge artifact manifest

One finalized knowledge product with portable payload location, provenance, media type, byte size, and SHA-256 integrity.

Open contract →03Conformance

knowledge profile claim

A machine-readable Profile 1 claim covering public schemas, fixtures, seam discipline, compatibility, and offline validation.

Open contract →

THE PRUNING RULE

Knowledge interoperability is not execution architecture.

Operational pages are preserved as labeled guidance, not silently promoted into the release. Producer-native evidence can be referenced opaquely without importing its lifecycle or shape.

See the documentation authority map →

OUTSIDE V1 AUTHORITYproducer-owned

run lifecycle

run bundles

operational errors

retries & rollback

staging mechanics

MCP schemas

3Draft 2020-12 schemas

85declared invalid cases

2compatibility proofs

1pinned SHA-256 inventory

READY TO INTEGRATE?

Resolve the registry. Pin the release. Validate the artifact.

Start with Profile 1 →Compatibility policy