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

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kredopay.gitbook.io/documentation/systems-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.