# Ticketing System The Ticketing System (TS) is a supporting component in the Circular Protocol reference architecture that can provide ordering “tickets” for coordinating event sequence. A ticket consists of a UTC timestamp plus an incremental counter that increases each time a ticket is issued (and resets on a daily boundary). The purpose of TS is to help preserve a consistent sequence of events in parts of the workflow where deterministic ordering is useful, reducing the risk of improper sorting that could lead to inconsistencies. It is intended for non-critical coordination points and is designed so it does not become a throughput bottleneck. A ticket may be requested when a new transaction is created or when a new block is assembled. As a simple metaphor, the Ticketing System is similar to the number used in stores to preserve service order. Different deployments may implement this function through redundant services or equivalent mechanisms. --- # 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://circular-protocol.gitbook.io/whitepaper/circular-protocol-architecture/ticketing-system.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.