Lattice Hub Docs
Guides

Specification

Shared protobuf/gRPC contracts for Lattice Hub across discovery, configuration, governance, security, and MCP.

Specification (lattice-hub/specification) is the cross-component contract layer. It defines messages, gRPC interfaces, and Thin SDK contracts (Sidecar Session / TargetService); it does not run the control plane. pole-control-plane is the primary server implementation. Rust SDK, Thin SDK, Pole Sidecar, Controllers, and protocol adapters consume the same wire contract.

specification protocol map

Role in the product

RoleResponsibility
Specificationapi/v1 protobuf, error codes, Discover/Config request types, governance release enums
Control PlaneServer implementation, storage, cache, auth, multi-protocol entry points
SDK / Sidecar / ControllerClients or data planes that speak the contract

A field existing in the contract does not prove every runtime implements it. Check the target component docs for the capability matrix.

Modules

DirectoryContents
api/v1/modelNamespace, shared types, responses, error codes
api/v1/service_manageServices, instances, clients, contracts, heartbeat, DiscoverGRPC
api/v1/config_manageConfig files and ConfigGRPC
api/v1/traffic_manageRoute, rate limit, lane, lossless, mirror, mock (+ rate-limit gRPC)
api/v1/fault_toleranceCircuit breaker, fault detector
api/v1/securityManagement auth, traffic security, workload credentials
api/v1/aiMCP server/tool model (mcp.proto)

Nine governance release types align with the product: Route, RateLimit, CircuitBreaker, FaultDetect, Lane, Lossless, TrafficSecurity, TrafficMirror, TrafficMock.

Protocol entry points

ContractPurposeDefault control-plane port
DiscoverGRPCRegister/discover instances and pull rules/contracts8091
ConfigGRPCCreate/update/publish/discover configuration8093
WorkloadCredentialServiceIssue/renew workload credentials (separate from admin auth)deployment-defined
MCP protoServer/Tool model; management APIs live on control-plane HTTP8090 / MCP SSE

AI Native boundary

  • mcp.proto defines MCP registration metadata, not an execution engine.
  • A2A appears mainly via auth resource enums; full registry APIs live in the control plane.
  • Do not describe Specification as an agent runtime.

Multi-language consumption

LanguageBuild entryVersion fact
Gocd source/go && bash build.shGo 1.19; module github.com/pole-io/specification
Rustcd source/rust && bash build.shcrate pole-specification 0.1.0
JavaREADME still mentions source/javaNo Java sources in the current repo; do not treat v1.3.0 as a verified release

Root VERSION is 0.1.0. Prefer repository facts over historical README examples.

Further reading

On this page