Team Coordination - Shared Context Across Your Team
How it actually works
When multiple team members work on the same project, they all share the same project vault. When any session seals, that knowledge propagates to all active sessions on the project.
"Specialists" means focused sessions working in their domain - not separate AI instances automatically assembled by fai. A session focused on testing sees the same project vault as a session focused on architecture. They share decisions, patterns, and context through the vault.
What You See
You: "Refactor the authentication system to use JWT instead of sessions"
AI: "Working on your refactor..."
A few minutes later:
AI: "Done. Here's what changed:
- Auth middleware updated (JWT verification)
- Session cleanup removed
- Token refresh endpoint added
- Tests updated (all passing)
- Migration guide generated for existing users"
Your AI worked through this using all the context in your workbench - your patterns, your testing style, your documentation conventions. Everything it needed was already there.
What you experience with a team
- Start a session focused on testing
- Another team member starts a session focused on architecture
- When they seal, their architectural decisions appear in your testing session
- Your test patterns flow into their architectural context
Knowledge flows through the vault, not through AI-to-AI communication.
When It Triggers
Every sealed session contributes to the shared project vault. The more your team works, the richer the shared context becomes.
- One person working: Session knowledge accumulates in your project vault
- Team working in parallel: Each sealed session adds to shared knowledge
- Cross-domain work: Architecture decisions inform testing, testing patterns inform architecture
The right context for the right task - from accumulated shared knowledge.