> 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/use-cases/session-bound-trading.md).

# Session-Bound Trading

## Session-Bound Trading

An owner gives an autonomous agent permission to trade RWA assets during a defined session. The delegation specifies a start time, end time, budget, asset scope, and maximum trade size.

This delegation defines bounded authority. It does not grant unrestricted access to trade whenever the agent identifies an opportunity.

Without session boundaries, an agent could continue after its approved window. It could exceed its delegated budget, trade an unintended asset, or continue after revocation. KSO prevents those conditions from becoming authorized trades.

### A delegated trading session

Consider an agent with an active session. The session has a defined trading budget, a specific set of allowed RWA assets, and a maximum trade size.

The agent detects an opportunity and submits a trade intent. KSO evaluates the session before the request can continue through the Pact.

#### 1. Identity

KSO confirms the agent identity associated with the session. The request must come from the agent covered by the active delegation.

#### 2. Session Status

KSO confirms that the session is active. A revoked session cannot authorize a new trade.

#### 3. Time Window

KSO checks that the current time falls between the session start and end. An expired session prevents authorization even if other conditions pass.

#### 4. Budget

KSO verifies that the requested amount remains within the session budget. It evaluates the request against the budget remaining for that session.

#### 5. Asset Scope

KSO confirms that the requested RWA asset belongs to the session scope. Scope allows an owner to delegate authority for selected assets only.

#### 6. Maximum Trade Size

KSO confirms that the individual request does not exceed the session's configured size limit. This limit constrains each action, separately from the total session budget.

### Example: asset outside session scope

The agent's session permits Asset A and Asset B. It submits a request for Asset C.

The oracle is fresh. Liquidity is sufficient. Slippage is acceptable. Gas conditions are favorable. KSO still rejects the request because Asset C is outside the active session scope.

The request does not continue to execution. KAR can preserve the rejection context for later review.

### Session authorization and policy

Session authorization differs from policy enforcement.

KSO asks:

> Is this agent authorized to act right now?

KPV asks:

> Does this specific trade comply with the configured policy?

Both checks must pass. KSO establishes delegated authority. KPV applies trading constraints such as policy asset permissions, risk thresholds, and policy-level trade limits.

```
Session Created
  -> Active
  -> Agent Submits Trade
  -> KSO Validates Scope and Budget
  -> Continue to Pact
  -> Session Expires or Is Revoked
```

KSO does not execute a trade. It provides the session authorization result that the Pact uses before it can authorize execution.

### Why Session Boundaries Matter

Autonomous agents need bounded authority, not unrestricted access. RWAPACT makes the delegation explicit and enforceable before the trade reaches execution.

***


---

# 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/use-cases/session-bound-trading.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.