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

# Technical Architecture

Core Components

* **Frontend Dashboard**: A responsive web interface for user interactions, built for simplicity.
* **Python Backend**: Handles verification logic, including OCR, facial recognition, and OTP validation.
* **Rust Backend**: Manages blockchain updates and NFT generation with secure signing.
* **Kafka Messaging**: Ensures reliable, asynchronous communication between backends.
* **Walrus Storage**: Provides decentralized, encrypted storage for sensitive documents.

**Architecture Flow**

1. Users submit documents and selfies via the frontend.
2. The Python backend processes verification and sends results to Kafka.
3. The Rust backend consumes Kafka messages, signs data, and updates the blockchain contract.
4. Encrypted documents are stored in Walrus, and NFTs are issued to users.

This modular architecture ensures scalability, security, and a seamless user experience.


---

# 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://suiverify.gitbook.io/suiverify/technical-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.