> 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/security-and-risk-model/oracle-integrity.md).

# Oracle Integrity

How oracle freshness and price context inform RWA risk evaluation and policy enforcement.

## Oracle Integrity

A risk engine is only as useful as the market information it evaluates. Incorrect or stale oracle information can materially affect an autonomous Agent's RWA trading decision.

RWAPACT accounts for oracle-related risk through KRO and KPV. KRO evaluates the available oracle context as part of the Risk Score. KPV can enforce a fresh-oracle requirement and define the acceptable risk threshold.

### Oracle-related conditions

KRO evaluates oracle staleness and price deviation as part of the RWA risk model. Oracle staleness identifies when available market information is no longer current. Price deviation identifies when price references materially diverge.

KPV provides the policy boundary around those conditions. A policy can require a fresh oracle and reject a Trade Intent that exceeds its allowed Risk Score.

| Component | Question it answers                                                            |
| --------- | ------------------------------------------------------------------------------ |
| KRO       | What is the current risk associated with the available oracle information?     |
| KPV       | Does this trade satisfy the policy requirements for oracle freshness and risk? |

This separation matters. KRO supplies the risk context. KPV decides whether that context meets the configured policy.

### Stale-oracle rejection

An Agent can request an RWA token trade while its oracle is stale. KRO can classify the trade as critically risky. The Pact can then reject the Trade Intent with a reason such as `ORACLE_STALE`.

KAR records the Rejection and its context. The trade does not reach the Execution Layer.

```
Stale oracle
  -> KRO critical risk result
  -> KPV fresh-oracle and risk requirements apply
  -> Pact Rejection
  -> KAR Attestation
```

### Scope of oracle integrity

RWAPACT can detect and enforce the oracle conditions defined by the protocol. Its Attestation records the decision and context used at evaluation time.

This does not guarantee that the underlying oracle information is correct. It records how the Pact evaluated the available information under the active policy.

***


---

# 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/security-and-risk-model/oracle-integrity.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.