> For the complete documentation index, see [llms.txt](https://docs.rakelaunch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rakelaunch.xyz/rake/security/execution-safety.md).

# Execution Safety

Echo, parser, schema, and slippage protections for RAKE money-moving execution.

## Conversation is not execution

RAKE has a conversational layer, but conversation does not set executable transaction parameters. The LLM provides conversation spice. Execution stays with the parser + schema.

```
User
    ↓
Conversational interface
    ↓
Parser + schema
    ↓
Echo confirmation
    ↓
Execution
```

The parser + schema are the source of truth for execution. The conversational model cannot bypass money verbs, infer missing amounts, or generate executable calldata.

### Money-moving actions

Echo confirmation applies to these actions:

* tip
* swap
* buy
* burn
* buyback
* bridge

### Exact confirmation

RAKE creates a draft before execution. The user must confirm the exact action and exact same amount within 180 seconds.

```
RAKE:    TIP DRAFT #184
         to @anon, asset NVDA, amount 2
         reply: @rake_agent confirm tip 184 2 NVDA

User:    @rake_agent confirm tip 184 2 NVDA
         execute

User:    @rake_agent confirm tip 184 20 NVDA
         canceled, amount differs

User:    ok
         rejected, must say "confirm"
```

| Requirement       | Result                 |
| ----------------- | ---------------------- |
| `confirm` keyword | Required for execution |
| Exact same amount | Mismatch cancels       |
| 180-second window | Timeout cancels        |

Echo is designed to address misclicks, typos, and prompt injection. It requires explicit authorization for the drafted money-moving action.

### No inferred transaction

An incomplete request cannot become executable by guessing the missing amount. The LLM cannot fill that gap or produce executable calldata.

Conversation can be flexible. Execution is constrained.


---

# 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://docs.rakelaunch.xyz/rake/security/execution-safety.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.