persist

To save decisions and notes from conversations into a knowledge base, this Skill identifies and persists candidate items like facts and plans directly into the Ouroboros KB. It applies upsert semantics based on type, project, and title to maintain a clean, searchable repository.

The best way to capture project facts and plans discussed in chats is to apply this workflow across project discussions, which extracts enduring information and stores it with searchable fields. You simply tell the AI to persist the current conversation to the knowledge base.

Upserting conversation records into a knowledge base works by matching content based on type, project, and title to avoid duplicates. When you persist decisions or notes, the Skill updates existing KB entries if they match or creates new ones to ensure accurate knowledge retention.

You can persist decisions from current conversations without creating duplicate knowledge base entries because the Skill uses upsertable KB entries governed by type, project, and title. This ensures important context is preserved cleanly without redundant records across chats.

Yes, you need access to the current conversation to upsert notes into the Ouroboros knowledge base. The Skill requires this access to identify candidate items such as relations and plans, applying upsert semantics to store searchable fields and human-readable notes.

You can persist decisions, facts, notes, relations, and plans from discussions to a knowledge base. The Skill captures these specific candidate items from your conversations, storing them with searchable fields and human-readable notes for reuse across projects and teams.