Lattice Hub Docs

Concepts and terminology

Shared vocabulary for Lattice Hub resources, release semantics, and AI registries—without treating Namespace as tenancy or A2A as a runtime.

Use this page to align on product language before reading guides or principles. Facts follow the control-plane implementation: a Namespace is an environment, A2A registers capability metadata only, and Pole Agent prepares drafts without publishing.

concepts resource model

Brand and components

TermMeaning
Lattice HubProduct brand for the cloud-native control plane for services and agents.
Pole Control PlaneTechnical product (pole-control-plane) owning APIs, domain servers, cache, storage, and protocol entry points.
ConsolePlatform UI; can run in-process (--mode all) or separately (--mode console).
Pole AgentConversational Console workspace. Reads via allowlisted MCP tools; confirmed config writes become drafts only.
Rust SDKProxyless client that consumes discovery, configuration, and governance views.
Thin SDKMulti-language Sidecar contract clients (Go / Java / Python / Node.js / C++ / C#) via Sidecar Session and TargetService v1—not a full Proxyless governance SDK.
Pole SidecarPingora-based local data plane. Executes routing locally; facts still come from the control plane.
LimiterDistributed rate-limit runtime module in the Control Plane artifact; deploy via limiter-server / full modes instead of listing it as a separate ecosystem component.
Kubernetes ControllerSyncs Kubernetes Services/annotations and can inject the Sidecar.

Environments and identity

TermMeaningNot this
NamespaceRuntime environment boundary (dev/staging/prod). The same logical service has independent content and releases per Namespace.Tenant, team space, or org boundary.
ServiceDirectory entry that hosts instances, rules, and related resources.Not automatically a Kubernetes Service.
InstanceA callable endpoint with address, weight, health, isolation, and metadata.Health failure is not the same as directory deletion.
RevisionFingerprint of a resource view for cache freshness.Not a Git commit.
Service ContractInterface contract for callers.Not a governance rule.

Configuration

TermMeaning
Config GroupGroups configuration files.
Config FileEditable configuration content.
Config ReleaseImmutable published snapshot consumed by clients.
Progressive deliveryShip a release to a subset of clients before full rollout or rollback.
Long-poll / SSEClient watch mechanisms for configuration changes.

Current limits: max content length 20,000 characters; max page size 100.

Governance releases

TermMeaning
Rule objectConsole-managed rule used for create/edit/delete.
Rule ReleaseVersion that can be published, activated, rolled back, or stopped.
Active ReleaseVersion clients, SDKs, xDS, and Sidecars actually read.
Edit vs publishEditing the rule object does not change runtime until publish.

Nine governance families: route, lane, rate limit, circuit breaker, fault detect, lossless lifecycle, traffic security, traffic mirror, traffic mock.

AI Registry

TermMeaningBoundary
MCP RegistryRegisters MCP servers and tools in API, cache, store, and Console.Not a general workflow engine.
A2A Agent RegistryRegisters agent cards, skills, protocol interfaces, and metadata.Not a task proxy or agent runtime.
Pole MCP toolsAllowlisted tools Pole Agent may call.Non-allowlisted tools are unavailable to the agent.
Proposal / draftPreviewed config change saved only as a draft after confirmation.Humans still publish.

Control-plane internals

TermMeaning
API server slotsProtocol plugins under plugin/apiserver/*.
Domain serverShared business semantics (discover, config, goverrule, admin).
Interceptor chainCross-cutting proxies; current order authparamcheck.
CacheManagerLow-latency read views with incremental refresh (lastMtime - 5s overlap).
StoreSource of truth; default MySQL pole_server plus pole_observability.
History / DiscoverEvent / StatisOperation history, discovery events, and statistics plugin chains.
OTel boundaryMetrics/logs via Collector and GreptimeDB—not a full APM product claim.

Access patterns

PatternWhen to use
Console / APIPlatform management and release review.
Rust SDKIn-process proxyless governance.
Thin SDKMulti-language target-envelope contracts for local Pole Sidecar (end-to-end listener still evolving).
Kubernetes ControllerCluster sync and injection.
Pole SidecarLanguage-agnostic local proxy path.
Compatible protocolsExisting Nacos / Apollo / Eureka / Envoy clients.

Suggested reading

  1. Features
  2. Control-plane assembly
  3. Server installation
  4. Using the Console

On this page