From d3ea521c0bf80555128047ff236a136f5e77bb8c Mon Sep 17 00:00:00 2001 From: Dotta Date: Mon, 18 May 2026 08:38:34 -0500 Subject: [PATCH] docs: clarify content plugin managed resource guidance Co-Authored-By: Paperclip --- doc/plugins/PLUGIN_AUTHORING_GUIDE.md | 5 +++++ doc/plugins/PLUGIN_SPEC.md | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/doc/plugins/PLUGIN_AUTHORING_GUIDE.md b/doc/plugins/PLUGIN_AUTHORING_GUIDE.md index 815814d69ea..d6e71df9dbd 100644 --- a/doc/plugins/PLUGIN_AUTHORING_GUIDE.md +++ b/doc/plugins/PLUGIN_AUTHORING_GUIDE.md @@ -142,6 +142,11 @@ Do not hide long-lived work behind private plugin state when it should be visibl to the board, scoped to a company, audited, budgeted, and assigned like normal Paperclip work. +Content-oriented plugins, such as LLM Wiki-style ingestion or durable knowledge +systems, should use the same pattern: managed projects for operation issues, +managed agents plus managed skills for LLM work, and managed routines for +ingest, lint, refresh, or maintenance runs. + Use these surfaces: - Managed agents: declare top-level `agents[]` and require diff --git a/doc/plugins/PLUGIN_SPEC.md b/doc/plugins/PLUGIN_SPEC.md index 1fe3490d692..e8cda1de932 100644 --- a/doc/plugins/PLUGIN_SPEC.md +++ b/doc/plugins/PLUGIN_SPEC.md @@ -673,6 +673,11 @@ Plugins that perform durable work should declare managed Paperclip resources rat The LLM Wiki plugin is the current reference for this pattern: it declares managed agents, projects, routines, and skills in manifest, reconciles them per company, and uses managed routines for periodic wiki maintenance and ingest operations. +Content-oriented plugins should follow the same model instead of running +unmanaged background loops: make the LLM-facing worker an operator-visible +managed agent, attach reusable prompt/tool guidance as managed skills, keep +operation issues in a managed project, and drive recurring work through managed +routines. Origin rules: