Architecture

Navi Agent keeps a small runtime-centered architecture. Protocol adapters and offline evolution stay outside the core execution loop.

flowchart LR
    CLI[CLI / Weixin] --> APP[Application Service]
    APP --> RUNTIME[Agent Runtime]
    RUNTIME --> MODEL[Model Transport]
    RUNTIME --> TOOLS[Tool Registry]
    RUNTIME --> EVENTS[Runtime Events]
    RUNTIME --> SESSIONS[Session Store]
    RUNTIME --> MEMORY[Memory]
    EVENTS --> STORE[Event Store]
    EVENTS --> TRACE[Trace Builder]
    EVENTS --> HEALTH[Health Metrics]
    EVENTS --> UI[UI Events]
    STORE --> EVOLUTION[Offline Evolution]

Responsibilities

Gateway

Handles protocol polling, message normalization, access policy, and outbound delivery. The current gateway implementation supports Weixin only.

Application service

Assembles runtime dependencies and exposes use-case-level operations to the CLI and gateway without leaking storage details.

Runtime

Owns session loading, context construction, model calls, tool dispatch, steering, cancellation, compaction, and final responses.

Tools

Expose capabilities through explicit schemas and results. Tools validate their inputs, but approval and execution policy remain in the runtime.

Runtime events

RuntimeEvent is the fact stream for execution. Subscribers persist events or derive traces, health data, and user-facing progress without coupling those views to the runtime loop.

Memory and sessions

The session store is authoritative for conversation history. Memory provides cross-session recall and remains user-scoped.

Evolution

Consumes stored evidence to propose and govern prompt or skill candidates. It does not mutate the live runtime path directly.