# Validate

{% hint style="success" %} <sub>You leave Validate with a</sub> <sub></sub><sub>**paper trail**</sub> <sub></sub><sub>you can show a cofounder, a mentor, or future you.</sub>
{% endhint %}

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

<table><thead><tr><th width="304.90911865234375">Validate is</th><th>Validate is not</th></tr></thead><tbody><tr><td><sub>A serious pass with staged work</sub></td><td><sub>A single button that prints “validated” without evidence</sub></td></tr><tr><td><sub>A writer to your validation page in Notion</sub></td><td><sub>A replacement for your own judgment on market risk</sub></td></tr></tbody></table>

<h3 align="center"><sub>The four stages (names you will see)</sub></h3>

<table><thead><tr><th width="254">Stage</th><th>What it means in one breath</th></tr></thead><tbody><tr><td><sub>Prepare Notion validation page</sub></td><td><sub>Workspace and Notion agree on where the report will live</sub></td></tr><tr><td><sub>P01 signal research (web)</sub></td><td><sub>Structured web research pass</sub></td></tr><tr><td><sub>Rubric plus rescore decision</sub></td><td><sub>The rubric does the disciplining, not your optimism</sub></td></tr><tr><td><sub>Write report to Notion</sub></td><td><sub>Human readable output lands where your team already works</sub></td></tr></tbody></table>

<h3 align="center"><sub>Modal contract</sub></h3>

<sub>**Validation pipeline**</sub> <sub></sub><sub>uses the same family of rules as Discover:</sub>

* <sub>Steps are enumerated so you can speak them out loud on a call.</sub>
* <sub>**Closing the window does not stop validation.**</sub> <sub></sub><sub>If you need focus elsewhere, fine. If you need the run to stop, use the product controls meant for that job, not the close button as a superstition.</sub>

{% hint style="warning" %}
If Notion saved the report but ARIA did not store DB history, the product surfaces a specific notice. Treat that as an operator alert, not as “ignore it.”
{% endhint %}

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

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

<sup><sub>Validate one idea at a time when you are learning the system. Parallel runs are for teams who already know their failure modes.<sub></sup>
{% endstep %}

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

<sup><sub>If a run fails, screenshot the modal and the idea title. Narration beats memory, it will be in your personal Notion.<sub></sup>
{% endstep %}

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

<sup><sub>Re-read the written report in Notion before you declare victory in Slack. The workspace UI is the cockpit. Notion is the black box recording.<sub></sup>
{% endstep %}
{% endstepper %}

***

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

<p align="center"><sub><strong>What sentence in the Notion report would you be embarrassed to read aloud if it were wrong?</strong></sub> <br><sub>That sentence is your quality bar for the next run.</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/validate.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.
