# Overview

{% hint style="success" %} <sub>You can read this chapter in one coffee if you walk the pages in the order below. You will leave with named owners, not vibes.</sub>
{% endhint %}

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

<table><thead><tr><th width="329">This chapter is</th><th>This chapter is not</th></tr></thead><tbody><tr><td><sub>Plain language for founders and operators</sub></td><td><sub>A substitute for your employment agreements or SOC policies</sub></td></tr><tr><td><sub>A map of who fixes what when smoke appears</sub></td><td><sub>A promise that every Test will always be green</sub></td></tr></tbody></table>

<h2 align="center"><sub>Read in this order</sub></h2>

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

[Vendor accounts](broken://pages/079e23514ad7e68c2c43f1585b9843122cd77e55) so billing and admin seats have faces.
{% endstep %}

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

[Repositories and deploy artifacts](broken://pages/4d21e8dbbda4131aa514ac74ec558fc573668893) so nobody “inherits” mystery repos.
{% endstep %}

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

[Notion pages and sharing](broken://pages/885e6c17ee2835bdaf7e3c6f67e7662d548004e0) so truth has a home humans can audit.
{% endstep %}
{% endstepper %}

<h2 align="center"><sub>Ask a question</sub></h2>

<p align="center"><sub><strong>Which integration, if mis-owned, becomes a silent single point of failure?</strong></sub> <br><sub>Put a name and a calendar reminder on it this week.</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/ownership-and-responsibility/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.