LLM Repo Wiki boundary

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

Boundary and evidence

This run covers LLM Repo Wiki as a shipped, local knowledge system over GitHub repositories, not just its MCP server or author API. Its intended use is to ingest repository evidence, propose and maintain wiki pages, admit human-reviewed revisions, and answer questions from retained code and wiki content. The target class is memory/knowledge/context-engineering system; the boundary kind is whole-system. The repository ships the producers, review surface, persistence and later consumers within the same application (SRC-1, README.md, package.json, src/worker.ts, src/app/w/[wiki]/actions.ts, src/agent/chat.ts, src/mcp/server.ts).

The model-dependent production path is explicit in implementation: the author job retrieves evidence in code and calls a language model to draft structured pages. Its own explanation distinguishes this from a model-controlled retrieval loop (SRC-1, src/agent/author.ts):

// The job retrieves and the model only writes: tools + JSON output in one loop let models skip // searching (or never stop), and evidence we chose is evidence we can check citations against. --- src/agent/author.ts

Shipped writing instructions also participate in operation, rather than merely documenting it. The prompt loader reads WIKI_SCHEMA.md per call, and both author and chat instructions incorporate it (SRC-1, src/agent/prompts.ts). The schema states:

The rules the author agent follows when it writes this wiki. This file is part of the agent's system prompt, so edit it to change how the wiki is written. --- WIKI_SCHEMA.md

Included loop and entry points

The following trace fixes the functional boundary. It establishes coverage, not that every implementation detail has already been analysed.

• package.json exposes the Next.js application, separate src/worker.ts, stdio src/mcp/server.ts, repository-add CLI, export CLI and evaluation/benchmark drivers. The worker registers ingestion, wiki-maintenance and author jobs (SRC-1, package.json, src/worker.ts).
• Ingestion jobs bind GitHub, embedding, chunking, stale-page marking and author scheduling. The sync path marks affected pages stale and enqueues authoring after changed-file work. Thus acquisition and refresh are inside the target, not assumed responsibilities of an external host (SRC-1, src/ingest/jobs.ts, src/ingest/sync.ts).
• Author-job registration injects the wiki-scoped store, search and model. Authoring loads project context and the schema, reads existing pages, gathers source hits, and calls generateText. Initial and incremental authoring belong to the same boundary (SRC-1, src/agent/jobs.ts, src/agent/author.ts, src/agent/prompts.ts).
• Server actions implement human editing, acceptance, rejection, bulk decisions and reversion. Store acceptance checks the proposal's parent revision, updates the current revision and schedules indexing. The index-page job embeds accepted page sections into wikiChunks. This is the admission-to-retrieval connection, not an excluded UI concern (SRC-1, src/app/w/[wiki]/actions.ts, src/wiki/review.ts, src/wiki/store.ts, src/ingest/index-page.ts).
• The shipped page route reloads stored content, citations, stale-file information and proposals for display and review. Chat reloads server-side messages, builds context from summary, schema, tree and project context, runs a tool-loop agent, and saves responses. Context folding persists a model-written summary for later turns (SRC-1, src/app/w/[wiki]/wiki/[...path]/page.tsx, src/app/api/w/[wiki]/chat/route.ts, src/agent/chat.ts, src/agent/context.ts).
• Hybrid search is shared by the application and MCP dependency wiring. The MCP server serves search, page reads, page lists, freshness and sync requests for one wiki. Export reloads accepted revisions and emits Markdown. These are material consumers of retained state, so all are included (SRC-1, src/search/index.ts, src/mcp/server.ts, src/export/cli.ts, src/export/export.ts).
• Daily wiki lint is registered by the worker. Evaluation and benchmark drivers are included as shipped measurement machinery; their presence is not evidence that this run executed them (SRC-1, src/wiki/jobs.ts, eval/run.ts, package.json).

Top-level tracked coverage

The tracked tree was inspected at the frozen commit. Every top-level tracked item is classified below. “Included” establishes scope for later inspection, not a claim to have read every blob. Paths named as initially traced were read or searched; remaining included files are available but not yet substantively inspected. No material shipped path was inaccessible.

Frozen evidence and external limits

The sole frozen source is the acquired Git checkout at 38a439cd649105c0cd90b687fc1f8d8dd1d0986c; its HEAD was checked against the acquired object. The applicability cutoff is 2026-11-09. The overall tier is code-grounded: executable source supports the responsibility trace, while schema, README and development instructions supply declared intent. This run has not executed the application, tests, examples or model calls.

External GitHub repositories being indexed, the GitHub service, OpenRouter/provider services, PostgreSQL/pgvector and dependency package implementations are outside the frozen evidence. Their integration code and declared configuration are included, but service behavior, provider retention, model reliability and database-engine guarantees cannot be independently established from this checkout. The concrete database of an installed instance, ignored benchmark result files and local secrets/configuration were not supplied; this prevents claims about an actual user's retained content, measured performance or live freshness. Claude Code and other MCP hosts are external consumers: this boundary includes the shipped MCP server, instructions and benchmark drivers, not an enclosing client's reasoning, edit policy or memory. No source link in the repository expands this run to another repository or moving web page (SRC-1, README.md, package.json, docker-compose.yml, docs/mcp.md, src/mcp/server.ts).

Source register