# Quickstart {% hint style="success" %} _{You can teach a mate the whole workspace in one sitting if you walk the pages in the order below.} {% endhint %}

_{This page means}

| This section is | This section is not | | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | _{A map of the left rail and what each screen owes you} | _{A replacement for in-app tooltips on every field} | | _{Written for operators and founders} | _{A guarantee about third-party uptime (Notion, Stripe, and the rest have their own status pages)} |

_{The tour (read in this order on day one)}

Step	Screen	One line job
₁	_Overview	_{Command center: counts, momentum, recent motion}
₂	_Leaderboard	_{Compare operators on ships and validations}
₃	_Discover	_{Turn research into structured ideas on a board}
₄	_Validate	_{Run one idea through a serious checklist, write to Notion}
₅	_Strategy	_{Turn validation into a distribution plan}
₆	_Build	_{Ship landing surfaces with repo plus deploy}
₇	_MVP	_{Configure and ship a hosted MVP tied to a spec}
₈	_{Social Media}	_{Plan content from validated signals (preview surface)}

_{Verbal punctuation}

{% stepper %} {% step %} _**First** _{Read the title and the single description line at the top of every screen before you touch a filter or a primary button. Quiet first, loud second.} {% endstep %} {% step %} _**Second** _{When a pipeline modal opens, read the step names like a checklist. Treat the small notice at the bottom as part of the contract, not fine print.} {% endstep %} {% step %} _**Third** _{If two screens disagree, trust the on-screen error first, then your filing cabinet in Notion second.} {% endstep %} {% endstepper %} ***

_{Ask yourself}

_{Which single screen will you open tomorrow to prove the workspace is “healthy,” not just “busy”?}
_{If you cannot name it, start on Overview.}

--- # 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/quickstart.md?ask= ``` 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.