# About R\&D doc section The purpose of an R\&D Doc is to explore architecture, parts, views and components for an application. This is not waterfall, it is a living and breathing doc that will evolve as the project evolves. It is focused more on the lower fidelity high level design architecture, views and components then the final UI. When possible It sketches out parts and components in language agnostic way specifying inputs and output “interfaces” and leaves technical implantation dependent on framework and language of choice to a second draft. It’s also valuable to evaluate and get feedback on implementation from others. It might also help to define a taxonomy of your system as list or diagram to define terminology used across the doc. --- # 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://autoedit.gitbook.io/documentation/transcriptions/about-r-and-d-doc-section.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.