> For the complete documentation index, see [llms.txt](https://rwapact.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwapact.gitbook.io/whitepaper/roadmap-and-vision/the-rwapact-vision.md).

# The RWAPACT Vision

## The RWAPACT Vision

Autonomous agents can already express intent and interact with execution infrastructure. The missing layer is deciding whether a requested RWA trade should be allowed to execute.

RWAPACT is designed to provide that decision layer. Every autonomous RWA trade should be evaluated against risk, session, policy, gas, and attestation conditions before it reaches the execution layer.

### A consistent decision boundary

RWAPACT is not another trading agent, wallet, or DEX. It is infrastructure that can sit underneath or around those systems and provide a consistent decision boundary.

```
Agent
  -> Decision Layer
  -> Execution Layer
```

The agent remains responsible for generating intent. Existing execution infrastructure remains responsible for executing the transaction. RWAPACT provides the risk and authorization boundary between them.

### The Pact as one system

The Five-Layer Pact works as a combined decision system:

| Layer | Long-term role                                     |
| ----- | -------------------------------------------------- |
| KRO   | Makes RWA-specific risk explicit.                  |
| KSO   | Makes delegated agent authority bounded.           |
| KPV   | Makes trading policy enforceable.                  |
| KGR   | Makes execution cost part of the decision context. |
| KAR   | Makes the decision auditable.                      |

These layers are not independent features. Their outputs combine before RWAPACT authorizes execution. A favorable result from one layer does not bypass the conditions evaluated by the others.

### From Execution to Decision Infrastructure

Most trading infrastructure asks:

> How should this transaction execute?

RWAPACT focuses on:

> Should this autonomous trade execute under the current risk, authority, policy, and execution conditions?

This distinction becomes more important as autonomous trading expands. Agents can submit valid transaction requests quickly. A valid request still needs RWA-specific risk context, bounded authority, enforceable policy, and an auditable decision record.

### Long-term direction

The roadmap identifies several planned expansion areas:

* Broader execution-layer integrations
* Enterprise risk services
* Cross-chain expansion

These directions extend the same decision model to more execution contexts. The roadmap does not define specific future chains or products.

> RWAPACT does not execute trades. RWAPACT decides whether a trade should execute.

The long-term goal is to make autonomous RWA trading more controlled, transparent, and auditable. Execution systems can retain their roles without rebuilding their own risk middleware.


---

# 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://rwapact.gitbook.io/whitepaper/roadmap-and-vision/the-rwapact-vision.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.