> For the complete documentation index, see [llms.txt](https://help.kenyalaw.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.kenyalaw.org/legislation/tracking-history-of-legislation.md).
# Track legislation history
Legislation changes over time. This platform makes it easy to understand the history of legislation and what amendments have been applied.
## How to track amendments to legislation
1. Look for a list of amending legislation at the beginning of the document below the title.
2. Click the **History tab** on a document to view the lifecycle of a piece of legislation.
The legislations or statutory instruments displayed here, are linked.
3. Click on the **Related documents** tab to view a list of statutes that the current document amends, repeals, or is amended by. This section also provides details on the amending legislation and statutory instruments associated with the document.
## Tips!
Pay attention to the banner notification, which indicates whether the amendments to the document you are viewing have been applied. If the amendments have not yet been incorporated, you can find the amending document under the **History** or **Related documents** tabs.
---
# 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.kenyalaw.org/legislation/tracking-history-of-legislation.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 `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.
.png?alt=media)
