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

# Recommended Build Order

> The step-by-step order for building your Context Layer effectively.

The Context Layer components build on each other. Following this order ensures each step has the inputs it needs and avoids rework.

## The Order

<Steps>
  <Step title="Connect Your Data Warehouse">
    Everything starts here. [Connect your warehouse](/get-started/connect-your-data-warehouse) so ClarityQ can access your data. Configure [mandatory filters](/get-started/connect-your-data-warehouse#mandatory-filters) if needed.
  </Step>

  <Step title="Review the Table Catalog">
    After connecting, ClarityQ automatically discovers your tables and columns. Review the results, enrich descriptions, and [build entities](/context-layer/building/building-entities-from-tables) from your key tables. Daily discovery jobs will keep the catalog up to date as your schema evolves.
  </Step>

  <Step title="Set Up the Event Catalog">
    If your product tracks events, set up the Event Catalog. Run the [Missing Description Wizard](/context-layer/event-catalog/missing-description-wizard) to fill in gaps, then [sync events to the Semantic Catalog](/context-layer/event-catalog/syncing-events-to-the-semantic-catalog) so they become queryable.
  </Step>

  <Step title="Build the Semantic Catalog">
    Define your core business logic — [dimensions](/context-layer/semantic-catalog/dimensions), [metrics](/context-layer/semantic-catalog/metrics), [features](/context-layer/semantic-catalog/features), and [segments](/context-layer/semantic-catalog/segments). Start with the components your team asks about most. ClarityQ's AI agent actively helps build these using your existing definitions and data structure.
  </Step>

  <Step title="Add Memory">
    Store business rules, naming conventions, and domain context that doesn't live in your database. Start with [personal memory](/context-layer/memory) for the conventions you find yourself repeating, and add product memory as it rolls out.
  </Step>

  <Step title="Create Skills">
    Once your team has identified repeatable analysis patterns, [encode them as skills](/context-layer/skills). This is an ongoing process — add skills as new workflows emerge.
  </Step>
</Steps>

## When Can I Start Asking Questions?

You don't need to complete every step before using Ask Anything. As a rule of thumb:

| Stage                                             | What You Can Do                                                               |
| ------------------------------------------------- | ----------------------------------------------------------------------------- |
| **Table Catalog reviewed + a few entities built** | Ask basic questions about your data                                           |
| **Event Catalog synced**                          | Ask about product events and user behavior                                    |
| **Core metrics and dimensions defined**           | Ask business questions with accurate, consistent answers                      |
| **Memory added**                                  | Get answers that reflect your organization's specific context and terminology |
| **Skills created**                                | Run complex, multi-step analyses consistently                                 |

The Context Layer is a living system — keep building and refining it over time for increasingly accurate results.