plugin-llm-wiki

LLM Wiki

Paperclip plugin for operating an existing LLM Wiki v2 Obsidian vault as a first-class local knowledge root.

Vault contract

The plugin uses the vault's native lifecycle:

10_Sources -> 20_Notes -> 30_Projects -> 40_Knowledge
           -> 50_Decisions -> 60_Workflows -> 90_Index

• 10_Sources/ preserves original material and Paperclip text snapshots. New captures default to 10_Sources/Incoming/.
• 20_Notes/ holds first-pass summaries, extracts, OCR/transcript notes, and observations.
• 30_Projects/ holds current project context and execution state.
• 40_Knowledge/ holds durable reusable concepts and domain knowledge.
• 50_Decisions/ holds explicit choices, rationale, alternatives, and reversals.
• 60_Workflows/ holds repeatable procedures and operating rules.
• 90_Index/ holds MOCs and navigation maps.

The plugin does not require a parallel content tree, a global index, or a vault activity log. Existing Korean filenames, nested domain folders, frontmatter, and Obsidian links remain native vault content. Bootstrap only adds missing starter files; it never replaces an existing file.

Features

• manifest-declared Wiki page, route sidebar, and local vault folder
• browsing and search across all seven lifecycle roots, including existing files not created by the plugin
• dedicated source capture and metadata persistence
• lifecycle-aware page writes with path validation, atomic writes, revision metadata, and optional stale-hash checks
• Obsidian wikilink/backlink discovery for title, path, alias, heading, and block forms
• managed Wiki Maintainer agent and managed ingest, query, lint, Paperclip distillation, and MOC-refresh skills
• paused Paperclip routines for bounded activity distillation, read-only lint, and relevant-MOC refresh
• Paperclip operation issues/comments as the work order, progress surface, result report, and audit trail
• explicit 필요한 데이터 reporting when available sources cannot support a requested claim

Paperclip-derived distillation currently targets the default wiki space. It maps current project state to 30_Projects/, durable concepts to 40_Knowledge/, decisions to 50_Decisions/, procedures to 60_Workflows/, and navigation changes to relevant MOCs under 90_Index/. Source snapshots stay under 10_Sources/Paperclip/.

Source preservation

Maintainer page-write tools reject 10_Sources/ destinations. Only the dedicated capture path creates source files, and capture does not overwrite existing content. Generated/maintained Markdown may target only:

• 20_Notes/
• 30_Projects/
• 40_Knowledge/
• 50_Decisions/
• 60_Workflows/
• 90_Index/

Normal indexing excludes Obsidian state, trash, AppleDouble files, and generated OCR page caches. Binary source material remains the vault operator's responsibility, including Git LFS policy where applicable.

Paperclip asset security gate

Paperclip-derived text ingestion is limited to issue titles/descriptions, issue comments, and issue documents.

• Issue attachments/assets are metadata-only.
• Issue work products are metadata-only.
• The plugin must not fetch /api/assets/:id/content, dereference work-product URLs, or store capability-bearing links as source content.

The accepted policy lives in doc/plans/2026-05-06-llm-wiki-paperclip-asset-security-gate.md.

Bootstrap layout

<configured-vault-root>/
  AGENTS.md                         # added only when missing
  .gitignore                        # added only when missing
  10_Sources/
    Incoming/
  20_Notes/
  30_Projects/
  40_Knowledge/
  50_Decisions/
  60_Workflows/
    LLM Wiki 운영 워크플로우.md     # starter, added only when missing
  90_Index/
    LLM Wiki 운영 MOC.md            # starter, added only when missing

An existing vault is considered structurally healthy from its lifecycle directories; plugin starter files are not required control files. Use the settings page or bootstrap action to add only missing starters. Paperclip's local-folder API provides path containment, symlink checks, read/write validation, and atomic writes.

Managed operations

Each operation is a Paperclip issue assigned to the Wiki Maintainer. The agent reads the issue/comments, performs bounded vault work, and comments with:

• changed paths
• evidence used
• relevant MOC updates
• unresolved risks and follow-up work
• 필요한 데이터, including the missing subject, needed source type, and files checked

Routine execution uses the same issue/comment path. Native v2 workflows do not encode Hermes-specific commands or maintain a synthetic vault log.

Development

From the repository root:

pnpm --filter @paperclipai/plugin-llm-wiki typecheck
pnpm --filter @paperclipai/plugin-llm-wiki test
pnpm --filter @paperclipai/plugin-llm-wiki build

After changing manifest-loaded assets such as skills, agent instructions, or templates, rebuild before re-enabling a local plugin install. The ignored package-local dist/ directory is what Paperclip loads at runtime.

Local installation

Build the package, then install its absolute directory through Paperclip's local plugin API or Plugin settings UI. For example:

curl -X POST http://127.0.0.1:3100/api/plugins/install \
  -H "Content-Type: application/json" \
  -d "{\"packageName\":\"$(pwd)/packages/plugins/plugin-llm-wiki\",\"isLocalPath\":true}"

Managed instruction sources

• agents/wiki-maintainer/AGENTS.md — managed agent identity and operating loop
• skills/*/SKILL.md — operation-specific procedures
• templates/AGENTS.md — optional vault-root starter contract

The settings health check can detect drift from managed agent defaults. Resetting managed instructions asks for confirmation before replacing operator customizations.