Crate Layout

Crates

Crate	Responsibility
orbit-cli	Clap-based entrypoint that composes Core, Registry, MCP, and Web.
orbit-cmd	CLI-facing command layer extracted from orbit-core: doctor, migrate, diagnostics, hooks, agent-rules, direct v2 activity runs. Exposes *Commands extension traits over OrbitRuntime.
orbit-core	Neutral runtime bootstrap, config layering, default asset seeding, and runtime-integrated command modules. Surfaces OrbitRuntime to orbit-cmd, orbit-cli, and orbit-web.
orbit-registry	Local machine identity and logical workspace catalog validation with atomic file persistence.
orbit-web	HTTP API, embedded dashboard UI, dashboard mutations, and SSH web connection over Core and Registry.
orbit-engine	Activity and job execution, template rendering, retry logic. Owns the CLI agent subprocess runner, which references orbit-agent::{Agent, AgentConfig} directly.
orbit-agent	Per-provider AgentRuntime implementations under providers/<name>/<name>_runtime.rs (claude, codex, gemini, gemini_http, grok, openai_compat, anthropic, ollama, mock_agent). Hosts HTTP LoopTransport primitives.
orbit-tools	Generic tool registry plus workspace-scoped builtins, filesystem tools, and policy-aware exec tools.
orbit-policy	Filesystem-scoping policy engine. Owns FsProfile resolution and denyRead / denyModify evaluation.
orbit-exec	Process / sandbox / supervision primitives for shell-command execution under an FsProfile.
orbit-store	Generic YAML/SQLite stores, connection primitives, namespaced feature-migration ledger, and immutable historical bootstrap migrations. Feature crates own their active schemas and queries.
orbit-mcp	RMCP framing, canonical discovery, server identity context, and direct SSH stdio proxy.
orbit-search	Retrieval/ranking feature and workspace-local semantic index; also builds orbit-search-companion, a separately installed embedding companion binary, as an additional [[bin]] target.
orbit-types	Lowest contract leaf — domain-qualified shared types (identity, workspace, task, workflow, policy, resource, tool, telemetry, record) and OrbitId. No I/O or Orbit crate deps.
orbit-common	Mechanism crate above orbit-types — OrbitError, governance, filesystem, process, storage, protocol, observability, and security helpers.

Dependency Direction

flowchart LR
  CLI["orbit-cli"] --> Cmd["orbit-cmd"]
  CLI --> Core["orbit-core"]
  CLI --> MCP["orbit-mcp"]
  CLI --> Registry["orbit-registry"]
  CLI --> Web["orbit-web"]
  Web --> Core
  Web --> Registry
  Cmd --> Core
  Core --> Engine["orbit-engine"]
  Core --> Store["orbit-store"]
  Core --> Tools["orbit-tools"]
  Engine --> Agent["orbit-agent"]
  Engine --> Store
  Engine --> Tools
  Agent --> Tools
  Tools --> Exec["orbit-exec"]
  Tools --> Policy["orbit-policy"]
  MCP --> Registry
  MCP --> Tools
  MCP --> Common["orbit-common"]
  Store --> Common
  Exec --> Common
  Policy --> Common
  Common --> Types["orbit-types"]

Arrows show the principal layering edges rather than every manifest edge. Do not add cross-crate dependencies that violate this direction. Layering constrains dependency direction, not feature ownership: focused feature crates own their domain data and transport behavior while reusing neutral kernels. Lower layers stay reusable and never depend back on the feature. In particular, orbit-core must not depend on orbit-agent (the CLI agent subprocess runner in orbit-engine is the bridge) and must never depend on orbit-cmd.