# Context-Separation Checklist for a Personal AI Assistant
# Source: https://agntc.work/blog/personal-ai-assistant-work-and-personal-life/

# Context-Separation Checklist

## Before connecting anything
- [ ] List every account the assistant can reach, one world per list: work, personal
- [ ] Assign each account to exactly one world. If unsure, treat it as work
- [ ] Confirm the employer's policy in writing before any work account is connected
- [ ] Check what a workspace merge or account link moves, and whether it is reversible

## Walls
- [ ] Separate credentials per world, with no shared tokens or shared API keys
- [ ] Crossing between profiles is refused by the tool, not by the model remembering
- [ ] No shared memory store between worlds. Summaries crossing manually are reviewed first

## Bridge rules, if you build one
- [ ] Every fact that may cross has a named scope and one direction
- [ ] Facts are minimal: availability, not reasons. Patterns, not events
- [ ] Every crossing is logged on both sides, queryable in one place
- [ ] Every scope is revocable, and derived data expires with the scope
- [ ] Consent scopes are reviewed monthly, and unused scopes are removed

## Red lines, never cross
- [ ] No financial details into work channels
- [ ] No work documents into personal tools without written policy approval
- [ ] No health or family details into employer systems
- [ ] No untrusted content (email, web pages) processed where it can trigger actions on the other world

## Test it quarterly
- [ ] Ask the work assistant what it knows about your private life. The answer should list only bridged facts
- [ ] Try to make the personal assistant act in a work channel. It should refuse loudly
- [ ] Revoke one scope and verify the other side stops using the derived data
- [ ] Read the crossing log. Anything surprising becomes a removed scope