> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/ai/how-ai-powers-transform.md).

# How AI Powers Transform

A practical overview of where AI shows up in Transform and how to use it.

### Overview

AI features focus on capturing context and turning it into usable delivery output.

Use this section to understand where AI appears and why it exists.

### Key Concepts

* **Meeting Notetaker**: meeting capture that generates structured notes and follow-ups
* **Console**: natural language query across Project content, returning answers with sources
* **Knowledge Management**: practices for keeping decisions and context reusable

### How It’s Used

Use Meeting Notetaker during discovery and governance meetings.

Use Console during reviews when the location of an answer is unknown.

Use Knowledge Management practices to reduce rework across Projects.

### Benefits

* Faster conversion from meeting context to requirements and tasks
* Less time spent searching for decisions and prior rationale
* More consistent governance through traceable source links

### Setup Steps

1. Confirm AI features are enabled at Account scope.
2. Confirm access roles allow content visibility for the intended audience.
3. Standardize naming for Processes, Systems, and Segments to improve query precision.

### Best Practices

* Keep decisions in comments with a consistent pattern, such as `Decision:` and `Approved by:`.
* Prefer links to source items over copying generated text into external tools.
* Use Save Views to pair AI answers with repeatable review lists.

### Summary

AI workflows:

* [Meeting Notetaker](/ai/meeting-notetaker.md)
* [Console AI Search](/ai/console-ai-search.md)
* [Knowledge Management](/ai/knowledge-management.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://help.transform.ai/ai/how-ai-powers-transform.md?ask=<question>&goal=<user_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.