> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/implementation-playbook/0.9.0/govstack-implementation-playbook/1-version-history/release-notes.md).

# Release notes

## Version for TAC review - November 2022

The version for the Technical Advisory Committee (TAC) is an **early version** of the GovStack Implementation Playbook that contains major features under each section and has been released to TAC panel members, pilot countries' digital teams, and the organic public that reach the GovStack website, Govstack GitHub and GovStack community of practices for initial comments and feedback.&#x20;

This **early version** will allow the GovStack team **to test:**&#x20;

* Content structure and relevance
* Digital service co-design standard and delivery protocols
* Ease of use of the tools and methods included in each section
* Graphics and diagrams that explain key concepts&#x20;

As we move forward with the TAC review process and pilot reference implementations, the content will be updated constantly. Bare with us in this initial version and give us feedback! We are committed to active revision of comments and make every iteration of the playbook better.&#x20;

##


---

# 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://specs.govstack.global/implementation-playbook/0.9.0/govstack-implementation-playbook/1-version-history/release-notes.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.
