ARCHIVED — moved to giga/content. Do not work here. Chapter 3 source is now chapter-3/chapter-3.md in https://git.vanillacore.net/giga/content
This repository has been archived on 2026-09-03. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
Find a file
2026-09-03 09:04:37 +02:00
chapter-3.md docs: establish Chapter 3 technical baseline 2026-08-27 15:46:33 +00:00
README.md docs: archive repository, work continues in giga/content 2026-09-03 09:04:37 +02:00
SERIES_SCOPE.md docs: establish Chapter 3 technical baseline 2026-08-27 15:46:33 +00:00

ARCHIVED — moved to giga/content

This repository is archived. Do not work here.

All chapters of the public-service cloud architecture series now live in one combined repository: https://git.vanillacore.net/giga/content

This repository's full content and commit history were migrated there. Chapter 3's source file is now chapter-3/chapter-3.md, and SERIES_SCOPE.md is now chapter-3/SERIES_SCOPE.md.

Open no issues, branches or pull requests here. Everything — edits, reviews, releases — happens in giga/content only. The content below is kept for reference only and is no longer maintained.


Technical architecture baseline and reference implementation

This repository holds the working source for Chapter 3 of the public-service cloud architecture series.

Chapter 3 follows Chapter 2. Chapter 2 gives decision makers a service-to-foundation decision frame. This chapter gives platform architects and operators a technical baseline for turning that frame into a reviewable environment.

Status

chapter-3.md is a canonical working draft, not a released implementation manual. It will be released only after the full-series audit, technical review, rendered-reader inspection and public-release controls pass.

Scope

The chapter explains general IaaS and platform capabilities first, then uses OpenStack, the Sovereign Cloud Stack and other implementations as conditional reference examples. A reference is not a product prescription or proof of sovereignty, resilience, portability or readiness.

Screenshots are included only when they evidence a stated configuration or validation step. They must be scrubbed, captioned and paired with a detailed text alternative.