> For the complete documentation index, see [llms.txt](https://documentations.seclea.com/nist-ai-risk-management-framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentations.seclea.com/nist-ai-risk-management-framework/map-3-ai-benefits-and-costs/map-3.3-ai-application-scope.md).

# MAP 3.3 - AI Application Scope

NIST AI RMF (in the playbook companion) states:

> ### MAP 3.3 
>
> Targeted application scope is specified, narrowed, and documented based on established context and AI system classification. <br>
>
> <details>
>
> <summary><strong>About</strong></summary>
>
> \
> Systems that function in a narrow scope tend to enable better mapping, measurement, and management of risks in the learning or decision-making tasks and the system context. A narrow application scope also helps ease oversight functions and related resources within an organization.
>
> For example, open-ended chatbot systems that interact with the public on the internet have a large number of risks that may be difficult to map, measure, and manage due to the variability from both the decision-making task and the operational context. Instead, a task-specific chatbot utilizing templated responses that follow a defined “user journey” is a scope that can be more easily mapped, measured and managed.
>
> </details>
>
> <details>
>
> <summary><strong>Actions</strong></summary>
>
> * Consider narrowing contexts for system deployment, including factors related to:
>   * How outcomes may directly or indirectly impact users and stakeholders.
>   * Length of time the system is deployed in between re-trainings.
>   * Geographical regions in which the system operates.
> * Engage AI actors from legal and procurement functions when specifying target application scope.
>
> </details>
>
> <details>
>
> <summary><strong>Transparency and Documentation</strong></summary>
>
> \
> **Organizations can document the following:**
>
> * To what extent has the entity clearly defined technical specifications and requirements for the AI system?
> * How do the technical specifications and requirements align with the AI system’s goals and objectives?
>
> </details>


---

# 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://documentations.seclea.com/nist-ai-risk-management-framework/map-3-ai-benefits-and-costs/map-3.3-ai-application-scope.md?ask=<question>&goal=<endgoal>
```

`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.