> For the complete documentation index, see [llms.txt](https://cattoverse-1.gitbook.io/cattoverse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cattoverse-1.gitbook.io/cattoverse/introduction/trust-and-safety-architecture.md).

# Trust and Safety Architecture

Autonomy without safety is not a product. It is a liability.

Catto's trust model is built on four non-negotiable principles:

#### 1. Always Non-Custodial

Catto never holds private keys. All execution flows through wallet-native signing. User funds remain under the user's cryptographic control at all times.

#### 2. Explicit Permission Scoping

Every autonomous capability requires explicit user authorization. Catto cannot self-expand its execution boundaries. You define the scope; Catto operates within it.

#### 3. Full Execution Transparency

Every agent action is logged, timestamped, and visible in the user's activity history. Nothing happens silently.

#### 4. Staged Autonomy

The default state is always the most conservative configuration. Users must actively expand Catto's autonomy level. The system is never aggressive by default.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cattoverse-1.gitbook.io/cattoverse/introduction/trust-and-safety-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.