> 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.md). # Version history {% hint style="success" %} Add a line to the version history table describing the major changes to the specifications between *published* versions. Ideally, include links to issues and authors on GitHub. {% endhint %}
VersionAuthorsComment
Version for TAC Review Oct 2022Same as contributors TAC review version is the first iteration of the GovStack implementation playbook with TAC panel members and digital teams in pilot countries.
May 26th 2023Same as contributorsDesign elements have been updated
Jun 15th 2023victor.martinez, felix.bellido, yolanda.martinezayush.shukla artun.gurkanNew sections have been added based on country implementation: Change management, one-stop-shop (Service catalog and CMS), Sections withing Design and delivery: Prototyping, Use cases
Nov 7th 2023yolanda.martinez, ayush.shuklaRestructuring of content in Adopt GovStack and its child pages
--- # 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.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.