> For the complete documentation index, see [llms.txt](https://docs.amoeba.farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amoeba.farm/reference/04-products-indexes-buckets.md).

# Products, Indexes, and Buckets

Amoeba markets start with product definitions.

The oracle can only produce a useful movement if the thing being measured is defined carefully. Product definitions should be narrow enough to compare movement, but not so narrow that the market has no usable source set.

## Product bucket

A bucket is a standardized product category. For memory markets, a bucket may include:

* product standard;
* generation;
* capacity;
* grade;
* condition;
* region or market environment;
* quote convention;
* delivery or listing convention.

Examples may include DRAM module categories, NAND flash gauges, channel-market SSD gauges, or embedded NAND gauges.

## Basket weight vs. source weight

These two weights do different jobs.

| Weight type   | What it controls                                      | When it changes                                          |
| ------------- | ----------------------------------------------------- | -------------------------------------------------------- |
| Basket weight | The economic meaning of the product index.            | Only through a published product-version process.        |
| Source weight | The influence of one accepted source inside a bucket. | Formed before the live period and frozen for that month. |

Changing basket weights changes the product. Changing source weights changes the oracle recipe. Neither should change silently inside a live contract.

## Product version

Every live market should point to a product version.

A product version should publish:

* bucket definitions;
* basket weights;
* source category rules;
* oracle calendar;
* settlement window;
* payoff family;
* risk disclosures.

The public rule is simple: a contract knows its recipe before users trade it.

## Early product families

Public names such as RAMX, NANDX, or composite hardware baskets should be used only when the final definitions are published. Until then, docs should describe them as product families or examples, not final live market specs.


---

# 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.amoeba.farm/reference/04-products-indexes-buckets.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.