禁用了知识库技能，添加了知识库memory

offline-backend-20260512/backend/knowledge/knowledge_base/rules/knowledge_usage.md

@@ -0,0 +1,75 @@
+# Knowledge Usage Rules
+
+Use this file when a caller skill needs material from the policy knowledge base.
+
+## Role Of The Knowledge Base
+
+The knowledge base is a substrate for other skills. It provides:
+
+- File navigation.
+- Background concepts.
+- Actor, event, narrative, and policy context.
+- Optional domain playbooks.
+- Evidence and source pointers.
+
+It does not automatically own the final answer structure. If the caller skill has its own workflow or output format, follow the caller skill and use knowledge-base files as supporting material.
+
+## Reading Discipline
+
+1. Start from `routing.md`, a relevant `_MANIFEST.md`, or a legacy routing file.
+2. Read only files that are relevant to the current task.
+3. Do not read the whole knowledge base.
+4. For large directories, read `_MANIFEST.md` before opening individual files.
+5. For long files, read the relevant section when possible instead of consuming the entire file.
+6. Prefer existing local files and local helper APIs over ad hoc guessing.
+
+## When To Read A Playbook
+
+Read a playbook when the task needs a domain-specific analysis method, such as:
+
+- Signal interpretation.
+- Scenario planning.
+- Narrative attribution.
+- Party strategy analysis.
+- Escalation risk assessment.
+- Election or voter-flow analysis.
+
+Do not force a playbook for simple background lookup or when the caller skill already provides a complete method.
+
+## When To Read Knowledge Files Without A Playbook
+
+Use knowledge files directly when the caller only needs:
+
+- A factual background note.
+- Actor context.
+- Event timeline context.
+- A narrative definition.
+- A concept or framework definition.
+- A reference table.
+
+In these cases, read the relevant `_MANIFEST.md` and concrete files, then return the information in the caller skill's format.
+
+## File Priority
+
+When unsure, use this order:
+
+```text
+routing.md
+  -> rules/*.md as needed
+  -> relevant _MANIFEST.md
+  -> relevant playbook if method is needed
+  -> concrete entities / narratives / events / primitives / reference files
+```
+
+## Separation From Current Events
+
+Knowledge files may be stale. Treat them as background and analytical context. Use `bm25_search_news` or user-provided current materials for recent facts.
+
+## Output Integration
+
+When using knowledge-base material:
+
+- Mention the specific file when it materially supports a claim.
+- Do not say only "the knowledge base says".
+- Preserve the caller skill's final format.
+- Mark uncertainty if the knowledge base does not cover a key point.