Tolaria boundary

Type: agentic-system-analyses/types/agentic-system-boundary.md

Boundary and evidence

This run examines Tolaria as a file-backed knowledge-base application with model-dependent paths for consuming and changing that knowledge. It is not a review of any one CLI agent's internal runtime. The intended use is to explain the shipped knowledge, context and agent-integration mechanisms from source, distinguishing application responsibilities from delegated agent behavior.

The target class is memory/knowledge/context-engineering system. The README describes the application as managing Markdown knowledge bases, including company documentation used as AI context and assistant memory. This establishes intended use, not evidence of those deployments (SRC-1, README.md). The source also supplies executable model-call entry points, rather than merely advertising compatibility with external tools: the frontend selects CLI-agent or direct-model streaming, and native commands dispatch into the corresponding Rust implementations (SRC-1, src/lib/aiAgentSession.ts, src/utils/streamAiAgent.ts, src/utils/streamAiModel.ts, src-tauri/src/commands/ai.rs).

Tolaria is a desktop app for macOS, Windows, and Linux for managing markdown knowledge bases. People use it for a variety of use cases: --- README.md

if (context.target?.kind === 'api_model') { --- src/lib/aiAgentSession.ts

The functional boundary includes the desktop application, its React callers and native commands, vault files and derived state, agent prompts and managed guidance, transcript storage, CLI adapters, direct-provider calls, MCP server and UI bridge, and the repository's web/remote/collaboration paths. A caller shipped here is part of the target even when it invokes a library API. Native startup calls tolaria_lib::run; the renderer lazy-loads the application. The agent dispatcher names Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, Kiro and Hermes adapter paths (SRC-1, src-tauri/src/main.rs, src/main.tsx, src-tauri/src/ai_agents.rs).

The boundary kind is complete artifact, partial loop, not whole-system. The complete repository is frozen and available, but initial inspection traces selected producer/consumer paths rather than establishing exhaustive coverage of every shipped state path. In particular, vault scanning/cache invalidation, editor admission and serialization, watcher/Git reconciliation, every adapter's permission implementation, and remote collaboration persistence have not been traced end to end. These are available but not yet inspected responsibilities, not unavailable evidence or deliberate functional exclusions. Their inclusion in the target does not establish that their implementations have been assessed. This boundary prevents a whole-system completeness claim and any blanket conclusion about durable correctness, safety or cross-client consistency.

Initial inspection establishes these paths and limits:

Two short passages fix consequential distinctions for later work:

Each agent still owns its authentication, available tools, and runtime behavior. --- site/concepts/ai.md

if should_offer_openai_tools(request) { payload["tools"] = serde_json::Value::Array(vec![openai_create_note_tool()]); payload["tool_choice"] = serde_json::Value::String("auto".into()); } --- src-tauri/src/ai_model_tools.rs

External dependencies include the selected installed agent CLIs and their authentication/model services; direct-provider endpoints; MCP clients and SDK; the operating system, Node, Tauri and frontend libraries; and optional Git remotes. Their implementation and live behavior are excluded: the source supports how Tolaria invokes them, not their actual enforcement, reliability or model quality. User vault contents, private deployments and the separately hosted starter-vault repository are not captured; this prevents conclusions about actual user knowledge quality, accumulated memory effectiveness or the current remote starter content. Repository-contained examples and generated documentation remain available source, not independent deployment evidence (SRC-1, package.json, src-tauri/src/vault/getting_started.rs, README.md).

The sole frozen source is the acquired Git repository at 48f2a70844c1e8005a7aa5f1499c66f7678360de. HEAD was checked against that pin. The applicability cutoff is 2026-10-14, the supplied run date; dates inside source material do not expand this boundary. The overall tier is code-grounded. No target execution, live provider calls, fetched documentation, observed-run artifacts or causal experiments are included. No source access failure was encountered.

Source register