> For the complete documentation index, see [llms.txt](https://docs.taptap3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taptap3d.com/concepts/records-and-outputs.md).

# Records and outputs

Organisations, events, lots, assets and catalogues in the Taptap3D record model.

Taptap3D separates the inventory record from the document that presents it. A catalogue is an output of those records, not a separate copy of the inventory.

| Entity       | Meaning                                                                       |
| ------------ | ----------------------------------------------------------------------------- |
| Organisation | The business that owns the records and defines its field policy.              |
| Membership   | A user's association with an organisation.                                    |
| Event        | A group of records associated with a sale, exhibition or other project.       |
| Lot          | An inventory record within an event. The auction-first UI uses the term lot.  |
| Asset        | An image or other stored file associated with the work.                       |
| Catalogue    | A document derived from an event's records, with its own layout and audience. |

## Stable identity

A record's identity must not depend on its page number, position in a grid or sale order. Those can change during editing.

Presentation corrections are associated with the lot and field. A pin records an arrangement by its members. This allows a catalogue to change density or order without treating every visual element as a new object.

## Import provenance

An import records where data came from and which mapping was approved. Importing a spreadsheet is a review step: suggested mappings are not silently committed.

For an integration, preserve that distinction between source data and an approved public representation. A listing should not be a dump of the source row.

## A catalogue and a listing

The catalogue workflow derives a layout and produces a PDF. The planned listing projection will derive a public representation of the same record with its approved images.

The listing is not implemented yet. Its proposed contract is documented under [Listing contract](/proposed-reference/listing-contract.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taptap3d.com/concepts/records-and-outputs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.