# Introduction

Welcome to the `lens.fun` documentation. This document explains the purpose, mechanics, and goals of our project.

***

**The Problem: Signal vs. Hype**

We begin from a problem that many users in the Web3 and digital space experience: Information Overload.

It has become increasingly difficult to find high-quality, in-depth content (the "Signal") amid a constant flood of speculative, low-effort information (the "Hype" or "Noise").

This environment creates two core issues:

1. For Readers: Finding valuable analysis and "real words" becomes a time-consuming and frustrating experience.
2. For Creators: "Real Creators" who focus on substance over speculation struggle to be discovered and are often overshadowed by Hype.

**Our Mission: A Lens for Quality**

The mission of `lens.fun` is to provide a clear and effective solution to this problem. We are not building another content feed; we are building a filter.

Our entire system is designed around one guiding principle:

> "See the real words instead of hypes."

`lens.fun` is the lens designed to surface the "real insight." It is a dedicated ecosystem where the discovery and reward mechanics are structured to favor quality and substance.

In the following sections, we will detail *what* this system is, *how* it functions economically, and *who* it is designed for.


---

# 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.lens.fun/introduction.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.