Java SDK
For enterprise systems, execution engines, and Spring-based implementations.
Open Java
SDKs should make implementation easier without inventing new protocol concepts.
SDKs
Language-native access to the protocol without changing its semantics.
Official SDKs expose the same mission, evidence, event, and verification model using idiomatic language constructs.
What this page covers
Preserve protocol meanings across languages.
Model immutable events cleanly.
Keep extension support explicit and predictable.
Make version negotiation visible to builders.
Highlights
Protocol-native entry points for this surface.
TypeScript SDK
For developer tooling, web products, and event-rich interfaces.
Open TypeScriptPython SDK
For orchestration, research, AI workflows, and automation.
Open Python
SDK design goals
text
Portable mission models
Immutable event payloads
Extension-friendly object graphs
Stable serialization contracts
Working principles
Keep the protocol stable while implementations evolve.
Preserve protocol meanings across languages.
Model immutable events cleanly.
Keep extension support explicit and predictable.
Make version negotiation visible to builders.
Next step
Need a language-specific view?
Each SDK page frames the same protocol through the conventions of its target ecosystem while preserving compatibility with the core model.