CrewAI

CrewAI crews should map each role to a distinct UnifiedMemory actor. This keeps researcher, coder, reviewer, and ops working memory separate while still allowing approved canonical facts to be shared.

Pattern

• Issue one scoped key per crew role or bind each role to a stable agent_id.
• Use pre-task recall for role-specific context.
• Use post-task writeback for final decisions, completed tool outcomes, and reusable project facts.
• Use explicit handoff summaries instead of transcript inheritance.

Safety

Do not let one role request agent_scope=all. Admin/operator visibility belongs in Ops routes, not prompt context.