expo-llm-wiki boundary

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

Boundary and evidence

This run analyses the repository's shipped family of SQLite-backed memory packages, including its own callers, prompts, maintenance interfaces and evaluation drivers. Its intended use is retaining conversational and document-derived knowledge for later agent or application queries. The target is a memory/knowledge/context-engineering system, not an enclosing general-purpose agent runtime. The boundary is whole-system at the repository level; it does not claim to include independently deployed hosts or providers. SRC-1, README.md, packages/core/src/index.ts, packages/core/src/WikiMemory.ts.

Core LLM Wiki is a family of cross-platform TypeScript packages for long-term LLM memory, built on SQLite. It turns raw conversation logs and documents into a structured knowledge base of facts, tasks and graph edges, with background fact extraction, semantic search and memory pruning. It runs wherever your app runs: Expo, React Native, the browser, or Node.js. --- README.md

The inspected entry path runs from root compatibility exports through platform factories to WikiMemory, which composes repositories and ingestion, retrieval, write, maintenance, temporal, graph and import/export services. Inclusion covers direct deterministic writes as well as model-mediated extraction. Event writing can trigger background maintenance; explicit maintenance APIs also exist. The librarian reads retained events and facts, constructs a prompt, calls the supplied model interface, parses its result and validates candidates. These paths establish model-dependent operation rather than merely a database wrapper. SRC-1, src/index.ts, src/react/index.ts, packages/expo/src/factory.ts, packages/core/src/WikiMemory.ts, packages/core/src/services/WriteService.ts, packages/core/src/services/librarian/legacy.ts, packages/core/src/prompts.ts.

responseText = await callLlm( deps.options, { operation: 'librarian', entityId, trigger, meter: ctx.meter }, { systemPrompt, userPrompt }, ); --- packages/core/src/services/librarian/legacy.ts

The whole-system boundary includes shipped consumers, not just the public API. ScopeLab writes user messages, retrieves context, inserts it into a model request and dispatches an authorized tool call; its memory wrapper is included even where implementation may not fulfil its persistence intent. WikiDemo constructs a provider-backed memory instance and supplies interactive read, write, ingest, maintenance and export surfaces. The benchmark driver persists an ingestion database, reopens it, reads a memory bundle, formats it for an answer model, and asks a judge model for a verdict. Consequently, later analysis can assess the shipped retention-to-consumption loop rather than excluding the drivers that supply its state. These are source traces, not successful executions. SRC-1, apps/scopelab/src/lib/memory/wiki-service.ts, apps/scopelab/src/lib/llm/function-caller.ts, apps/wiki-demo/src/App.tsx, packages/benchmarks/src/longmemeval/ingest.ts, packages/benchmarks/src/longmemeval/run.ts.

const bundle = await wiki.read(ENTITY, q.question, readOpts as any); const context = formatContext(bundle, { maxEvents: 0, maxTasks: 0 }); --- packages/benchmarks/src/longmemeval/run.ts

The MCP package is included as a distinct shipped integration: its tool server delegates operations to a SynapseTree HTTP client, not directly to the local WikiMemory object. The remote service's implementation, authorization enforcement and production persistence are unavailable in this source set, so no local-engine property is automatically attributed to that service. The Prisma outbox consumer and native Rust GraphRAG slice are also included; neither is treated as the enclosing runtime. SRC-1, packages/mcp-server/src/server.ts, packages/mcp-server/src/tools/memory-search.ts, packages/mcp-server/src/client.ts, packages/prisma-outbox/src/PrismaOutboxWorker.ts, crates/graphrag-core/src/lib.rs, crates/graphrag-core/README.md.

External dependencies include caller-supplied SQLite adapters and storage lifecycle, inference and embedding providers, browser/Expo/React facilities, MCP clients, and the remote SynapseTree and Prisma endpoints. Their internal implementations and live behavior are outside the frozen repository. This prevents claims of provider reliability, deployment durability, external authorization correctness or end-to-end production success. Shipped wrappers, request construction, state transitions and error handling remain within scope. SRC-1, README.md, packages/expo/src/factory.ts, packages/react/src/WikiContext.tsx, packages/mcp-server/src/client.ts, packages/prisma-outbox/src/PrismaOutboxWorker.ts.

The frozen evidence is SRC-1 at full commit 09c90258560a6b1664038d642b5d25d9de0c4d3d, verified as the acquired checkout's HEAD. The analysis cutoff is 2026-11-08. The overall tier is code-grounded. Source documentation supplies declared design, not independent confirmation. Tests and benchmark drivers are inspected as implementation and evaluation design; their presence does not establish passing results. No target code, tests, examples or provider calls were executed for this boundary. Available but not yet inspected files remain eligible under SRC-1; initial inspection is not a path allowlist.

Top-level coverage

Every top-level tracked file or directory is classified below. “Included” sets functional scope; it does not mean every file has already been read. No material shipped memory-loop path is deliberately excluded.

Source register