125 lines
5.2 KiB
Markdown
125 lines
5.2 KiB
Markdown
# Knowledge Base Routing
|
|
|
|
This file is the lightweight session-start routing memory for the policy knowledge base.
|
|
|
|
It may be injected at conversation start. It does not replace the caller skill. The caller skill owns the final workflow and output format; this file only points to the smallest useful knowledge entry point.
|
|
|
|
## Root
|
|
|
|
Knowledge root:
|
|
|
|
```text
|
|
/mnt/knowledge
|
|
```
|
|
|
|
Repository source path:
|
|
|
|
```text
|
|
offline-backend-20260512/backend/knowledge/knowledge_base
|
|
```
|
|
|
|
## Core Principles
|
|
|
|
Use the knowledge base as a reusable substrate:
|
|
|
|
1. Use this file to choose the first manifest, rule, or routing file.
|
|
2. Read only the files needed for the current task.
|
|
3. Do not force the caller skill into a full policy-analysis workflow unless the caller task needs it.
|
|
4. Prefer manifests before reading many files.
|
|
5. Follow the caller skill's output structure; use knowledge files only as supporting evidence.
|
|
|
|
## Scope
|
|
|
|
Use this knowledge base for Taiwan elections, Cross-Strait relations, US/Japan-Taiwan relations, political rhetoric, public-opinion events, policy signals, party dynamics, influence analysis, and scenario planning.
|
|
|
|
Do not use it for unrelated technical, lifestyle, economic, legal, medical, or private-person questions. Do not use it to produce political propaganda, campaign messaging, attacks, doxxing, private-communication analysis, or unverified allegations.
|
|
|
|
For unclear tasks, ask a focused clarification question before reading many files.
|
|
|
|
## Core Rules
|
|
|
|
Read these rule files only when needed:
|
|
|
|
```text
|
|
rules/knowledge_usage.md
|
|
rules/missing_and_placeholder.md
|
|
rules/citation_and_evidence.md
|
|
rules/realtime_news_usage.md
|
|
rules/neutrality_and_perspective.md
|
|
```
|
|
|
|
When to read:
|
|
|
|
- `rules/knowledge_usage.md`: before using knowledge files for a non-trivial task, or when unsure how much to read.
|
|
- `rules/missing_and_placeholder.md`: when a file is missing, marked `[占位]`, or the knowledge base appears incomplete.
|
|
- `rules/citation_and_evidence.md`: when the answer uses knowledge-base material as evidence.
|
|
- `rules/realtime_news_usage.md`: when the task needs recent events, news facts, public-opinion developments, or source verification.
|
|
- `rules/neutrality_and_perspective.md`: when the task involves political controversy, competing claims, attribution, blame, legitimacy, or sensitive issues.
|
|
|
|
## Directory Index
|
|
|
|
Use `_MANIFEST.md` files as directory-level indexes before reading many files.
|
|
|
|
```text
|
|
entities/_MANIFEST.md # people, parties, institutions, media, foreign actors
|
|
narratives/_MANIFEST.md # political narratives and discourse frames
|
|
events/_MANIFEST.md # key events, timelines, recurring patterns
|
|
primitives/_MANIFEST.md # concepts, frameworks, methods
|
|
playbooks/_MANIFEST.md # analysis methods
|
|
reference/_MANIFEST.md # reference tables and standards
|
|
data_pointers/_MANIFEST.md # external/current material notes
|
|
routing/_MANIFEST.md # legacy detailed routing files
|
|
```
|
|
|
|
## Route By Task
|
|
|
|
Start with these broad entry points, then narrow through manifests:
|
|
|
|
```text
|
|
Background or fact lookup -> reference/_MANIFEST.md, events/_MANIFEST.md, entities/_MANIFEST.md
|
|
Speech or rhetoric analysis -> playbooks/_MANIFEST.md, narratives/_MANIFEST.md, reference/_MANIFEST.md
|
|
Cross-Strait signal analysis -> playbooks/_MANIFEST.md, narratives/_MANIFEST.md, events/_MANIFEST.md
|
|
US/Taiwan/international signal -> playbooks/_MANIFEST.md, narratives/_MANIFEST.md, entities/foreign_actors/_MANIFEST.md
|
|
Election or party analysis -> playbooks/_MANIFEST.md, entities/_MANIFEST.md, narratives/domestic/_MANIFEST.md
|
|
Narrative or influence analysis -> playbooks/_MANIFEST.md, narratives/_MANIFEST.md, primitives/_MANIFEST.md
|
|
Prediction or scenarios -> playbooks/_MANIFEST.md, events/_MANIFEST.md, narratives/_MANIFEST.md
|
|
```
|
|
|
|
Do not use a playbook for simple background lookup unless the user asks for analysis, interpretation, comparison, prediction, or attribution.
|
|
|
|
For multi-aspect tasks, read `playbooks/multi_playbook_orchestration.md` only after confirming that one playbook is not enough.
|
|
|
|
## Legacy Detailed Routing
|
|
|
|
If this lightweight routing is not specific enough, use the legacy routing files:
|
|
|
|
```text
|
|
routing/by_question_type.md
|
|
routing/by_topic.md
|
|
routing/by_actor.md
|
|
routing/by_event.md
|
|
routing/cross_reference_rules.md
|
|
```
|
|
|
|
These are more detailed and may point to specific entities, narratives, events, primitives, and playbooks. Use them only when manifests are not specific enough.
|
|
|
|
## Realtime Or Recent Facts
|
|
|
|
The knowledge base may be stale. For recent events, news facts, public-opinion developments, policy updates, or source verification:
|
|
|
|
1. Read `rules/realtime_news_usage.md`.
|
|
2. Use `bm25_search_news` if available.
|
|
3. Keep knowledge-base background separate from current news evidence.
|
|
|
|
## Minimal Use Pattern
|
|
|
|
```text
|
|
1. Identify whether the caller task needs knowledge-base support.
|
|
2. Read the relevant rule file if needed.
|
|
3. Use this routing file or a `_MANIFEST.md` to pick a small set of files.
|
|
4. Read only those files.
|
|
5. If a playbook is useful, read it; otherwise use knowledge files as supporting material.
|
|
6. Cite specific files when using knowledge-base material.
|
|
7. Return control to the caller skill's workflow and output format.
|
|
```
|