> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/genesis-overview.md). # Genesis overview Autify Genesis helps QA teams use AI to streamline tasks such as test design and specification generation. Work in Genesis is organized into **workspaces**, which you can create and manage by product or use case. Inside a workspace, **Resources and Context**, the **AI Assistant**, **Spaces**, and **Workflows** work together to support QA work. ## Workspace A workspace is the unit where you manage resources such as product source code, specifications, and design documents, and where you run AI-assisted QA work. You can create multiple workspaces within an organization and manage them by product or use case. ### Workspace structure A workspace consists of the following four areas. | Area | Description | | ------------------------- | ------------------------------------------------------------------------------------------------- | | **Resources and Context** | Manage the resources the AI can reference by connecting GitHub repositories and uploading files. | | **AI Assistant** | Ask questions in natural language and request tasks using the resources in the workspace. | | **Spaces** | Manage structured QA data such as test cases, feature lists, and scenarios in typed tables. | | **Workflow** | Run and manage AI workflows such as automatic generation of PRDs, specifications, and test cases. | ## Resources and context Resources and Context is the knowledge base that helps the AI understand your specifications and code correctly. You can register **files** such as specifications, design documents, and test plans, as well as **codebases** connected from GitHub or uploaded as ZIP files. Registered resources are indexed and used as context when the **AI Assistant** and **Workflows** perform tasks. ## AI Assistant The AI Assistant is a conversational AI feature that works while referring to registered **resources**. It can answer questions about your workspace based on specifications and implementation details, and can help with tasks such as drafting specifications and generating test cases. ## Spaces Spaces is a workspace tab for managing structured QA data — test cases, feature lists, scenarios — in typed, editable tables. Inside a Space, data is organized into **Collections** (typed tables of rows). You can define the columns each row contains, nest additional data with sub-collections, and view the full change history for every row. Workflows and the AI Assistant can also read and write Spaces data directly. For more details, see [About Spaces](/spaces/about-spaces.md). ## Workflow Workflows combine multiple AI agent blocks to automate more complex work processes. They use knowledge from registered **resources** together with dynamic inputs provided at runtime. This makes it possible to standardize and automate tasks such as generating test cases from specifications and summarizing documents. --- # 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://help.genesis.autify.com/genesis-overview.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.