Architecture

The distributed consensus design in depth: consensus compared with single-model agents, Toolers and Analysts, the scheduler, the Moot Mesh sidecar, and reminders for crews.

The distributed-consensus design in depth.

  • Consensus vs Single-Model : Compare Kubemoot's committee of small specialist models and a coordinator with a single large-model agent, and what each architecture gains and costs.
  • Agentic Consensus : How a coordinator convenes a subcommittee, why failure is a signal, and how a discussion settles.
  • Tooler-Analyst Architecture : Kubemoot splits discussion work into Toolers that query live systems through MCP and Analysts that reason over their findings with RAG, in separate phases.
  • Reminders and Follow-ups : How a crew sets reminders, follow-ups, and recurring tasks: a Tooler calls scheduling-mcp, records land in NATS KV, and the operator fires them when due.
  • Kubemoot Scheduler : The Kubemoot scheduler matches agents to Model and ModelServer bindings by capability, using labels and CrewSchedulingPolicy rules to filter, score, and bind.
  • The Moot Mesh : The sidecar that sits between an agent's harness and everything else: the bus, the models, the tools, and the trace. What it guarantees, its three doors, and what it does not do yet.
  • The Harness Seam and the Shim : How an external harness such as goose takes a seat at the table through the Moot Mesh sidecar, why a thin shim gives command-line harnesses the A2A face the sidecar calls, and how another harness reuses it.

Kubemoot Architecture - Distributed Consensus vs Single-Model Orchestration

Compare Kubemoot’s committee of small specialist models and a coordinator with a single large-model agent, and what each architecture gains and costs.

Agentic Consensus

How a coordinator convenes a subcommittee, why failure is a signal, and how a discussion settles.

Tooler-Analyst Architecture

Kubemoot splits discussion work into Toolers that query live systems through MCP and Analysts that reason over their findings with RAG, in separate phases.

Scheduling - reminders, follow-ups, recurring

How a crew sets reminders, follow-ups, and recurring tasks: a Tooler calls scheduling-mcp, records land in NATS KV, and the operator fires them when due.

Kubemoot Scheduler

The Kubemoot scheduler matches agents to Model and ModelServer bindings by capability, using labels and CrewSchedulingPolicy rules to filter, score, and bind.

The Moot Mesh

The sidecar that sits between an agent’s harness and everything else: the bus, the models, the tools, and the trace. What it guarantees, its three doors, and what it does not do yet.

The Harness Seam and the Shim

How an external harness such as goose takes a seat at the table through the Moot Mesh sidecar, why a thin shim gives command-line harnesses the A2A face the sidecar calls, and how another harness reuses it.