> For the complete documentation index, see [llms.txt](https://docs.unich.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unich.com/unich-network/kyc-requirements/the-principle-behind-every-case.md).

# The Principle Behind Every Case

Every case follows the same logic: FC is only as valid as the activity that produced it, and activity is only valid when both Nodes involved are verified real people. A Peer Meet between two verified Nodes produces real value. A Peer Meet where one party is unverified produces nothing the network can stand behind.

Circumventing this — through fake accounts, bot activity, or coordinated non-KYC Nodes — does not just harm the network. It directly undermines the value of every Node that participates honestly. Acting against the network's integrity is acting against the freedom of every other Node in it.


---

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

```
GET https://docs.unich.com/unich-network/kyc-requirements/the-principle-behind-every-case.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.