Crate reference

Every crate in the apomesh workspace, grouped by the layer it belongs to. Each role line is the crate’s own one-sentence self-description (its //! module doc). A crate with a full reference page is linked; the rest are named here and documented as the coverage backlog is worked down.

The layering runs bottom-up: the wire protocol is the leaf nothing depends backward on, the substrate core and its implementation planes sit above it, the orchestrator and worker drive sessions, and the transports, verticals, and UI compose the whole. See Control & execution planes for the narrative.

Wire / protocol

Crate	Role
apomesh-protocol	The wire protocol — prost-generated protobuf types only.

Substrate core

Crate	Role
apomesh-substrate-types	The substrate type vocabulary and port traits — the stable, most-depended-on foundation.
apomesh-substrate	The substrate domain library — functions take domain types and return domain types.

Substrate implementation planes

Crate	Role
apomesh-substrate-catalog	The agent-definition plane — the Fleet-definition machinery (agent catalog, prompt-composition seam, skill registry).
apomesh-substrate-llm	The LLM and embedding provider implementation plane — the concrete provider impls behind the ports.
apomesh-substrate-mcp	The MCP tool-transport plane — external MCP servers projected behind the substrate Tool port.
apomesh-substrate-net	The shared HTTP egress primitive — the webpki-roots reqwest client the impl planes compose.
apomesh-substrate-sandbox	The tool-sandbox implementation plane — the per-platform adapters and runner-subprocess machinery.
apomesh-substrate-state	The state implementation plane — the in-memory and SQLite StateStore adapters.
apomesh-substrate-tools	The leaf-capability tool plane — web, file-ops, git, and shell tools plus the predicate evaluator.

Orchestrator

Crate	Role
apomesh-orchestrator	The control-plane gRPC daemon library.
apomesh-orchestrator-bin	The orchestrator daemon binary — wires the registry with the concrete strategies.

Worker / tool execution

Crate	Role
apomesh-worker	The worker — the execution endpoint binary and its library surface.
apomesh-tool-runner	The sandboxed tool-dispatch entry point, spawned inside the OS sandbox to run one tool invocation.

State stores

Crate	Role
apomesh-state-store-postgres	The production StateStore adapter — Postgres durable persistence, event log, snapshots, and episodic memory.
apomesh-state-store-redis	The Redis cache primitive for the production StateStore stack.
apomesh-state-store-smartchat-postgres	The Postgres adapter for SmartChat’s SmartChatStore.

Transports and applications

Crate	Role
apomesh-rest-api	The REST/JSON external API surface — the human-facing parallel to the gRPC wire.
apomesh-smartchat	SmartChat — an operator-facing chat layer built on substrate primitives.

Auth, config, and support

Crate	Role
apomesh-auth-providers	Configurable SessionAuth and WorkerAuth backends — OAuth 2.0 / OIDC, pre-shared API keys, and mTLS.
apomesh-config	The apomesh daemon configuration surface.

Tooling

Crate	Role
apomesh-bump	The workspace version-bump tool.
apomesh-reseal	The operator entrypoint for a sealing-key rotation.
cassette-refresh	The cassette format and drift-detection engine for recorded LLM provider interactions.

Verticals

Crate	Role
apomesh-vertical-coding-assistant	The Coding-Assistant use-case — LSP, tree-sitter, and coding-typed tools plugged into the substrate.
apomesh-vertical-deep-research	The Deep-Research use-case — a SessionStrategy specializing the loop for verified-citation reports.
apomesh-vertical-deep-research-projection	Deep-research’s dependency-light tier-4 open-vocabulary consumer surfaces — the coverage-audit ExtensionHandler and the sandboxed coverage-schema verification unit.

UI

Crate	Role
apomesh-control-plane	The desktop operator app — submit, observe, and cancel sessions against an orchestrator’s gRPC service.

Samples

Crate	Role
apomesh-sample-tail-consumer-prometheus	A reference tail-consumer sample — the substrate event bus projected to Prometheus.