# Social Networking Architecture

The **Social Networking** architecture of Unich Network is designed to facilitate meaningful meetings that lead to FC distribution through a three-step process: Swipe, Match, and Meet.

* **Swipe**: Users browse through other profiles based on criteria such as geographic location, shared interests, or networking goals. This process is similar to modern dating applications, providing a quick and intuitive way for users to express interest.
* **Match**: A match is created when two users mutually express interest (double opt-in). This eliminates asymmetry and creates a foundation for communication. Only when there is a match can both parties send messages and arrange a meeting.
* **Meet**: The decisive step is the real-world meeting. This is when in-app activities are transformed into actual connections and FC is distributed. When a meeting is verified (through a third-party independent location verification system), both users are distributed FC (as detailed in Section 5) and Boost (as detailed in Section 4.2)  - assets with real value that can accumulate over time.

This architecture eliminates the dark patterns found in traditional platforms. There are no provocative FOMO-inducing notifications or algorithms designed to maximize time spent on the app. Instead, the platform is designed to push users outside the app and into real-world meetings where FC distribution is activated.


---

# Agent Instructions: 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:

```
GET https://docs.unich.com/unich-network/system-architecture/social-networking-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
