# Interpreting Results

Every decision cycle produces a structured record. Understanding these records is essential for monitoring RaxBot's behavior and verifying that it operates within your mandate.

***

#### Decision Record Fields <a href="#id-552a4e94-49da-4e60-85c2-c51eb83b712a" id="id-552a4e94-49da-4e60-85c2-c51eb83b712a"></a>

**Type** — The category of decision: hold, rebalance, emergency\_stop, or pending\_approval.

**Status** — Whether the decision was executed, is awaiting approval, was rejected, or completed as a hold.

**Current Allocation** — The vault's allocation at the time of the decision.

**Proposed Allocation** — The allocation RaxBot recommends, if a change is warranted.

**Current Risk Score** — The overall risk score at evaluation time, on a 0-100 scale.

**Expected Risk Change** — How much the risk score would change if the proposal were executed. Negative values mean risk would decrease.

**Compliance Check** — The result of validating the proposal against all mandate constraints. Lists any violations or warnings.

**Rationale** — A human-readable explanation of why the decision was made.

**Execution Details** — For on-chain executions: transaction hash, block number, gas used, and explorer link. For simulated executions: marked as simulated.

***

#### Reading Compliance Results <a href="#id-6b835737-6a52-45ba-8ecc-716af6712d34" id="id-6b835737-6a52-45ba-8ecc-716af6712d34"></a>

**Violations** are hard failures that block execution. Common violations: risk score exceeds mandate maximum, single protocol exceeds exposure limit, liquid assets below threshold, protocol not on allowlist, capital movement exceeds per-rebalance limit.

**Warnings** indicate approaching limits without blocking execution.

***

#### When to Intervene <a href="#d90ed42f-5bdb-485f-822f-6f9358811bc2" id="d90ed42f-5bdb-485f-822f-6f9358811bc2"></a>

Manual intervention is appropriate when: repeated rejected proposals suggest the mandate is too restrictive, emergency stops require review before unpausing, pending approvals accumulate, or the rationale describes conditions you want to respond to differently.

The correct response is always adjusting the mandate — not overriding individual decisions.


---

# Agent Instructions: 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:

```
GET https://docs.raxprotocol.xyz/raxbot-coming-q3-26/interpreting-results.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.