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

# How AutoCap Works?

AutoCap operates through **discrete allocation rounds**. Each round defines a self-contained accounting period during which on-chain economic activity is measured, and DataCap is distributed.

Each round is parameterized by:

* A fixed start time and end time
* A registration fee, paid in FIL
* A fixed total DataCap (DC) pool to be allocated at the end of the round

#### Round Lifecycle

Each round progresses through three protocol phases:

1. **Registration**\
   Participants explicitly register for the round by paying the registration fee.
2. **Contribution and On-Chain activity**\
   During the active window of the round, participants generate on-chain economic activity. Contributions are measured through FIL burned via the settlement of Filecoin Pay rails.
3. **Allocation and Distribution**\
   At the end of the round, the total DC pool is distributed proportionally to participants based on their relative contribution during the round.

Throughout the round, AutoCap provides continuous, real-time observability into participant contributions and provisional allocation outcomes via the [dashboard](https://filautocap.xyz/).

#### Round Independence

Rounds are independent of one another. Activity in one round does not carry over to subsequent rounds, and participants must register separately for each round they wish to join.

This design ensures:

* Clear accounting boundaries
* Deterministic allocation outcomes
* No retroactive effects across rounds


---

# 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://lucas-documentation.gitbook.io/docs/how-it-works.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.