# Work/Personal Separation

Separate work and personal knowledge domains so they can be managed, backed up, and accessed independently.

The core idea is to define domain boundaries in the knowledge configuration -- a `work` domain and a `personal` domain, each with their own directory trees, distillation rules, and access controls. Your PA would route observations to the correct domain based on context clues (project names, time of day, explicit tags).

This matters when you want to back up personal notes without including work IP, or share work knowledge with a team without exposing personal data. It also helps the PA avoid cross-contaminating contexts -- your meal planning knowledge should not surface during code review sessions.

Open questions: how to handle items that span both domains, whether to use separate git branches or separate directories, and how distillation should merge or keep separate.