# Strategy

{% hint style="info" %} <sub>Strategy is</sub> <sub></sub><sub>**distribution planning**</sub> <sub></sub><sub>built on</sub> <sub></sub><sub>**validated inputs**</sub><sub>. It is not a generic marketing calendar unrelated to evidence.</sub>
{% endhint %}

<h3 align="center">Inputs &#x26; Outputs</h3>

<table><thead><tr><th width="130.3636474609375">Direction</th><th>What happens</th></tr></thead><tbody><tr><td><sub><strong>In</strong></sub></td><td><sub>A validated idea selection plus Notion validation context the skill can read</sub></td></tr><tr><td><sub><strong>Out</strong></sub></td><td><sub>A structured plan written to your <strong>Distribution</strong> story in Notion</sub></td></tr></tbody></table>

<h3 align="center">Sections you may see on the board</h3>

<details>

<summary><strong>Expand: Board section names (no jargon inside)</strong></summary>

<table><thead><tr><th width="215.72723388671875">Label</th><th>Reader friendly meaning</th></tr></thead><tbody><tr><td><sub>Bottleneck diagnosis</sub></td><td><sub>Where the funnel feels tight</sub></td></tr><tr><td><sub>Broken funnel stage</sub></td><td><sub>If a stage is flagged, you see targeted diagnosis</sub></td></tr><tr><td><sub>Stage diagnosis</sub></td><td><sub>Plain language about where you are stuck</sub></td></tr><tr><td><sub>First 48 hours</sub></td><td><sub>What to do immediately after you ship a message</sub></td></tr><tr><td><sub>4-step revenue loop</sub></td><td><sub>Repeatable motion, not one hero launch</sub></td></tr><tr><td><sub>Channel plan</sub></td><td><sub>Concrete channel choices tied to evidence</sub></td></tr><tr><td><sub>Kill signals</sub></td><td><sub>Early warnings that say “stop funding this path”</sub></td></tr></tbody></table>

</details>

<h3 align="center">Modal truth (one line)</h3>

<sub>**Closing the dialog does not cancel the run**</sub> <sub></sub><sub>when work continues on the automation side. Full detail still lands in Notion when the run finishes. That sentence exists so you do not confuse “quiet UI” with “quiet work.”</sub>

***

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

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

<sub>Pick one validated idea before you ask for strategy. “All ideas” is a recipe for mush.</sub>
{% endstep %}

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

<sub>When the board is empty, read the empty state once. It usually means “generate distribution,” not “mysterious outage.”</sub>
{% endstep %}

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

<sub>If regeneration is running, treat the progress dialog as the honest status surface. Refreshing the page is not a personality trait.</sub>
{% endstep %}
{% endstepper %}

***

<h3 align="center"><sub>Checkpoint question</sub></h3>

<p align="center"><sub><strong>Which channel in the plan would you personally defend with your own reputation next week?</strong></sub> <br><sub>If none, the plan is still a draft.</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/strategy.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.