Flow diagram of the various inscriptions used by GeneratOrd
The basic principal behind GeneratOrd is that instead of inscribing each image in your collection, you inscribe each trait, and then each image is constructed from these traits using Java Script code that is inscribed on chain. In order to make this work several inscriptions are required.
GeneratOrd is designed so that the Processor, Default Renderer and Fallback Renderer are identical for all collections. This means you don't need to inscribe these files, as they are already pre-inscribed.
#### Metadata
The metadata contains all the inscription ID's for all the traits in your collection, as well as which traits are in each image. This data is compressed by default to reduce inscription fees, however if you would rather it be readable, you can choose for it to not be compressed.
#### Collection
The actual collection consists of a number of HTML files. There could be thousands of these depending on the size of the collection. These are incredibly simple files, and all they do is reference the Config file.
Each file also has a Token ID in it, which is simply a number indicating which item it is in the collection, and is used in conjunction with the metadata do determine which traits should be displayed.
#### Config
The Config is a JavaScript file that contains certain configuration details about your collection. This includes information such as the inscription ID of your metadata, the pixel size of your images, and if they are pixelated or not. This information is then given to the Processor.
#### Processor
The processor is the 'heart' of GeneratOrd. It loads your metadata and decompresses it. It then retrieves the Token ID, stored in the HTML file, and uses that to extract inscription ID's for the traits of this image from the metadata. Finally the trait inscription ID's are given to the Default Renderer.
#### Default Renderer
The Default Renderer uses the inscription ID's provided by the processor to load all the traits for the given image. It then combines all of these into a single image and displays it. Importantly, it actually combines the traits into a single image, rather than simply layering the traits on top of each other. This means that you can right click save the image as you would with a normal image.
#### Fallback Renderer
At this stage, this is not used in by the GeneratOrd website, however it will be used in the future for delayed reveal collections and custom renderers (see [Planned Features](/planned-features.md)).
---
# 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.generatord.io/readme/how-does-generatord-work.md?ask=
```
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.