<!-- source: https://deepwiki.com/qhkm/zeptoclaw/14-glossary -->

# Glossary

- .config/nextest.toml
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- Cargo.lock
- Cargo.toml
- README.md
- deploy/homebrew/zeptoclaw.rb
- docs/ACP_IMPLEMENTATION.md
- landing/zeptoclaw/docs/src/assets/logo.svg
- landing/zeptoclaw/docs/src/styles/custom.css
- landing/zeptoclaw/index.html
- src/channels/acp_protocol.rs
- src/channels/factory.rs
- src/channels/mod.rs
- src/cli/channel.rs
- src/cli/common.rs
- src/config/mod.rs
- src/config/types.rs
- src/kernel/provider.rs
- src/lib.rs
- src/providers/mod.rs
- src/providers/registry.rs
- src/tools/mod.rs

This page provides definitions for codebase-specific terms, jargon, and architectural components within ZeptoClaw. It serves as a technical reference for onboarding engineers to understand the internal language and data structures of the system.

## Core System Entities

### AgentLoop

The central execution engine of ZeptoClaw. It manages the state machine for a single conversation, coordinating between the LLM provider, the tool registry, and the message bus.

- Implementation : AgentLoop is the primary struct in src/agent/loop.rs 1-10
- Data Flow : It receives InboundMessage objects, builds context via the ContextBuilder , calls an LLMProvider , and executes tools in a loop until a final response is generated src/lib.rs 46

### MessageBus

An asynchronous pub/sub system used for internal communication between communication channels (like Telegram or Slack) and the `AgentLoop`.

- Implementation : Defined in src/bus/mod.rs 1-20
- Types : Uses InboundMessage for user inputs and OutboundMessage for agent responses src/lib.rs 47

### ToolRegistry

A central repository of all available capabilities (Tools) that the Agent can invoke.

- Implementation : src/tools/mod.rs 128
- Role : It maps tool names (sent by the LLM) to actual Rust implementations of the Tool trait src/tools/mod.rs 138

### Provider

An abstraction over Large Language Model (LLM) APIs. ZeptoClaw supports multiple providers including Anthropic, OpenAI, and local backends like Ollama.

- Implementation : Controlled by the LLMProvider trait src/providers/mod.rs 84
- Registry : The PROVIDER_REGISTRY in src/providers/registry.rs 55 defines metadata and priority for resolution.

## Technical Jargon & Abbreviations

## Architectural Mapping

The following diagram bridges the gap between high-level conceptual names used in documentation and the specific code entities found in the `src/` directory.

### Natural Language to Code Entity Space: Execution Flow

"This diagram illustrates how a user request (Natural Language) is transformed into internal types and handled by specific code classes."

```

```

**Sources**: [src/lib.rs46-47](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/lib.rs#L46-L47) [src/bus/mod.rs1-20](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/bus/mod.rs#L1-L20) [src/providers/mod.rs84](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/providers/mod.rs#L84-L84) [src/tools/mod.rs128-138](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/tools/mod.rs#L128-L138)

### Natural Language to Code Entity Space: Configuration & Security

"Mapping of security concepts to the implementation layers and configuration types."

```

```

**Sources**: [src/config/types.rs58-139](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/config/types.rs#L58-L139) [src/config/mod.rs142-190](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/config/mod.rs#L142-L190) [src/lib.rs33-40](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/lib.rs#L33-L40) [src/audit.rs1-10](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/audit.rs#L1-L10)

## Glossary Details

### Compaction Tiers

ZeptoClaw uses a three-tier strategy to manage context window overflow:

1. Normal : Triggered at 70% capacity. Performs basic trimming.
2. Emergency : Triggered at 90% capacity. Aggressively removes older messages.
3. Critical : Triggered at 95% capacity. Instructs the LLM to flush important facts to memory before clearing the active session context.

- Code Pointer : CompactionStrategy in src/lib.rs 33 and CompactionConfig in src/lib.rs 34

### Tool Categories

Tools are grouped into `ToolCategory` enums to determine security policies (e.g., whether a tool requires manual approval).

- Implementation : src/tools/mod.rs 138
- Categories : Includes FilesystemWrite , Shell , Web , Memory , etc. These categories are used by the AgentModeConfig to decide if a tool call needs user confirmation src/lib.rs 83-85

### Runtime Runtimes

ZeptoClaw supports 6 distinct backends for executing code or the agent itself in isolation:

- Native : No isolation src/lib.rs 64
- Docker : Standard containerization src/lib.rs 64
- Apple Container : macOS-specific virtualization using Apple's virtualization framework src/lib.rs 81
- Landlock/Firejail/Bubblewrap : Linux-specific sandbox technologies for process-level isolation AGENTS.md 16

### Gateway Mode

A multi-channel server mode where ZeptoClaw acts as a central hub for various communication platforms (Telegram, Slack, Discord, etc.).

- Implementation : Managed via ChannelManager and specific channel implementations like TelegramChannel src/lib.rs 50-53
- Supervision : The gateway handles startup guards to prevent crash loops and manages hot-reloading of configuration AGENTS.md 45-53

**Sources**: [src/lib.rs1-101](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/lib.rs#L1-L101) [src/config/types.rs58-139](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/config/types.rs#L58-L139) [src/tools/mod.rs1-143](https://github.com/qhkm/zeptoclaw/blob/2c743d31/src/tools/mod.rs#L1-L143) [AGENTS.md1-60](https://github.com/qhkm/zeptoclaw/blob/2c743d31/AGENTS.md?plain=1#L1-L60)
