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

# Key Concepts

> Core concepts and terminology used throughout WisePilot.

Understanding these core concepts will help you get the most out of WisePilot.

## Websites (Workspaces)

A **website** is the top-level workspace in WisePilot. Everything — content, brand settings, integrations, and analytics — is scoped to a website. Each workspace operates independently with its own configuration and team access.

## Governed Generation

WisePilot uses **governed generation** — prompts are outputs, not inputs. Rather than writing prompts directly, you configure strategy (brand guidelines, ICPs, voice profiles) and the system assembles the right context for each generation task automatically.

### Context Priority

When sources conflict, the system resolves using this hierarchy:

1. **Your direct input** (highest priority)
2. **Brand guidelines**
3. **Retrieved reference content** (RAG)
4. **ICP data**
5. **System defaults** (lowest priority)

## Execution Profiles

Each content type uses an **execution profile** that determines which tools, context, rules, and validators are applied during generation. Available profiles include: `ideas`, `outline`, `conversion-page`, `long-form`, `email`, `social`, `video-script`, and `sales-enablement`.

## Content Entities

A **content entity** is any configurable AI object in your workspace — ICPs, hooks, angles, offers, stories, clusters, image styles, and brand subjects. Each entity type has:

* A **CRUD table** for creating and managing instances
* An **AI chat** for conversational refinement
* **Field schemas** that the AI follows during generation

## Asset Registry

The **asset registry** is your central content library. Every piece of generated content — blog posts, landing pages, social posts, emails — is stored as a typed asset. Assets can be edited, published, tracked, and scored.

## Attribution

WisePilot tracks visitors from content through conversion using the **Attribution ID (`cr_attrib`)**:

* A UUID assigned to each visitor session
* Follows them through CTA clicks and form submissions
* Links conversions back to the specific content and CTA that drove them

## Optimization Scoring

Each content asset receives an **optimization score** (0–100) based on:

* Weighted performance metrics (traffic, engagement, CTA clicks, conversions)
* **Confidence tier** (High/Medium/Low) based on data quality — join coverage, freshness, and sample size

## Automated Pipeline

WisePilot runs a nightly automation pipeline that keeps your data current without manual intervention:

* **Data collection** — Google Analytics, Search Console, and HighLevel data are imported automatically
* **Aggregation** — All metrics are rolled up into daily performance records per asset
* **Scoring** — Optimization scores and objectives are recalculated
* **Quality refinement** — Blog content is refined in the background minutes after generation
* **Weekly insights** — Every Monday, the system discovers content gaps, compiles performance digests, and sends growth recommendations

See [Automation & Data Freshness](/optimization/automation) for the complete schedule, expected delays, and what's manual vs. automatic.

## Content Library Resources

Your **content library** is the set of reusable building blocks that feed into generation:

| Resource     | Purpose                                            |
| ------------ | -------------------------------------------------- |
| **Hooks**    | Opening lines and attention-grabbers               |
| **Angles**   | Content perspectives tied to pain points           |
| **Offers**   | Value propositions and promotional offers          |
| **Stories**  | Case studies, testimonials, and proof points       |
| **Clusters** | Audience and topic groupings                       |
| **CTAs**     | Call-to-action templates with attribution tracking |