> For the complete documentation index, see [llms.txt](https://docs.gravityblocks.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gravityblocks.xyz/marketplace/architecture.md).
# Architecture
Validators connect to Gravity through a lightweight sidecar that links the validator scheduler to the marketplace. The Connector sends transaction flow and slot lifecycle updates to Gravity, which returns the selected sequencing decisions for execution.
The validator retains full responsibility for verifying and executing transactions, voting, and broadcasting shreds. The Connector does not participate in consensus or replace the validator’s execution engine. If the external sequencing path becomes unavailable, the validator falls back gracefully to its native scheduler.
## Auction dynamics
During a validator's leader slot, Gravity broadcasts transaction flow to the connected builders and runs a series of auctions by selecting the best sequence at each round, based on the rewards they produce for the validator. The winning sequence is sent through the Connector for execution.
Each round follows the same process:
1. Gravity opens an auction round
2. Builders receive flow and submit candidate mini-blocks
3. At the round deadline, Gravity selects the highest reward submission and forwards it to the validator
4. The validator executes the winning sequence and sends back execution results
A block is therefore constructed across multiple competitive rounds during the slot, with builders competing separately for each allocation.
---
# 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.gravityblocks.xyz/marketplace/architecture.md?ask=&goal=
```
`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.