# Estate-Specific Tooling Supplements

Files in this directory are **optional**. They describe how **one organisation** (or one cloud estate) maps principles to **concrete product names** and vendor documentation.

They are **not** part of the portable **principles** layer. If your estate differs, add or replace a supplement here; **do not** bake that estate’s product choices into `doctrine/principles/` unless the choice is genuinely universal.

## Relationship To Timeless Doctrine

Read [../../principles/timeless-principles-and-tooling.md](../../principles/timeless-principles-and-tooling.md) first.

## Scaffold

| File | Scope |
| --- | --- |
| [TEMPLATE.md](TEMPLATE.md) | Copy to start a new estate supplement |
| [minimum-viable-doctrine.template.md](minimum-viable-doctrine.template.md) | One-page **5–7 principle** pitch for a team (before the full library) |

## Available Supplements

| File | Scope |
| --- | --- |
| [azure-container-runtimes.md](azure-container-runtimes.md) | Example: one Azure-oriented mapping of managed application platform vs Kubernetes |
| [aws-container-runtimes.md](aws-container-runtimes.md) | Stub: fill when AWS estate has an owner |
| [gcp-container-runtimes.md](gcp-container-runtimes.md) | Stub: fill when GCP estate has an owner |
