> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wisdom.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Context Builder - Connections
Metric definitions, business rules, and table descriptions live across GitHub repositories, dbt YAML files, Looker models, and data catalogs — and the moment any of those sources changes, your domain starts falling behind. Context Builder closes that gap by connecting your domain directly to the systems where your business logic lives, powered by WisdomAI's Adaptive Context Engine, and keeps your domain's knowledge layer automatically synchronized.
## How it works
Context Builder follows a continuous synchronization lifecycle that maps external logic updates to your active domain across four functional stages.
Navigate to your domain's Overview page, select the Context Builder option, and click Build Content. A five-step wizard guides you through: choosing a source type, authenticating, scoping the extraction to a repository or branch, setting a schedule, and validating credentials. The connection appears in your list with a **PENDING** status.
The first run performs a full scan of the connected source. Subsequent runs are incremental, processing only changes since the last extraction. When a run completes, you receive an in-app notification with the count of items requiring attention and a direct link to the review screen.
The context engine compares every incoming context object against what already exists in your domain. Conflicting entries appear side by side, so you can accept either version, write a custom merged definition, or defer. No automatic merges ever occur.
Publishing a resolved extraction increments your domain version number and makes your updated knowledge layer available immediately across chat and dashboards.
Looker and dbt projects stored in GitHub are available immediately via the GitHub connection. Atlan, Glean, and Collibra are in active development and will appear in the connection wizard as they go live.
## Connection statuses
Use the table below to understand what each status means.
| Status | Meaning |
| :------------------ | :------------------------------------------------------------- |
| **PENDING** | Connection created, waiting for the first extraction to begin. |
| **EXTRACTING** | Extraction is in progress. |
| **AWAITING REVIEW** | Extraction complete. Items are ready for your review. |
| **ACTIVE** | All items reviewed and published. |
| **ERROR** | Extraction failed. A manual re-run option is available. |
## Supported sources
Currently supports the following source types, with more integrations on the way.
| Source | Status |
| :-------------------------------------- | :------------------------------------------------------------------------ |
| GitHub (includes Looker and dbt in Git) | Available |
| Query history | Available for enabled domains. Contact your Solutions Engineer to confirm |
| Atlan, Glean, Collibra | In active development |
## Target users
Context Builder is available to **Admins** and **Domain Admins**, who connect sources, configure schedules, review extractions, and publish changes.
## User Stories
See real stories of how WisdomAI improvements are helping solve real user problems:
**Keeping Metrics Aligned After a dbt Model Refactor**
A data engineering team refactors their `revenue` model in dbt, changing the grain and updating metric definitions across three YAML files. Previously, a domain lead would only discover the discrepancy after getting a wrong answer in chat. With Context Builder, the latest incremental extraction picks up the dbt changes automatically. The domain admin receives a notification: "3 conflicts detected. ARR definition differs between dbt and existing domain." They open the side-by-side diff, accept the updated dbt definition for ARR, write a custom merged definition for one edge case, and publish. The domain reflects the new business logic before analysts start their day.
**Bootstrapping a New Domain from a GitHub Monorepo**
A new domain is being stood up for a fintech product team. Their entire metric layer lives in a GitHub monorepo: dbt YAML files, SQL pipeline configs, README documentation, and metric definitions.
Instead of manually exporting and uploading files, the domain admin connects their GitHub org via Context Builder, scopes to the relevant repositories, and triggers an initial extraction. Within the hour, 200+ context objects (metric definitions, JOIN patterns, business glossary entries, and table descriptions) surface for review. The admin bulk-approves the high-confidence entries, edits a handful of edge cases, and publishes. A domain that would have taken days of manual entry is operational by afternoon.
## FAQs
No. Every extraction goes through a human-in-the-loop review. An auto-accept option is available if you want to approve all suggestions at once, but nothing publishes without your explicit action.
Nothing is interrupted. Extraction jobs run as persistent background processes. You can return at any time and the job will still be running or waiting for review.
Open the version history panel, find the prior version, and restore it with a single confirmation step. History is append-only, nothing is ever permanently deleted.
Context Builder - File uploads is a one-time, manual flow designed for bootstrapping. Context Builder - Connections connects to the live source system, extracts automatically on a schedule, and keeps the domain continuously aligned without manual export or file handling.
The connection is removed and credentials are revoked immediately. Context already published to your domain remains in place and is not removed automatically.
## Next steps
Learn how to manually create relationships, metrics, and context in your domain.
Measure how effectively your domain's knowledge layer is producing correct answers.