Identity | Who they are: role, location, affiliation (slow-changing) | “Manik works at Red Planet” | Role, company, background |
Knowledge | What they know: expertise, skills, understanding | ”Expert in TypeScript and React” | Skill level, technical depth |
Belief | Why they think that way: values, opinions, reasoning | ”Values simplicity over complexity in code” | Design and architectural reasoning |
Preference | How they want things: likes, dislikes, style choices | ”Prefers pnpm over npm” | Tooling, style, setup choices |
Habit | What they do regularly: recurring behaviors, routines | ”Reviews PRs every morning before standup” | Routines, recurring workflows |
Goal | What they want to achieve: future targets, aims | ”Launch MVP by Q2 2026” | Planning, prioritization |
Task | One-time commitments: follow-ups, promises, action items | ”Send the contract draft to Sarah by Friday” | Open action items, follow-ups |
Directive | Rules and automation: always do X, notify when Y, remind me to Z | ”Always run tests before creating a PR” | Enforced rules and triggers |
Decision | Choices made, conclusions reached | ”Chose Neo4j for graph storage because of traversal performance” | Past choices and their reasoning |
Event | Specific occurrences with timestamps | ”Started auth refactor on Jan 15, 2026” | Temporal queries |
Problem | Blockers, issues, challenges | ”Hit rate limits with GitHub API when syncing 50+ repos” | Debugging, constraint planning |
Relationship | Connections between people | ”Works with Sarah on CORE project” | Team and collaborator graph |