Architecture Overview

A high-level guide to how Nava Guardian fits together, aimed at developers integrating with the platform.

System Diagram

Transaction Lifecycle

1. User instructs the agent. The instruction can describe the desired operation, such as swapping an asset with a defined slippage limit.
2. Agent builds an action. The agent or integrating builder constructs the structured action it proposes to submit.
3. Builder requests a verdict. The structured proposed action is sent to Nava Guardian through the documented Nava Service boundary.
4. Nava Guardian resolves policy. Nava Guardian decodes the action and resolves the active policy for the agent.
5. Nava Guardian evaluates checks. Applicable deterministic checks evaluate the decoded action against that policy. The live approval path does not use an LLM or reason over free-form intent text.
6. Nava Guardian stores and returns the verdict. Database-backed metadata tracks a pending, approved, or rejected outcome with reason codes and evidence.
7. Builder handles the verdict. The builder keeps pending actions paused, does not submit rejected actions, and may sign and submit the exact approved action through its own venue integration.

See the Nava Guardian overview for the product boundary and current Developer Preview capabilities.