# Recycle — Execution Flow

### Overview

A recycle operation moves through several deterministic steps executed by protocol contracts.

These operations convert native fees and accounting units into recycling activity and provider rewards.

***

### Step 1 — Inventory Provisioning

Inventory providers supply tokens through the Inventory interface.

Tokens are transferred into the ledger and converted into accounting units.

These units represent execution capacity.

***

### Step 2 — Execution Request

A user submits a recycle request through the Recycle interface.

The request specifies:

• asset\
• native service fee\
• beneficiary address

The engine calculates accounting unit consumption.

***

### Step 3 — Fee Routing

The service fee is routed through the Protocol Fee Router.

Example fee rails:

Ops rail\
Sponsor rail\
Fund rail\
Recycle rail

Each rail receives a predefined share of the service fee.

Distribution is defined using parts-per-million parameters.

***

### Step 4 — Recycling Engine Execution

The recycling engine performs several operations:

• consumes accounting units\
• updates recycling weight\
• records execution telemetry\
• allocates rewards

Example engine event:

```
Recycled(
 beneficiary,
 token,
 nativePaidWei,
 unitsConsumed,
 recycleRailWei,
 weightMinted
)
```

***

### Step 5 — Weight Accounting

The engine tracks protocol participation using a weight system.

Key variables:

```
weightOf(user)
totalWeight
```

Weight represents a participant’s share of recycling activity.

Higher participation produces greater weight allocation.

***

### Step 6 — Reward Allocation

A portion of the service fee is routed to inventory providers.

Rewards accumulate inside internal accounting balances.

Providers may withdraw these balances through the operator interface.

***

### Step 7 — Proof Reporting

The protocol allows reconstruction of recycling activity through report generation.

Reports are created using:

• contract event logs\
• ledger state reads\
• fee routing events

Available formats include:

CSV\
JSON\
HTML

Reports operate within fixed block windows to ensure deterministic reconstruction.

***

### System Guarantees

The recycling infrastructure operates under deterministic constraints.

All operations follow defined on-chain rules including:

unit conversion\
fee routing\
weight minting\
reward allocation

The interface provides proof of execution but does not create ownership, entitlement, or guarantees.

***


---

# 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.waveswaps.com/terminal-b-recycle/recycle-execution-flow.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.