> For the complete documentation index, see [llms.txt](https://circular-protocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circular-protocol.gitbook.io/whitepaper/circular-protocol-architecture/auto-progressive-sharding.md). # Auto-Progressive Sharding Circular is designed to support a performance-aware sharding model in which participating nodes may be grouped into subnets based on observed capability signals such as compute capacity (CPU/GPU) and network connectivity. Lower-index subnets are intended to accommodate lower-capability nodes, while higher-index subnets are intended to support higher-capability nodes. Under this model, all nodes can participate in validation and block production, while subnet assignment helps prevent the slowest nodes from constraining overall throughput. Subnet membership and sizing are expected to be governed by protocol parameters and may be adjusted dynamically as nodes join or leave the network. Throughput characteristics depend on implementation details, network conditions, and the number and quality of participating nodes. Any performance figures referenced elsewhere in this document should be treated as indicative targets, not guarantees, and may change as the network evolves. --- # 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://circular-protocol.gitbook.io/whitepaper/circular-protocol-architecture/auto-progressive-sharding.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.