An order asks for a specific entity (meal/plant) with a quantity and sometimes a quality requirement, and pays money + reputation when fulfilled. Some orders repeat.
Order model
| Field | Meaning | Evidence |
|---|---|---|
| Order ID | Unique reference | STRUCTURED |
| Club / café | Which source sent it | PARTIAL |
| Requested entity | Meal or plant | PARTIAL |
| Quantity / quality | How many, min quality | PARTIAL |
| Rewards | Money + reputation | PARTIAL — per transaction |
| Repeatable | Can recur | PARTIAL |
Transaction separation
The economy model treats club orders, café/market and direct sale as separate transaction types — they pay differently. The money page explains each.
The order data schema is live; values are filled per current-version verification. Nothing here is estimated.
Quest-critical orders (like epic salads for the Atrium) are blocked progress points on launch week — tracked in quest and troubleshooting records.
Orders share records with recipes, reputation and money — one dataset, many views.