A natural fit for long-lived systems that need predictable protocol contracts. Java SDK

Protocol-native modeling for enterprise and Spring ecosystems.

The Java SDK is designed for execution engines, internal platforms, and integrations that need strong typing, stable models, and explicit versioning.

Back to SDKs Explore CLI

What this page covers

Use records and value objects where possible.

Keep lifecycle transitions explicit.

Separate protocol models from UI or persistence concerns.

Design extensions as additive profiles.

Highlights

Protocol-native entry points for this surface.

Strong models

Represent missions, capabilities, and verification objects with explicit Java types.

See protocol concepts

Immutable history

Events and evidence stay audit-friendly and serialization-ready.

Read conformance

Framework-ready

Well suited for Spring Boot services, orchestration backends, and enterprise APIs.

See cloud

Mission mission = ...;
EvidenceRequirement requirement = ...;
VerificationResult result = verifier.evaluate(mission, requirement);

Working principles

Keep the protocol stable while implementations evolve.

Use records and value objects where possible.

Keep lifecycle transitions explicit.

Separate protocol models from UI or persistence concerns.

Design extensions as additive profiles.

Specification

Use the draft as the source of truth for semantics and compatibility.

Read spec

CLI workflows

See how command-line tooling can operate on the same protocol concepts.

Browse CLI

Next step

Enterprise-friendly by design.

Java implementations often carry critical operational workloads, so the SDK should favor clarity, compatibility, and explicit lifecycle contracts over clever abstractions.