kb-interop.v1-rc1
kb-interop.v1-rc1 is the current immutable release candidate for knowledge-artifact interoperability. It is assembled for authority review; it is not a final release.
Consume it directly
| Purpose | Repository-relative artifact |
|---|---|
| Bootstrap registry | contracts/registry.json |
| Module descriptor | contracts/schemas/module.v1.schema.json |
| Knowledge artifact manifest | contracts/schemas/knowledge_artifact_manifest.v1.schema.json |
| Profile 1 claim | contracts/schemas/knowledge_profile_claim.v1.schema.json |
| Stable-reference vectors | contracts/test_vectors/stable_references.v1.json |
| Release inventory | contracts/releases/kb_interop_release.v1-rc1.json |
| Migration guidance | contracts/migrations/v1-rc1.md |
These links are for human browsing. Automated consumers should resolve repository-relative paths from contracts/registry.json, pin the release manifest's source_commit, and verify its SHA-256 inventory.
One golden path
npm ci
npm run contract:validate
The validator makes no network calls. It validates the registry, schemas, every valid and invalid fixture, compatibility cases, stable-reference vectors, release cross-references, exact-byte hashes, and the pinned source commit. It also verifies that validation leaves the working tree unchanged.
Release contents
The release contains only:
kb.module@1.0kb.knowledge_artifact_manifest@1.0kb.knowledge_profile_claim@1.0- Knowledge Interoperability Profile 1
- checked-in conformance and compatibility examples
- stable-reference preservation vectors
- migration guidance and release integrity metadata
It contains no run-record, run-bundle, operational-error, lifecycle, promotion, runtime-library, or MCP schema.
Known adoption gap: producer-owned schemas
RC1 resolves Profile 1 public_schemas through the KB Contracts registry. It does not yet provide a standard declaration that pins a producer-owned schema by repository, source commit, repository-relative path, and exact-byte SHA-256.
The recommended next-RC design is documented in Producer-owned, independently verifiable schemas. Until that protocol is approved and released, producers retain their schema authority and should not copy domain schemas into KB Contracts or force a KB-owned binding merely to satisfy RC1.
Reading precedence
- The pinned release manifest and its checksum inventory.
- Registered JSON Schemas and fixtures.
- ADR-0006 and the compatibility policy.
- Focused explanatory documentation.
- Legacy or candidate operational pages, only within their classification banner.