Knowledge Base

A git-versioned collection of project context shared across all agents. The longer you use Operum, the smarter it gets.

When you create a team, Operum initializes a .operum/knowledge/ directory in your repository. Agents read this for project context before every task.

What's Stored

  • project.yaml — Project name, description, tech stack, and repository details
  • goals.yaml — Strategic and near-term goals, priorities
  • decisions.md — Architectural and technical decisions log
  • team-log.md — Agent activity log (auto-updated as agents work)
  • workflow.md — Workflow stage definitions
  • artifacts/links.yaml — Important URLs and references
Git-Versioned: The knowledge base lives in your repo and is tracked by git. Changes are automatically committed, giving you full version history.

Edit knowledge base files in-app via the Knowledge page, or directly in your editor. Changes sync automatically.

Auto-Updated

You don't need to edit team-log.md manually. Agents append to it as part of their workflow.

Editing the Knowledge Base

Two ways:

  1. In-App Editor — Navigate to the Knowledge page in Operum to edit files with a visual interface
  2. Direct File Edit — Edit the YAML/Markdown files in .operum/knowledge/ with any text editor

Changes are synced to git automatically. If you edit files directly, the app will detect changes on next refresh.

Knowledge Sync

The knowledge base supports git-based sync:

  • Pull — Fetch knowledge updates from the remote repository
  • Push — Push local knowledge changes to the remote
  • Conflict Resolution — If conflicts occur, Operum provides a resolution UI

Onboarding

When you set up a new team, the PM agent runs an onboarding conversation that populates the knowledge base with your project details: project name, description, tech stack, repository and website URLs, current goals and priorities, team conventions and coding standards. You can always edit these values later through the Knowledge page.

Best Practices

  • Keep goals current — Update goals.yaml when priorities shift
  • Record decisions — Log important technical decisions in decisions.md
  • Add useful links — Include documentation URLs, dashboards, and resources
  • Review the activity log — Check team-log.md periodically
  • Commit regularly — Keep the knowledge base in sync with your repo

What's Next?