# Overview

{% hint style="info" %} <sub>By the end of this page, you will know which numbers on Overview answer “is our pipeline breathing,” and which numbers only light up after you ship something customer facing.</sub>
{% endhint %}

<h2 align="center"><sub>This page means</sub></h2>

| <sub>A snapshot of momentum and recent motion</sub>   | <sub>A place to edit deep copy for a single idea</sub>        |
| ----------------------------------------------------- | ------------------------------------------------------------- |
| <sub>A place to refresh and sanity check totals</sub> | <sub>A spreadsheet where every cell is editable by hand</sub> |

<h3 align="center"><sub>What each block is for</sub></h3>

<table><thead><tr><th width="175.3636474609375">Surface</th><th width="299.6363525390625">What you should look for</th><th>When to worry</th></tr></thead><tbody><tr><td><sub><strong>Ideas generated</strong></sub></td><td><sub>Volume of ideas entering the system</sub></td><td><sub>Flat line for days while you believe research is running</sub></td></tr><tr><td><sub><strong>Validation rate</strong></sub></td><td><sub>How much of what you generated earns a serious pass</sub></td><td><sub>Sudden drops after you changed rubric or Notion access</sub></td></tr><tr><td><sub><strong>Ideas built</strong></sub></td><td><sub>Completed (and failed) ship tracks you started</sub></td><td><sub>“Failed” climbing without owners assigned to fix keys or templates</sub></td></tr><tr><td><sub><strong>Signup demand</strong></sub></td><td><sub>Leads coming from deployed <strong>build</strong> landing pages</sub></td><td><sub>Zero while you already launched a public URL (often DNS, form, or tracking)</sub></td></tr><tr><td><sub><strong>Revenue intelligence</strong></sub></td><td><sub>Whether billing signals are connected for live windows</sub></td><td><sub>“Not tracked” when you expected live revenue (connect billing events first)</sub></td></tr><tr><td><sub><strong>Recent build activity</strong></sub></td><td><sub>What shipped lately, with a sane link to open the app</sub></td><td><sub>Empty when you know you deployed (refresh once, then check Build)</sub></td></tr></tbody></table>

<h3 align="center"><sub>Three habits</sub></h3>

{% stepper %}
{% step %} <sub>**First**</sub>

<sub>Hit</sub> <sub></sub><sub>**Refresh**</sub> <sub></sub><sub>when you enter the page after a long meeting. Numbers are honest only when the request finishes.</sub>
{% endstep %}

{% step %} <sub>**Second**</sub>

<sub>Read hints next to KPI labels. They tell you whether the denominator is “generated,” “validated,” or “completed,” so you do not compare apples to rocks.</sub>
{% endstep %}

{% step %} <sub>**Third**</sub>

<sub>When revenue says</sub> <sub></sub><sub>**Not tracked**</sub><sub>, treat that as a</sub> <sub></sub><sub>**routing problem**</sub><sub>, not a moral judgment on your company.</sub>
{% endstep %}
{% endstepper %}

***

<h3 align="center"><sub>Ask yourself</sub> </h3>

<p align="center"><sub><strong>If you could only keep one KPI from this page for your weekly standup, which would it be and why?</strong></sub> <br><sub>Write the answer once in Notion. That single habit prevents dashboard tourism.</sub></p>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ariaagi.com/workspace/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
