# Citation And Evidence Rules

Use this file when knowledge-base material supports an answer, analysis, decision, or recommendation.

## Core Rule

When using knowledge-base content, cite or name the specific file. Do not write only "the knowledge base says".

## Evidence Types

Keep these categories separate:

- **Knowledge-base background**: local Markdown files under `/mnt/knowledge`.
- **Current news evidence**: results from `bm25_search_news` or user-provided current materials.
- **User-provided material**: documents, prompts, screenshots, URLs, or files supplied in the conversation.
- **Model inference**: reasoning based on the above sources.

## How To Refer To Knowledge Files

For concise answers, a file-level reference is enough:

```markdown
依据 `entities/parties/dpp_overview.md` 和 `events/key_events/event_2024_election_three_way.md`，...
```

For higher-stakes or contested claims, be more specific:

```markdown
这一点来自 `playbooks/uncertainty_communication_protocol.md` 中关于信心度表达的规则。
```

## Do Not Over-Cite

Do not turn every sentence into a citation. Cite when the file materially supports:

- A factual statement.
- A definition.
- A timeline point.
- A framework choice.
- A confidence or uncertainty judgment.
- A disputed interpretation.

## Claims And Support

Use this discipline:

```text
Fact      -> needs a file, news source, or user material.
Context   -> can use knowledge-base background.
Inference -> must be labeled as inference.
Forecast  -> must include uncertainty.
Gap       -> must be explicitly marked.
```

## Conflict Handling

If files conflict:

1. State the conflict.
2. Prefer more specific, more recent, or higher-credibility material.
3. If recency matters, use `bm25_search_news`.
4. Mark residual uncertainty.

## Realtime News Links

For news-search results, use visible Markdown links in the final answer when available. Do not replace inline evidence with a bare source list at the end.