llm-wiki boundary

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

Boundary and evidence

This run analyses llm-wiki as an agent-facing knowledge and context system, not as an enclosing agent runtime. Its intended use is to retain reusable domain knowledge in Markdown bundles, retrieve that knowledge during later work, maintain its structure, and deliver directory-specific behavioral instructions to a model's host. The frozen target includes the shared core, its vendored copies, and all five shipped consumption forms: DSH, pi, MCP, Codex, and skill/CLI. It also includes shipped maintenance procedures, migrations, sample bundles, and evaluation code. These are responsibilities of the target even when a host invokes them (SRC-1, README.md, packages/core/index.mjs, packages/skill/SKILL.md).

The repository describes the common retained state and its consumers:

All five forms read and write the same bundle with identical behavior — they reuse packages/core, no duplicated implementation. --- README.md

This is design doctrine, not an established equivalence result. Initial implementation inspection traced the CLI's list/search/get/create/update dispatch to the core, the core's file writes and index/log maintenance, and its later reconstruction of concepts and backlinks from disk (SRC-1, packages/skill/bin/wiki.mjs, packages/core/lib/write.mjs, packages/core/lib/bundle.mjs). For example, creation retains the serialized concept before maintaining derived navigation:

const text = serializeDoc({ meta, body: p.body || '' }) await mkdir(dirname(file), { recursive: true }) await writeFile(file, text) --- packages/core/lib/write.mjs

The boundary includes admission behavior in the shipped callers, not just the core library API. The core's write module explicitly assigns interactive gating to those callers; inspected CLI and MCP creation paths consult directory gates before invoking createConcept (SRC-1, packages/core/lib/write.mjs, packages/skill/bin/wiki.mjs, packages/mcp/lib/tools.mjs). This establishes where to inspect admission, not a claim that every mutation path enforces identical gates.

The later-consumption loop also includes prompt delivery. Initial inspection traced DSH's apply handler from bundle resolution and prompt collection into assembly sections and runtime contexts; pi's default extension into tool registration and its per-turn prompt hook; the MCP executable into server assembly and tool dispatch; and Codex's manifest/hooks into context snapshot generation and its bundled MCP executable (SRC-1, packages/dsh/wiki.mjs, packages/pi/extensions/index.ts, packages/mcp/bin/wiki-mcp.mjs, packages/mcp/lib/server.mjs, packages/codex/.codex-plugin/plugin.json, packages/codex/hooks/hooks.json, packages/codex/hooks/inject-context.mjs, packages/codex/bin/wiki-mcp.mjs). The pi hook exposes a concrete model-context consumption surface:

const base = typeof event.systemPrompt === "string" ? event.systemPrompt : ""; return { systemPrompt: ${base}\n\n${text} }; --- packages/pi/extensions/index.ts

Thus whole-system means the repository's complete knowledge-system responsibility, including its host adapters and maintenance paths. It does not mean the enclosing model-execution loop. The target serves model-dependent work through tools, prompts and skills; the external host selects and calls the model and decides whether to follow returned guidance. The skill itself identifies that host boundary (SRC-1, packages/skill/SKILL.md). No model compliance, model quality improvement, or autonomous knowledge acquisition is established by these entry points alone.

Tracked top-level coverage

The tracked tree was enumerated at the frozen commit. Every top-level tracked file or directory is classified below. “Included” is functional scope, not a claim that every file has already been read. Initial inspection is listed separately; available but unread files remain eligible evidence under SRC-1 and are not access gaps.

Evidence and dependency limits

The immutable revision is f70e680d852a78d48504425d87252531e68c5624; checkout HEAD was checked against the acquired pin. The applicability cutoff is 2026-11-08. No later revision, live deployment or installed npm package is included. The overall tier is code-grounded: source inspection establishes implementation structure alongside documentation, but this job did not execute the target, tests or examples.

External dependencies are the enclosing DSH/pi/Codex/MCP-capable hosts and their model providers; Node and relevant transport/UI libraries; the Git executable and remote service; Feishu and lark-cli; and optional Obsidian/Dataview. Only the target-side contracts and adapters are in scope. Their external implementations, credentials, real user bundles and service state are not frozen here, preventing conclusions about live interoperability, successful synchronization, host prompt precedence or model adherence. The referenced upstream OKF specification and Karpathy pattern are not separate registered sources; the run may describe this repository's stated alignment, not independently establish alignment against unfrozen external documents (SRC-1, README.md, schema.md, SPEC-EXTENSIONS.md).

No observed execution trace or causal experiment was supplied. Test code and synthetic examples therefore cannot establish operational reliability, factual accuracy of retained knowledge, retrieval effectiveness on real workloads, or benefits to downstream model tasks. These are evidence limits, not unavailable repository paths.

Source register