Sam Rolfe
72edfec59c
'The spine' records 50+ containers across 3 hosts and a 4-host estate; the pages asserted containers 'across four hosts'. Reworded so the container count and the host count are each stated without implying a distribution the sources do not give. No metric value changed. DoD: schema valid (make validate clean), metrics still trace to the approved chip set.
1.7 KiB
1.7 KiB
id, area, level, title, claim, confidence, period, tech, metrics, artefacts, public, last_verified, tags
| id | area | level | title | claim | confidence | period | tech | metrics | artefacts | public | last_verified | tags | |||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| platform-overview | platform | 1 | Platform & Infrastructure | Runs a multi-machine NixOS and Proxmox estate — fifty-plus containers · declarative configuration · encrypted backups with a written restore runbook · and public ingress — sized to the hardware rather than the budget. | running | 2020– |
|
|
|
true | 2026-10-26 |
|
Platform & Infrastructure
Claim. Fifty or more containers on a four-host estate, configuration declared rather than hand-applied, encrypted backups on three machines with a restore runbook beside them, and one public listener at the edge.
Status. Running. Figures trace to the approved metric set and the infrastructure reference; verified 2026-10-26.
The constraint that shaped it. The runtime host is memory-bound rather than CPU-bound. Every service in this estate carries a memory cap and is bound to loopback, which is why the platform reads as engineering under constraint instead of hardware shopping.
Start here. The capability page covers what runs, where, and what was rejected.