@xemahq/kernel-contracts
v24.1.0
Published
Consolidated Xema OS kernel wire contracts — pure types + zod schemas for the kernel protocol surfaces. One package, one npm scope, wildcard per-surface subpath exports. No framework/runtime deps.
Downloads
30,977
Readme
@xemahq/kernel-contracts
Stable wire contracts for Xema kernel surfaces
Overview
This package publishes Xema's framework-independent protocol types and schemas
through stable per-surface entrypoints. It gives services, SDKs, and clients one
source of truth for exchanging validated kernel data without introducing
runtime or domain coupling. The agent-launch entrypoint defines the canonical
tenant-fenced request and authority-narrowing helpers used by every surface that
starts a full Agent; agent-catalog defines the strict, revision-pinned active
Agent discovery projection and cursor query; invocation wraps that launch
request with delivery/output semantics and publishes one durable, pinned
lifecycle record for synchronous, asynchronous and event delivery; model
owns the runtime-neutral model reference vocabulary.
The biome entrypoint owns the v4 xema-biome.json contract. Every manifest
declares stable components[] with a closed kind, portable artifact and wire
protocol, supported host ABI/execution modes, and component-local requirements.
Authors never declare physical ports, pods, runners, credentials, provider
endpoints, or Kubernetes topology. The generated JSON Schema is exported as
@xemahq/kernel-contracts/biome/xema-biome.schema.json; TypeScript types are
inferred from the same Zod source.
When to use it
- Use it when producing or consuming a public Xema kernel protocol surface.
- Import the narrow subpath for the contract domain you need.
Installation
pnpm add @xemahq/kernel-contractsLicense
Apache-2.0 © Xema — xema.dev
