> For the complete documentation index, see [llms.txt](https://docs.vishwalab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vishwalab.com/architecture.md).

# 3. Architecture

Every action follows the same path - intent, gateway, control layer, execution - and only a passing check reaches a signature.

![Vishwa verification path - intent to execution](https://2581884455-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiKtwuXgGckbrnwJbKNtR%2Fuploads%2FpNpd2gk414KDEU8MUOx4%2Fvishwa-verification-path.png?alt=media)

*Vishwa verification path - intent to execution*

The agent sends an unsigned request to the Vishwa gateway. The control layer verifies it inside a hardware enclave in under 100 ms, using its own market data, then either signs and settles or denies it before anything irreversible happens.

## The three checks

| Check               | Question it answers                                 | Example constraint                                                   |
| ------------------- | --------------------------------------------------- | -------------------------------------------------------------------- |
| Authorization       | Is this agent allowed this operation on this venue? | Buy and sell only, never transfer out; Polymarket only               |
| Solvency and limits | Is it within caps, and do real balances cover it?   | $20 per trade, $100 per day, $1,000 per month; collateral thresholds |
| Execution fidelity  | Is the price within tolerance of the live market?   | 2% max slippage, oracle deviation bounds, routing conditions         |

## Constraint policy

A policy is the owner's rulebook, sealed in the TEE. It defines authorized agents and their allowed operations; per-operation limits (`per_tx_usd`, `daily_usd`, `monthly_usd`, `approved_venues`, `max_slippage`); and global constraints, including an account-wide daily limit and a rate limit on operations per minute to stop runaway loops.

## Private state

Vishwa treats sensitive context as something to minimize, not collect. Three principles apply: data minimization, confidential compute, and verifiable handoff - proving a request is valid without exposing the state behind it. Selective disclosure lets an institution show an auditor that a mandate was respected without revealing the full book.

## Proofs and audit trail

Each decision follows an intent, policy, execution, record sequence. Executed actions return on-chain transaction signatures; decisions are rolled into weekly ZK batch proofs verifiable on-chain. Verification costs roughly 210,000-280,000 gas per proof.
