Stigmergy boundary

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

Boundary and evidence

This run examines Stigmergy as a complete shipped team-knowledge system, not just its MCP server or librarian API. Its intended use is to accept captures from people and agents, retain evidence, compile a shared wiki, maintain it, and return visibility-scoped knowledge to later readers. The target class is memory/knowledge/context-engineering system and the boundary kind is whole-system. It is in scope because its knowledge-production and answering paths issue model calls; it is not merely a static store or a host-independent returning computation. The source's own description supplies the intended use (SRC-1, README.md):

Immutable source material enters one queue, one librarian agent keeps a small Git-and-Markdown wiki current, and every search and answer is scoped to what the caller may see. --- README.md

The implementation trace starts at the console scripts declared in SRC-1, pyproject.toml. The librarian CLI constructs workspace dependencies and a worker; the worker claims a tenant's queued operation and invokes the writer. The capture writer extracts evidence, renders a source page, constructs a safe existing-context view and requests a filing plan (SRC-1, src/stigmergy/librarian/cli.py, src/stigmergy/librarian/worker.py, src/stigmergy/knowledge/writer.py). The planner actually supplies the shipped librarian instructions to its structured model call, rather than merely documenting an optional prompt (SRC-1, src/stigmergy/knowledge/planner.py):

result = await self._run_structured( output_type=FilingPlan, instructions=_read_skill(), --- src/stigmergy/knowledge/planner.py

return expected_librarian_skill().decode("utf-8") --- src/stigmergy/knowledge/planner.py

The packaged instructions establish the model-dependent state transformation (SRC-1, src/stigmergy/knowledge/librarian_skill.md):

Read the complete source and return one FilingPlan: the note, concept, entity, and project pages this source creates or updates, and the wikilinks that connect them. The source is immutable evidence. The catalog and candidate pages are the existing graph. Do not narrate your work. --- src/stigmergy/knowledge/librarian_skill.md

The read loop is shipped here too. MCP wrappers call BrainService, the bridge proxies reads while acquiring submission artifacts locally, and the answer service invokes its synthesizer over service-backed evidence and verifies the result (SRC-1, src/stigmergy/server/mcp_server.py, src/stigmergy/server/service.py, src/stigmergy/bridge/server.py, src/stigmergy/answer/service.py). This is later consumption of retained wiki state, not just a write-only library. The answering implementation includes:

prompt = first_message(question, self._first_search(question, ctx)) --- src/stigmergy/answer/service.py

verdict = verify(out, evidence, ctx.page_as_read, ctx.read_paths) --- src/stigmergy/answer/service.py:264-264

Functional inclusions are acquisition and normalization, original-evidence retention, queue admission and routing, tenant and audience policy, model planning and its instructions, candidate mutation and publication gates, Git publication and change records, scheduled repair and recompile, index construction and reconciliation, retrieval and verified answers, shipped adapters, backoffice readers and controls, erasure/refiling, deployment wiring, and evaluation drivers. The maintenance and lifecycle paths are part of the target, not an excluded host: the writer worker calls garden/rebuild/erasure paths, and the architecture declares recompile and refiling responsibilities (SRC-1, src/stigmergy/librarian/worker.py, src/stigmergy/knowledge/writer.py, docs/ARCHITECTURE.md). Their detailed semantics remain for later analysis; inclusion does not certify their correctness.

The frozen evidence is repository https://github.com/sturlese/stigmergy at full commit 0ca8bb1963ad9cf43eaf2c18329998023a9caa4f, inspected read-only at the source path above. HEAD was checked against the acquired revision. The applicability cutoff is 2026-11-08, the supplied run date, not a claim about when every file was authored. The overall tier is code-grounded: executable entry points and producer/consumer paths were inspected alongside design documentation. No target code, tests, examples, models or services were executed.

External dependencies include model routing/providers through OpenRouter, Postgres/pgvector, Git/GitHub and the librarian App, a private object store, Slack, Google Drive acquisition, and deployment services such as Fly. Their shipped clients, configuration and failure-handling code remain included; service internals and live deployments do not. This prevents conclusions about provider internals, actual deployment availability, production isolation, latency, cost or observed knowledge quality. The dependency declarations, process wiring and intended integrations are in SRC-1, pyproject.toml, docker-compose.yml, README.md and docs/ARCHITECTURE.md. External MCP hosts such as Claude Code and Codex are consumers, not Stigmergy-owned runtimes; this boundary cannot establish their autonomous submission policy or whether they actually reuse a returned answer. Tenant knowledge repositories and operator-created landing/legal content are not supplied as live evidence; fixtures and documentation cannot establish production corpus behavior (SRC-1, README.md, docs/ARCHITECTURE.md, evals/README.md). These are evidence limits, not reasons to omit the shipped producer or consumer code.

Tracked-root coverage

The tracked tree was enumerated at the pin. Every top-level tracked file or directory is classified below. “Included” means within the functional/evidence boundary, not that every descendant has already received line-by-line analysis. Initial inspection traced the principal write/read entry points and maintenance dispatch. Detailed implementations, specs, fixtures, tests and operator instructions not yet read remain available under SRC-1; they are not access gaps. No material shipped path was inaccessible. Excluded rows are deliberate scope exclusions, not unavailable evidence.

Source register