# Storage Format

#### File and File Name Format:

* All tournament summaries *MUST* be stored in plain text files.
* All tournament summary files *MUST* have an .OTS file extension.
* Filenames *MUST* use only ASCII characters.

{% hint style="info" %}
Other than the above requirements, hand history filenames can be named anything.  We recommend including at least the tournament name in the filename.
{% endhint %}

#### Tournament Summary Groupings per File

A tournament summary should be written to the tournament player's local computer as soon as the player busts from a tournament and there should be one [tournament summary JSON object](/less-than-standardized_tournament_summary-greater-than/less-than-standardized_tournament_summary-greater-than.md) per file.  All of the information for the tournament, that is relevant to the tournament player should be available at that time.

If multiple tournament summaries are requested by a user at a later date then multiple tournament summaries can be included in a single file.  When multiple tournament summaries are included in a single file, each [tournament summary JSON object](/less-than-standardized_tournament_summary-greater-than/less-than-standardized_tournament_summary-greater-than.md) *MUST* be separated by one blank line such as:

```
{"ots":<standardized_tournament_summary_object_1>}

{"ots":<standardized_tournament_summary_object_2>}

{"ots":<standardized_tournament_summary_object_3>}
```

{% hint style="warning" %}
If multiple tournament summaries are included in a single file, the resulting file will not be considered "valid" JSON.  However, for this standard, it is considered acceptable.
{% endhint %}


---

# 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://ts-specs.handhistory.org/storage-format.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.