> For the complete documentation index, see [llms.txt](https://help.ulii.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.ulii.org/legislation/glossary-of-defined-terms.md).
# Glossary of defined terms
Explore terms that have specific definitions in legislation.
The legislation glossary is an index of all the terms that are defined in legislation. The glossary makes it easy to see how the same term is defined across legislation.
## How to find the Glossary
1. Click **Legislation**
2. Under **More resources**, click **Glossary of defined terms**.
## How to use the Glossary
Use the glossary to find a specific term you are looking for, such as "youth".
1. Click the entry for the first letter of the term, such as **Y** for "youth".
2. The glossary will load.
3. Scroll down through the list of terms to find the one you are looking for.
4. Filter the terms to quickly find the one you need by typing the first few letters into the **Find a term...** box.
5. The glossary will update to show matching terms.
## Understanding an entry in the Glossary
An entry in the glossary includes:
* a definition of the term (taken from one of the pieces of legislation that defines the term); and
* a list of legislation that defines the term.
Similar definitions are grouped together.
Click **X groups of similar definitions...** to expand it and see all legislation that defines the term, and all the different definitions.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://help.ulii.org/legislation/glossary-of-defined-terms.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
