# Social Media

{% hint style="info" %} <sub>This area is explicitly a</sub> <sub></sub><sub>**preview**</sub> <sub></sub><sub>class surface in the product story. Read “preview” as: exciting, directional, not a full replacement for your native X, TikTok, or Ads managers until ARIA turns those integrations on for real.</sub>
{% endhint %}

<h3 align="center"><sub>The story in three pillars</sub></h3>

<table><thead><tr><th width="223.09088134765625">Pillar</th><th>What you get in words</th></tr></thead><tbody><tr><td><sub><strong>AI content generation</strong></sub></td><td><sub>Drafts with caps and tone rails tied to rubric language, not generic spam voice</sub></td></tr><tr><td><sub><strong>AI video generation</strong></sub></td><td><sub>Shot lists and safe aspect layouts for short video, still tied to the same signals</sub></td></tr><tr><td><sub><strong>Scheduling plus analytics</strong></sub></td><td><sub>Queue and measure with metadata that traces back to idea rows</sub></td></tr></tbody></table>

***

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

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

<sup><sub>Treat captions and hooks as legal copy adjacent. If your validation says you may not claim X, your social drafts should obey the same fence.<sub></sup>
{% endstep %}

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

<sup><sub>Approve before you queue. Automation without approval is how brands become case studies.<sub></sup>
{% endstep %}

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

<sup><sub>When integrations for networks are marked<sub></sup> <sup><sub> </sup><sup><sub>**coming soon**<sub></sup> <sup><sub> </sup><sup><sub>elsewhere in the product, believe the UI. Do not train you or your team on imaginary buttons.<sub></sup>
{% endstep %}
{% endstepper %}

***

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

<p align="center"><sub><strong>Which metric would you defend in a board meeting: views, clicks, signups, or revenue tied to an idea id?</strong></sub> <br><sub>Pick one primary. Secondary metrics are fine. Chaos is not.</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/social-media.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.