> For the complete documentation index, see [llms.txt](https://docs.chaingpt.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chaingpt.org/overview/learn-the-concepts/transformer-architecture.md). # Transformer Architecture Transformer architecture refers to the specific neural network design uncovered and implemented by Google's AI team, Google Brain. Superseding its predecessor architecture known as RNN (Recurrent Neural Networks), transformer architecture is an adaptive approach to data processing. Rather than sequencing steams of information in chronological strings, transformer architectures process entire blocks of data simultaneously and substitute form factors to optimize data coherence. Rooted in identifying core concepts by accurately allocating its focus, transformer architecture displaces excessive processing by applying four components: Attention Mechanisms, Multi-head Attention, Feed-Forward Layers, and Normalization Layers. ChainGPT makes good use of the transformer architecture in the design of its AI by allowing users the ability to provide theoretically unlimited input requests and being able to handle them aptly. [**Disclaimer**](/misc/legal-docs/disclaimer.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chaingpt.org/overview/learn-the-concepts/transformer-architecture.md?ask=&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 `automate deployments from our CI pipeline` 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.