> For the complete documentation index, see [llms.txt](https://docs.architect.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.architect.co/user-guide/futures-101/symbology.md).

# Symbology

Futures symbology is the naming convention that futures symbols use. Traditionally, there are two parts:

* **Symbol Root**\
  The Symbol Root is generally a few characters at the start that identify the type of futures contract you're trading. This is sometimes called a Futures Stem or Contract Code, and sometimes can vary across platforms. Some examples are GC for Gold futures, ES for E-Mini S\&P 500 futures, and CL for Crude Oil futures. See[Example of Available Products](/user-guide/futures-101/example-of-available-products.md) for a full list.
* **Contract Expiration**\
  The Contract Expiration shows when the future will expire. Traditionally the Month will be represented by a single letter:

  * January - F
  * February - G
  * March - H
  * April - J
  * May - K
  * June - M
  * July - N
  * August - Q
  * September - U
  * October - V
  * November - X
  * December - Z

  Followed by the expiration year as a single digit, e.g. 4 to represent 2024. <br>

So as an example, for the E-Mini S\&P 500 future (ES) expiring in December (Z) 2024 (4), the full symbol is ESZ4.&#x20;

In Architect, futures are categorized by their symbol root as well as the full expiration date.&#x20;

Additionally, Futures Spreads and Event Contracts contain further details that specify the relevant details of those trading instruments.&#x20;


---

# 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.architect.co/user-guide/futures-101/symbology.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.