> 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/cloud-infrastructure/1-version-history.md).

# 1 Version History

<table><thead><tr><th width="137">Version</th><th width="239">Author</th><th>Comments</th></tr></thead><tbody><tr><td>0.8</td><td>Kurt Garloff, Friederike Zelke, Maximilian Wolfs, Artem Goncharov</td><td>Key Functionality; Functional Requirements (ch. 6); Data structures (ch. 7) and APIs (ch. 8); Internal workflows (ch. 9) and architecture block diagram; use short data structure for server creation as example; Review and small corrections in chapters 6, 7, 8</td></tr><tr><td>0.9</td><td>Kurt Garloff</td><td>Add AZs and Regions. Token revocation. Floating IPs. Move IAM topics into an own section in chapter 6. Better describe flavors. Move user-data support and consumption into chapter 6. Require log analysis. Mention possible orchestration services with declarative API for IaaS. Scheduling (anti-)affinity for containers. Added optional billing and audit exposure for customers. Add Reference to OpenID Connect specs. Add example data structure for container deployment. Add example OpenAPI spec for status page.</td></tr><tr><td>1.0<br><sup><em>September 2024</em></sup></td><td>Kurt Garloff, Nico Lück</td><td>Formatting changes; Incorporation of feedback from Kristo Vaher, Ott Sarv, Sreepathy H Vardarajan to specific requirements in chapter 4-6 and for future considerations (v1.X and v2)</td></tr><tr><td>1.0.1<br><sup><em>February 2026</em></sup></td><td>Kurt Garloff</td><td>Cosmetic: Fix architecture image underlines; add back missing half-sentence on security upgrades, indent IAM items correctly, clarify two-layer multi-tenancy. PR <a href="https://github.com/GovStackWorkingGroup/bb-cloud-infrastructure-hosting/pull/3">#3</a></td></tr></tbody></table>


---

# 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://specs.govstack.global/cloud-infrastructure/1-version-history.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.