The Knowledge Base in the web workspace stores institutional knowledge: conventions, architectural decisions, and runbooks. It provides context so team members and agent runs stay aligned with repository rules.

## Structure of an entry

- **One topic per entry**: Split entries that cover multiple concerns so context retrieval remains focused.
- **Clear summaries**: Lead with direct statements rather than background history.
- **Tags**: Use consistent tags (e.g. `architecture`, `testing`, `auth`) to organize entries across projects.

## Managing entries

You can create, edit, and categorize entries directly in the web workspace Knowledge Base. Each entry belongs to your organization and can be linked to specific projects.

## Recommended practices

1. **Concrete rules**: Document actual commands, paths, and patterns instead of general guidelines.
2. **Deduplication**: When conventions evolve, update existing entries to prevent conflicting instructions.
3. **Auditability**: Significant convention changes should be documented so past agent runs remain interpretable.