> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/ecosystem-components/tokenization/participation-and-distribution-model.md).

# Participation & Distribution Model

The Participation & Distribution Model defines how users engage with tokenized structures and how value is allocated within these systems.

Within the Sweep ecosystem, participation is structured through defined units that represent positions inside a broader value framework. Users interact with these structures by acquiring or engaging with these units, which determine their level of participation within the system.

Rather than relying on fixed or static outcomes, value allocation follows a **predefined distribution logic** embedded within each structure. This ensures that all outcomes are generated according to transparent and consistent rules.

### **Participation Framework**

Participation is based on structured entry into tokenized systems:

* Users interact with defined units within a structure
* Each unit represents a measurable position
* Participation is flexible and can scale across different structures

This approach enables broader access while maintaining a consistent framework for how users engage with value.

### **Distribution Logic**

Value within each structure is allocated based on system-defined parameters:

* Distribution rules are established at the structure level
* Allocation follows predefined conditions
* Outcomes are generated without manual intervention

This ensures that value flow remains predictable, transparent, and aligned with the system’s logic.

### **Dynamic Allocation**

Unlike static distribution models, Sweep supports dynamic allocation mechanisms:

* Value distribution can be influenced by system performance or activity
* Allocation structures can adapt to different conditions
* Participation and outcomes remain interconnected

This creates a system where value is not fixed, but continuously shaped by the underlying structure.

### **Consistency Across Structures**

Although structures may differ in design, the underlying principles remain consistent:

* Participation is measurable
* Distribution follows predefined logic
* Outcomes are generated within a structured framework

This consistency allows users to engage with different systems while maintaining a clear understanding of how participation translates into outcomes.

### **Transparent Value Flow**

All participation and distribution processes are designed to be observable and verifiable:

* Rules are defined in advance
* Execution follows system logic
* Outcomes can be traced within the system

This reinforces trust by ensuring that value allocation is not subject to hidden or discretionary processes.


---

# 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://docs.sweep.finance/ecosystem-components/tokenization/participation-and-distribution-model.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.
