Skip to main content
Alesta uses panels, documents, and signals for different kinds of work. Keeping them separate makes it easier to know whether you are reading evidence, editing context, or deciding on a next step.

​
Panels

Panels are structured readings inside Analytics or competitor detail views. A panel has a title, scope, state, and source boundary. It may contain metrics, facts, lists, tables, or an explanation of why no result is available. Examples include:
  • PageSpeed scores;
  • Core Web Vitals;
  • SEO health and crawl summary;
  • observed AI visibility;
  • backlink profile;
  • traffic sources and top pages;
  • competitor changelog and pricing.
A panel can be ready, partial, locked, disconnected, unsupported, or unavailable independently of neighboring panels.

​
Documents

Documents are generated working artifacts in the Company panel. The free baseline can produce Product information, Marketing strategy, and llms.txt. Paid activation can add other documents when the current plan and run support them. Documents have their own lifecycle:
  • Preparing: queued for a stage that has not started;
  • Writing: being generated now;
  • Ready: readable and copyable;
  • Rewriting: a requested correction is running;
  • Updating: Alesta is reconciling the document after an upstream change;
  • Locked: access or generation requires another plan;
  • Unavailable: the document could not be produced;
  • Coming soon: the visible surface is not built yet.
Treat a document as an editable interpretation of the baseline, not as a source measurement.

​
Signals

Signals translate verified findings into reviewable next-step material. A signal can explain that work needs:
  • business input;
  • a codebase change;
  • service or operational access;
  • a prompt or instruction file;
  • a confirmed external action, such as creating a GitHub issue.
A signal does not automatically resolve the underlying finding. The feed exposes only the actions the server says are currently available.

​
How they relate

When a signal and an Analytics issue refer to the same finding, use Analytics to understand the evidence and Signals to review the proposed next step.

​
References