> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thig.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How It All Fits Together

> A visual overview of how thig.ai's features connect — projects, workspaces, AI memory, and more

# How It All Fits Together

thig.ai has several interconnected systems. This page gives you the mental model; the deep-dive pages explain each relationship in detail.

## The Big Picture

```mermaid theme={null}
graph TD
    ORG["🏢 Organization"]

    ORG --> WS["👥 Team Workspaces"]
    ORG --> PROJ["📁 Projects"]
    ORG --> TPL["📋 Templates"]
    ORG --> SKB["📚 Shared Knowledge Base"]

    WS -->|"groups"| PROJ
    TPL -->|"creates"| PROJ

    PROJ --> STD["Standard Projects"]
    PROJ --> PROD["Product Projects"]
    PROD -->|"links to"| STD

    PROJ --> CHAT["💬 AI Chat"]
    CHAT --> PRD["📄 Generated PRD"]

    CHAT -->|"reads from"| CTX["🧠 AI Context Layer"]
    CHAT -->|"writes to"| CTX

    CTX --> MEM["AI Memory<br/>(per-user preferences)"]
    CTX --> PKB["Project KB<br/>(per-project docs)"]
    CTX --> SKB
    CTX --> PROFILE["User Profile<br/>(role, company, style)"]

    PRD --> EXPORT["📤 Export / Share"]
    PRD --> REVIEW["✅ Stakeholder Review"]

    style CTX fill:#10B981,color:#fff
    style CHAT fill:#059669,color:#fff
```

## Three Things to Understand

<CardGroup cols={3}>
  <Card title="Organizing Work" icon="folder-tree" href="/user-guide/organizing-work">
    **Projects** are individual PRDs. **Workspaces** group projects by team. **Portfolio** shows product hierarchies. None of these affect permissions.
  </Card>

  <Card title="How AI Gets Smart" icon="brain" href="/user-guide/how-ai-context-works">
    Every chat message is enriched with **4 layers of context**: your profile, AI memories, knowledge base files, and conversation history. AI learns from every conversation.
  </Card>

  <Card title="Templates → Projects" icon="arrow-right" href="/user-guide/templates">
    Templates define PRD structure and AI behavior. When you start a project from a template, the structure is copied. The AI follows the template's guidance during chat.
  </Card>
</CardGroup>

***

## Quick Reference: What Goes Where

| I want to...                        | Use this                                  | Where                                                     |
| ----------------------------------- | ----------------------------------------- | --------------------------------------------------------- |
| Create a PRD for a feature          | **Project** (Standard)                    | `/admin/projects` → New Project                           |
| Group features under one initiative | **Product Project** + linked sub-features | `/admin/projects` → Portfolio tab                         |
| Organize projects by squad          | **Team Workspace**                        | `/admin/teams`                                            |
| Store reference docs for AI         | **Shared Knowledge Base**                 | `/admin/shared-kb`                                        |
| Let AI learn my preferences         | **AI Memory** (automatic)                 | Happens during chat; manage at `/admin/settings/memories` |
| Define a reusable PRD structure     | **Template**                              | `/admin/templates`                                        |
| Get external sign-off on a PRD      | **Stakeholder Review** via share link     | Share button on any project                               |

***

## Quick Reference: KB vs. AI Memory

This is the most common point of confusion. They're **two separate systems**:

|                | Knowledge Base                        | AI Memory                                      |
| -------------- | ------------------------------------- | ---------------------------------------------- |
| **Stores**     | Documents, facts, specs               | Preferences, decisions, style                  |
| **Scope**      | Organization-wide                     | Per-user                                       |
| **Created by** | Manual upload + auto-save             | AI extracts from conversations                 |
| **Used for**   | Factual context ("our API uses REST") | Personalization ("user prefers bullet points") |
| **Manage at**  | `/admin/shared-kb`                    | `/admin/settings/memories`                     |

**Rule of thumb:** If it's a fact about your company → Knowledge Base. If it's a preference about how you work → AI Memory.

<Tip>
  Read [How AI Gets Smart](/user-guide/how-ai-context-works) for the full picture of how both systems feed into every AI conversation.
</Tip>

***

## Common Workflows

### Starting a new PRD

<Steps>
  <Step title="Pick a template">
    Browse marketplace or org templates. The template defines PRD structure and AI behavior.
  </Step>

  <Step title="Chat with AI">
    AI asks questions guided by the template. Your profile, memories, and KB context are automatically applied behind the scenes.
  </Step>

  <Step title="Upload context (optional)">
    Drop in competitor analysis, user research, or specs. They become part of the project's KB.
  </Step>

  <Step title="Generate PRD">
    AI uses conversation + all context layers to generate a structured document.
  </Step>

  <Step title="Review, share, export">
    Edit in the rich editor, get AI coaching, share with stakeholders, export to PDF/DOCX/Notion.
  </Step>
</Steps>

### Organizing work across teams

<Steps>
  <Step title="Create workspaces">
    One per squad or department (e.g., "Mobile", "Platform", "Growth").
  </Step>

  <Step title="Assign projects">
    Link existing projects to the relevant workspace.
  </Step>

  <Step title="Create product hierarchy">
    Make parent "Product" projects, then link feature projects as sub-features.
  </Step>

  <Step title="Use Portfolio view">
    Switch to Portfolio tab on Projects page. Filter by workspace to see each team's products and progress.
  </Step>
</Steps>

### Teaching the AI about your company

| Approach                | Best for                                  | How                                                              |
| ----------------------- | ----------------------------------------- | ---------------------------------------------------------------- |
| **Add to Shared KB**    | Facts (tech stack, processes, guidelines) | `/admin/shared-kb` → create folder → add files                   |
| **Let AI Memory learn** | Preferences (style, detail level, tone)   | Just mention it during conversations — AI extracts automatically |
| **Both**                | Most teams use both                       | KB for reference docs, Memory for personal style                 |