> For the complete documentation index, see [llms.txt](https://docs.gdf.ai/gdf-full-stack-engineering/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gdf.ai/gdf-full-stack-engineering/intro-to-gdf-fse/why-gdf.md). # Why GDF? Generative AI tools like ChatGPT are extremely intuitive due to their conversational nature. It raises the question, why does there need to be a methodology or framework? To answer this, it is important to have the perspective that computing is just a collection of calls and responses, and language is the medium that allows call and response to communicate. Assume you go to a customer service counter and place an item on the desk. You could say the following things (the call): * *Say Nothing* * I want to buy this item * I want to return this item * I want to buy this item with my American Express, packaged in cardboard box, and delivered to 100 Little St. Big City CO via UPS Next-Day shipping at 3pm EST. * Quiero comprar este artículo con mi American Express, empaquetado en una caja de cartón y entregado en 100 Little St. Big City CO a través de UPS Next-Day shipping a las 3:00 p. m. EST. Based on what you say and what is understood by the person standing behind the counter, you could get a series of responses or a single response. The same is true with a large language model and by understanding what a large language models knows and how it understands requests will allow you to more effectively communicate with it. The purpose of GDF is not to slow down teams or individuals with yet another process, but to simply provide patterns and principles that can be implemented to whatever extent is efficient and secure. --- # 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.gdf.ai/gdf-full-stack-engineering/intro-to-gdf-fse/why-gdf.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.