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

# Domain-first baseline

> Learn what Alesta can establish from a company domain and how connected or human-supplied context extends it.

A domain-first baseline is the initial company and marketing picture Alesta builds from a submitted website and the public evidence available around it. The domain is the anchor, not a claim that the public web contains every fact needed to run the business.

## Three layers of context

<CardGroup cols={3}>
  <Card title="Public evidence" icon="globe">
    Reachable pages, site metadata, lab measurements, eligible field data,
    bounded search evidence, and candidate competitor pages.
  </Card>

  <Card title="Connected evidence" icon="link">
    Private measurements from services you explicitly authorize, such as Google
    Analytics or Search Console.
  </Card>

  <Card title="Human context" icon="user-check">
    Corrections, accepted competitors, business constraints, and decisions
    supplied by workspace members.
  </Card>
</CardGroup>

These layers should remain distinguishable. A connected metric is not the same as a public observation, and a human correction should not be silently replaced by a later inference.

## What the first profiling run can establish

Subject to source availability, the free run can build:

* a working company identity and description;
* category and public social-profile context;
* mobile and desktop PageSpeed observations;
* Core Web Vitals when Google has enough eligible field data;
* homepage, on-page, and technical crawl observations;
* likely competitor candidates;
* Product information, Marketing strategy, and `llms.txt` working documents.

The exact visible result can vary by domain. A small or blocked site may support less evidence than a large, crawlable site.

## What the domain cannot prove

The baseline does not automatically know:

* revenue, pipeline, or conversion quality;
* CRM records or sales-stage definitions;
* product usage, retention, or customer sentiment;
* internal positioning decisions or launch plans;
* private analytics, advertising, or email performance;
* budgets, staffing, legal approval, or operational constraints.

Do not turn these unknowns into negative conclusions. Add or connect the relevant context when a supported capability is available.

## Why corrections matter

The company profile, accepted competitor set, and generated documents form shared working context. If the company description is wrong, downstream strategy can be wrong in a consistent way. Correct upstream context before revising every output separately.

<Steps>
  <Step title="Review observations">
    Confirm that Alesta reached the intended site and read the expected public
    pages.
  </Step>

  <Step title="Confirm interpretations">
    Check inferred category, positioning, audience, and competitor
    relationships.
  </Step>

  <Step title="Add private evidence deliberately">
    Connect a supported service only when you need the questions it can answer
    and are comfortable with the requested permissions.
  </Step>

  <Step title="Keep decisions human-controlled">
    Review documents and Signals before anything is copied, downloaded, shared,
    or written to an external system.
  </Step>
</Steps>

## References

* [What is Alesta?](/getting-started/what-is-alesta)
* [Evidence and data states](/concepts/evidence-and-data-states)
* [Company profile](/workspace/company-profile)
* [Trust and data scope](/security/trust)