# Systems Architecture

**High-Level Design Philosophy**

Kredo follows a **stateless-user architecture**:

* Users do not exist as stored entities on-chain
* No addresses are associated with permissions
* No balances are tracked per user

All persistent state belongs to the system, not individuals.

**Core Architectural Components**

**1. Liquidity Fog Pool Layer**\
Manages pooled capital and enforces invariant rules for liquidity usage.

**2. Authorization Policy Layer**\
Defines global and contextual rules governing spending permissions, limits, and constraints.

**3. Zero-Knowledge Proof Verifier**\
Validates user-generated proofs asserting compliance with authorization policies.

**4. Intent Execution Engine**\
Processes spending intents and releases liquidity when proofs are valid.

**5. Governance & Policy Registry**\
Allows controlled evolution of authorization standards without touching user-level state.

**Stateless On-Chain Execution**

When a payment occurs:

* No user account is referenced
* No balance is updated
* No address is debited

The chain only verifies:

* Proof validity
* Policy compliance
* Pool solvency
* One-time intent execution

This dramatically reduces on-chain complexity while increasing expressive power at the authorization layer.