Step 4 of 6

Determine what Nava Guardian decided, which policy version it used, and what must happen before the proposed action can continue.

The preview version of Nava Guardian is verdict-only and advisory. See Execution safety for the handoff from verdict to execution.

Read the verdict in this order

1. Outcome — approved, rejected, or pending.
2. Primary reason — the most useful explanation of the decision.
3. Policy version — confirms which reviewed configuration was active.
4. Check evidence — shows the relevant pass, failure, or unavailable data.
5. Action context — identifies the agent, wallet, venue, network, asset, and time involved.

Respond to the outcome

Approved

Confirm that the action and policy version are the ones you expected. The preview verdict remains advisory; the execution handoff is described in Execution safety.

Rejected

Read the failed check and evidence. Correct the proposed action when it exceeds the intended scope. If the business requirement is legitimate, create a deliberate policy change rather than editing around the rejection.

Retrying the same deterministic action against the same policy will produce the same result.

Pending

Keep the action paused and allow the integration's bounded status workflow to complete. Do not treat an incomplete decision as approval.

Unavailable or malformed data

Verify the venue, network, action shape, addresses, and encoding. When a required dependency is unavailable, wait for usable data rather than weakening the policy.