Enterprise and Teams

Your company's knowledge shouldn't live in people's heads or scattered across AI conversations on platforms you don't control. Yanai transforms individual context into organizational intelligence — owned by your company, not any one platform or person.


The Enterprise Problem

Organizations face three persistent knowledge challenges:

  1. Knowledge is trapped — Critical information lives in one person's head, or locked inside their Claude/ChatGPT history. Other teams don't know it exists, let alone how to access it.
  2. Churn destroys context — When someone leaves, their knowledge leaves with them. Onboarding their replacement means months of rediscovery.
  3. Context switching costs compound — Engineers interrupt each other for context. Account executives can't quickly find the status of a deal their colleague is managing.

Yanai solves all three by making individual knowledge automatically flow into the collective — under your organization's control.

How It Works

The Knowledge Hierarchy

ā”Œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”
│     Organization Memory     │  ← Company-wide knowledge (yours)
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│  Team Memory (Engineering)  │  ← Team-level knowledge
│  Team Memory (Sales)        │
│  Team Memory (Product)      │
ā”œā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”¤
│  Individual Work Aspects    │  ← What each person knows
│  (Alice, Bob, Carol, ...)   │
ā””ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”˜

Knowledge flows bottom-up:

  1. Individuals store knowledge in their work aspects through daily AI interactions
  2. Team memories are consolidated from team members' individual knowledge, filtered for team-level relevance
  3. Parent team memories aggregate from child teams
  4. Organization memory consolidates from top-level teams

At each level, AI filtering ensures only relevant, valuable knowledge propagates upward. A developer's personal debugging notes don't clutter the org memory — but their architectural decision about a critical migration does.

Automatic Consolidation

The propagation pipeline runs automatically on a regular schedule (every 6 hours by default). You don't need to do anything — just use your AI tools normally and the system handles the rest.

Each consolidation step uses AI to:

  • Extract the most broadly relevant knowledge from the level below
  • Summarize and deduplicate overlapping information
  • Filter out personal or low-value content
  • Preserve attribution and provenance

Teams

Recursive Team Hierarchy

Yanai supports arbitrary team nesting:

Engineering
ā”œā”€ā”€ Backend Team
│   ā”œā”€ā”€ API Squad
│   └── Infrastructure Squad
ā”œā”€ā”€ Frontend Team
└── Mobile Team

Teams use materialized paths for efficient hierarchy queries — no recursive database queries needed. Every team can have child teams, and knowledge flows up through the entire tree.

Team Memory

Each team has a consolidated team memory — an AI-generated summary of the collective knowledge of its members. Team memory answers questions like:

  • "How does our payment processing pipeline work?"
  • "What architectural decisions has the Infrastructure Squad made recently?"
  • "What's the current state of the Mobile Team's release pipeline?"

Team members can access their team's consolidated memory (and ancestor team memories) through org-scoped MCP sessions.

Scoped Access

Yanai enforces hard boundaries between personal and organizational data:

Personal Scope

  • Sees only personal aspects and memories
  • Cannot access team or org data
  • Used for individual productivity (personal projects, hobbies, general knowledge)

Organization Scope

  • Sees only org-owned aspects, team memories, and org memory
  • Cannot access personal data
  • Used for work tasks that benefit from collective knowledge

These scopes are set during OAuth authorization and enforced at the token level. There is no way for a personal-scoped session to access org data or vice versa. Your personal context stays personal — always.

AI Chat

For organizations, Yanai provides an AI Chat feature that queries across the entire knowledge hierarchy:

  1. Individual search results — Specific memories from the asking user's work aspect
  2. Aspect summaries — High-level overviews of knowledge areas
  3. Team memories — Consolidated knowledge from the user's teams
  4. Organization memory — Company-wide knowledge
  5. Member identity — The AI knows who is asking (name, role, department, teams) for personalized responses

When the AI answers a question, it also:

  • Extracts new knowledge from the conversation using AI-powered analysis
  • Stores extracted knowledge to the user's individual work aspect
  • Lets the consolidation pipeline promote valuable knowledge upward through teams to the org

Every chat conversation makes the organization smarter — without anyone doing extra work.

Churn Protection

When an employee leaves, their individual work aspect remains within the organization. The knowledge they contributed to team and org memories persists. Yanai also supports explicit departed knowledge consolidation — a process that extracts and preserves the most valuable knowledge from a departing member's context.

The result: institutional knowledge survives employee transitions. New team members benefit from the accumulated understanding of everyone who came before them. Your company's brain doesn't walk out the door.

Use Cases

Engineering Teams

  • "How does our payment processing pipeline work?" → Answer drawn from 3 engineers' combined context
  • "What was the rationale for choosing Kafka over RabbitMQ?" → Retrieved from a decision made 8 months ago by someone who's since moved teams
  • New engineer onboarding — AI has full context on architecture, conventions, and tribal knowledge from day one

Sales Teams

  • "What's the current status of the Acme Corp deal?" → Retrieved from the account executive's stored context
  • "What objections did we handle in similar enterprise deals?" → Cross-referenced from multiple team members' experience

Leadership

  • "What are the biggest technical risks across engineering right now?" → Aggregated from team-level knowledge
  • "How has our infrastructure strategy evolved this year?" → Historical context showing the progression

Getting Started with Enterprise

  1. Create your organization on yanai.ai
  2. Invite team members and organize them into teams
  3. Have everyone connect their AI tools with org-scoped sessions
  4. Use AI tools normally — knowledge flows automatically
  5. Check org and team memories periodically to see the collective intelligence building

The system is zero-maintenance by design. The more your team uses AI tools connected to Yanai, the smarter the organization becomes — and that intelligence belongs to you.