Layer 3 of the spec: the AgentSpace tuple space. Ships LocalSpace, a complete single-JVM implementation of the Space API with leases and notifications, plus the delta-CRDT core (OR-Set entry state, LWW lease registers) on which the replicated space grows.

The framework-neutral annotation model and binder: @SpaceTake, @SpaceNotify, and @BidFunction on plain objects, virtual-thread worker loops with crash-equals-lease-lapse semantics, and automatic AgentCards generated from annotations and ...

Layer 4 of the spec: the capability-service runtime (publish, refresh, and discover CapabilityAdvertisements) and the shipped capabilities: push-sum aggregate, vote, the ordered-log (Raft) coordinator behind ORDERED takes, ...

Spring Boot autoconfiguration for AgentSpaces: properties-driven peer, group, and space wiring, a SmartLifecycle for ticking and card refresh, and a bean post-processor that binds annotated agent beans. Compiles against the provided-scope ...

Layer 2 of the spec: the signature-verifying, TTL-evicting advertisement cache fed by gossip, local-first find, and hop-budgeted remote queries.

The open connector SDK behind the AssetCard model (ENTERPRISE §6, COMPETITIVE §7 boundary: the SPI and protocol stay Apache 2 so anyone can build a connector; the finished enterprise connectors and the console are the commercial layer). ...

The fleet console as a served surface: a read-only observability peer presenting membership, discovery, and space state over HTTP. A HAL+JSON API (application/hal+json links, Spring HATEOAS compatible), a Server-Sent Events activity ...

The HTTP bindings of the Transport SPI (spec §5.5, SRAD srad/agentspaces-js.md §3.3): ws and wss (RFC 6455, one binary message per frame, subprotocol aspace.1) and the http and https request and response exchange (appendix C), on Netty's ...

Translates AgentSpaces AgentCards to A2A agent cards and serves them over HTTP, so A2A clients can discover a fleet's agents through one gateway.

The DTLS binding of the Transport SPI (spec §5.5, SRAD srad/dtls-support.md): signed frames over DTLS 1.2 (RFC 6347) on UDP, with Connection ID (RFC 9146), on BouncyCastle's DTLS implementation, and a small recovery sublayer that gives ...

The fleet through LangChain4j's extension points on any JVM host: the fleet's AgentCards as a ToolProvider, discovery and data tools, a take lease renewed per model round-trip and carried across threads, chat memory in a replicated space, ...