> 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/development-roadmap.md).

# Development Roadmap

## Development Roadmap

RWAPACT is planned as a progression from core risk controls to broader middleware and enterprise capabilities. Each phase extends the Pact without changing its central role as a decision boundary before execution.

| Phase   | Timeline | Deliverables                           |
| ------- | -------- | -------------------------------------- |
| Phase 1 | Q4 2026  | KRO + KPV on Robinhood Chain testnet   |
| Phase 2 | Q1 2027  | KSO + KAR integration, Uniswap v4 hook |
| Phase 3 | Q2 2027  | KGR gas router, mainnet deployment     |
| Phase 4 | Q3 2027  | MCP middleware, Robinhood API proxy    |
| Phase 5 | Q4 2027  | Enterprise API, cross-chain expansion  |

### Phase 1: risk and policy foundation

Phase 1 focuses on KRO and KPV on Robinhood Chain testnet. KRO establishes RWA-specific risk assessment. KPV establishes configurable policy enforcement.

These components form the initial Pact foundation. They evaluate whether an asset and trade request satisfy current risk and policy constraints before execution is considered.

### Phase 2: authority, records, and DEX integration

Phase 2 introduces KSO and KAR integration, alongside a Uniswap v4 hook. KSO validates session authority and delegated limits. KAR records Pact decisions and their associated context.

The Uniswap v4 hook connects risk and policy controls to a concrete execution-layer integration. The Pact can evaluate the trade before the hook allows the swap to proceed.

### Phase 3: gas conditions and mainnet deployment

Phase 3 introduces the KGR gas router and moves toward mainnet deployment. KGR adds gas and execution-path conditions to the decision flow.

This expands the Pact from risk and authorization into execution-cost optimization. KGR evaluates available conditions. It does not guarantee savings for every transaction.

### Phase 4: broader execution paths

Phase 4 adds MCP middleware and a Robinhood API proxy. These integrations extend RWAPACT beyond a direct DEX path.

MCP middleware can intercept an agent tool call before forwarding it to an execution MCP. The Robinhood API proxy can run the Pact before forwarding a trade request. Together, these paths support execution-layer agnosticism across different agent trading flows.

### Phase 5: enterprise and cross-chain expansion

Phase 5 adds the Enterprise API and cross-chain expansion. The Enterprise API extends access to RWA risk scoring capabilities for third-party applications.

Cross-chain expansion extends the planned protocol direction beyond a single execution environment. The roadmap does not specify which chains will be supported.

### Roadmap Logic

```
Risk and Policy
  -> Session and Attestation
  -> Gas Optimization
  -> Execution-Layer Expansion
  -> Enterprise and Cross-Chain Expansion
```

The sequence starts with the controls that evaluate a trade. It then adds delegated authority, durable decision records, gas-aware routing, broader execution paths, and external risk-service access.

{% hint style="info" %}
The roadmap describes the current development plan. Timelines and deliverables may evolve as implementation and testing progress.
{% endhint %}


---

# 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/development-roadmap.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.