browzy.ai boundary

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

Boundary and evidence

The target is the repository's personal knowledge system, including its terminal application and importable engine. Its intended use is to ingest user-selected material, compile retained wiki articles, and answer questions from those articles. It qualifies as a memory/knowledge/context-engineering system, rather than only a model API client: the shipped code owns source admission, article persistence, indexing, later retrieval and model-conditioned answering (SRC-1, src/core/ingest/index.ts, src/core/compile/compiler.ts, src/core/retrieval/contextBuilder.ts, src/core/query/engine.ts).

The boundary is whole-system at the source level. It includes the CLI drivers, prompts, customization file mechanism, maintenance paths, demo state producer and evaluators, not just exported library classes. The package's executable is the Ink/Commander entry; the library is a separate shipped surface (SRC-1, package.json, src/cli/entry.tsx, src/index.ts).

"bin": { "browzy": "dist/cli/entry.js" }, --- package.json

Tracing that entry reaches BrowzyApp when no arguments are supplied and the registered ingest, compile, query, lint, status, search and init commands otherwise. The older Commander/readline entry explicitly identifies itself as unused; its presence is not evidence that normal users run the old REPL (SRC-1, src/cli/entry.tsx, src/cli/index.ts).

Functional loop included

• Produce and admit: ingestion dispatches web, PDF, image and text processors, updates the raw manifest and source database, and invalidates the query cache. The application offers source previews and compilation guidance, bulk compilation, topic-search ingestion and optional clipboard capture. These callers are part of browzy, not an excluded host (SRC-1, src/core/ingest/index.ts, src/cli/app.tsx).
• Retain and maintain: compilation reads the raw manifest and existing articles, makes model calls for nontrivial sources, parses article markers, persists Markdown and search records, and updates backlinks and the wiki index. Short sources have a template path without a model call. Health checks, refresh/re-ingestion, rebuild requests and user schema controls remain inside the boundary; their labels do not establish that their intended effects always succeed (SRC-1, src/core/compile/compiler.ts, src/core/storage/filesystem.ts, src/core/lint/linter.ts, src/cli/app.tsx).
• Reload and consume: context construction searches SQLite, reloads article files and falls back to the wiki index before ranking and context assembly. The library query path calls the model itself; the terminal application calls prepare and then streams through the provider. Both paths are included, so library capabilities are not automatically attributed to the terminal caller (SRC-1, src/core/retrieval/contextBuilder.ts, src/core/query/engine.ts, src/cli/app.tsx).
• Retain interaction-derived material: the application saves sessions and metadata, reloads a prior session for digest generation, attempts to persist a digest as a wiki article, and invokes an insight crystallizer after multi-article answers. The crystallizer writes to drafts, not directly to wiki. This establishes separate code paths, not successful promotion or later retrieval of drafts (SRC-1, src/cli/hooks/useSession.ts, src/cli/app.tsx, src/core/query/crystallizer.ts).
• Direct behavior and evaluate: shipped compiler/query/linter/digest/crystallizer prompts and the user schema mechanism are included alongside retrieval and security test sources. Prompt instructions establish intended behavior, not compliance; tests are inspected source, not observed test results (SRC-1, src/core/prompts.ts, src/core/schema.ts, tests/e2e/retrieval-quality.test.ts, src/core/__tests__/filesystem.test.ts).

Minimum implementation passages supporting the retained-state loop:

this.fs.writeArticle(article.slug, article.frontmatter, article.content); --- src/core/compile/compiler.ts:123-123

const results = this.db.search(query, 20); for (const r of results) { if (!slugs.has(r.slug)) { slugs.add(r.slug); const article = this.fs.readArticle(r.slug); if (article) articles.push(article); } } --- src/core/retrieval/contextBuilder.ts

session.saveSession(); session.saveSessionMeta(stats); --- src/cli/app.tsx

// Write to drafts/ directory (NOT wiki/) const draftsDir = join(dataDir, 'drafts'); --- src/core/query/crystallizer.ts

Repository coverage

The tracked root tree was enumerated at the frozen commit. “Included” fixes functional scope; it does not claim a line-by-line audit. Available material not yet inspected remains distinguishable from unavailable evidence and is eligible for later inspection at this same pin.

Frozen evidence and external boundary

The sole frozen source is SRC-1 at commit 56c253042041ee2f483a5e9b824174d746891cf4, applicable through the run cutoff 2026-10-15. The acquired checkout's HEAD matched that commit and its status was clean. This is code-grounded analysis with documentation as attributed design evidence. No target process, examples, tests or provider calls were executed.

External dependencies include model services selected through the Claude, OpenAI, OpenRouter and Ollama provider adapter, web/search destinations, local user inputs and customization, and npm dependencies including SQLite bindings, SDKs, Ink and document parsers (SRC-1, src/core/llm/provider.ts, src/cli/app.tsx, package.json). The repository's adapter and integration code is included; service implementations, model weights, live pages, dependency repositories and arbitrary consuming applications are excluded. These exclusions prevent conclusions about provider reliability, model accuracy, live search quality, third-party implementation guarantees or behavior of an unspecified host.

No user knowledge directory, real session corpus, deployed environment, run trace, npm distribution capture or causal experiment was supplied. These are unavailable evidence, not uninspected repository files. Consequently the boundary supports source-level control/data-flow analysis and attributed intent, not observed persistence success, answer quality, security effectiveness, latency, cost or compounding knowledge quality. Obsidian compatibility in the README remains a declared integration claim, not inspected Obsidian operation (SRC-1, README.md).

Source register