Developers / Protocols
Integrate without taking over mission state
Every integration surface — agent, model, tool, or client — talks to the Kernel through a versioned protocol. None of them are permitted to hold a second copy of mission truth.
Protocol definitions below reflect target and in-progress contracts. Maturity is stated per protocol; none are frozen 1.0 specifications yet.
Five integration modes
Choose the mode that matches what you are building. A single integration can combine more than one mode.
Worker
Execute leased units of work under Kernel-issued scoped authority.
Provider
Supply a model or inference route the Kernel can select during capability negotiation.
Tool/context
Expose a tool or context source the Kernel can call during context assembly or execution.
Client
Present mission state and submit commands without holding authoritative state (Studio, CLI, custom UIs).
Mission Pack
Package a domain-specific capability bundle with its own versioned contract.
Protocol inventory
Each protocol has its own maturity. None are combined into a single "integration API" claim.
| Protocol | Purpose | Maturity |
|---|---|---|
| ACP | Agent Communication Protocol: how an agent negotiates capability and receives mission events from the Kernel. | development |
| MCP boundary | Defines where Model Context Protocol tool calls are accepted and how their effects are scoped. | development |
| LSP/IDE | Editor-surface integration for code-proximity workflows. | research |
| Telemetry | Structured event emission for observability without exposing raw mission state. | development |
| MMP | Mission Manifest Protocol: the versioned schema for plans, checkpoints, and evidence records. | development |
| Proof format | The structured evidence/proof object schema referenced on the Evidence page. | development |
Conformance workflow
A Mission Pack or integration is validated against its declared protocol version through a conformance test suite before it can be registered. This workflow is part of the target architecture; the public conformance program is not yet available.
- No non-functional code snippet is published; every published snippet is expected to run in CI against a versioned contract.
- SDK language coverage beyond the reference implementation is on the roadmap, not currently shipped.
- Protocol version numbers are pre-1.0 and may change with notice as the architecture stabilizes.
Talk to the architecture team
A technical briefing is the fastest way to get protocol-level detail matched to your integration.