Step 6 of 6

Diagnose the agent identity, active policy, proposed action, and available evidence before changing anything.

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

Agent or wallet mismatch

What you see: the wrong policy, an unexpected agent, or a wallet that is missing from the agent record.

What to do: compare the proposing wallet with every wallet associated with the agent. Correct the registration through the dashboard. Do not reuse another agent's credential.

An older policy is still active

What you see: the verdict cites an earlier version or a recent edit does not affect the result.

What to do: open policy history, confirm the intended version, and activate the reviewed configuration before sending a new controlled action.

The action is unsupported or malformed

What you see: the action cannot be decoded, or its venue, network, contract, or function does not match the configured context.

What to do: verify the action shape and exact identifiers. Rebuild the action for a supported scope rather than broadening the policy.

Required data is unavailable

What you see: the verdict reports unavailable or stale evidence.

What to do: identify the affected dependency, wait for usable data, and retry only when the action can be evaluated. Unavailable data is not approval.

For Hyperliquid, inspect the returned mark source and freshness. A missing or stale trusted mark blocks notional, outflow, leverage, and exposure evaluation; it does not prove that a configured cap was exceeded.

Asset identity cannot be resolved

What you see: reasonCode: "asset_identity_unresolved" before an ordinary asset-universe result.

What to do: confirm the EVM chain ID and token contract address, or the Hyperliquid market and selected network. This code means Guardian could not establish trusted identity; it is not evidence that the asset was outside the allowlist.

A reduce-only close is rejected

What you see: a reduce-only Hyperliquid order is blocked even though the side check is exempt or not_checked.

What to do: inspect the other checks. The side exemption does not bypass asset, execution-price, per-transaction, rolling outflow, leverage, exposure, or data requirements. A missing mark can fail closed, and gross close notional can consume outflow headroom. Do not turn off reduce-only or widen the side policy as a workaround.

No activity appears

What you see: the dashboard has no record after the agent proposes an action.

What to do: verify the workspace, agent identity, wallet, credential, and active policy without printing the secret. Use the request identifier, timestamp, agent name, and redacted evidence when escalating.

Safety rules during investigation

• Keep missing, pending, and rejected actions paused.
• Never bypass Nava Guardian to work around a verdict.
• Never weaken sanctions controls to make an action pass.
• Never paste a full agent API key into logs, tickets, source control, or chat.
• Change one scoped policy setting at a time and verify the next verdict.