MANAGING THE KNOWLEDGE BASE

Avoid duplicated content

A principle should not exist in multiple files written in different ways.

For example:

SOURCE_POLICY.md

should be the single primary source that defines how sources are used.

Other files do not need to restate the same policy.

Principle:

One important matter → one primary source of truth.

Handling contradictions

If there are multiple versions, it must be clearly stated which version is in effect.

For example:

VERSION: 2.1

STATUS: ACTIVE

UPDATED: 2026-08-14

REPLACES: 2.0

Do not let the Agent decide which document is newer.

Versioning

Important Knowledge should have a version.

Document: Research Methodology

Version: 1.4

Status: Active

Updated: 2026-08-14

When making changes:

CHANGELOG

v1.4

• Added Source Verification.
• Changed the workflow from 4 steps to 5 steps.

Versioning lets you know:

• which method the Agent is using;
• which change altered the output;
• when a rollback is needed.

Static Knowledge and Dynamic Data

Should stay in the KB

• framework;
• methodology;
• principles;
• policy;
• glossary;
• standards.

Should come from Data / Tools

• prices;
• news;
• exchange rates;
• new reports;
• order status;
• customer data;
• current operational data.

Principle:

Stable knowledge → Knowledge. Changing information → Data / Tools.