2026-presentInfrastructure engineeringOwner and operator
Private platform engineering
The problem
The costly failures were silent: dynamically allocated addresses reclaiming pinned slots after restarts, bind-mounted files staying on old inodes, and sign-in routes selecting the wrong provider. The configuration could still render cleanly while the running system was already wrong.
Decisions
Private platform engineeringDecision 1 of 4
Decision
Treat Compose as a dependency graph: pin released images by version and manifest digest, document startup order, and keep live authority explicit.
Consequence
Every image update becomes a deliberate edit. Nothing moves forward on its own, including security updates.
Private platform engineeringDecision 2 of 4
Decision
Turn network allocation and sign-in routing incidents into two tree-wide analyzers backed by 28 unit tests.
Consequence
The analyzers only catch the failure classes already understood; a new class stays invisible until someone writes its analyzer.
Private platform engineeringDecision 3 of 4
Decision
Put production automation behind scoped identities, typed API routes, command allowlists, signed reviews, 46 allow and deny cases, and two network guards.
Consequence
Routine work now has to pass the guards, and a legitimate change can be refused by them.
Private platform engineeringDecision 4 of 4
Decision
Route logs, metrics, and traces through one collector; define backup verification and off-host restore as explicit acceptance work.
Consequence
Recovery is stated as written verification criteria rather than a single availability figure, which is harder to summarise.
Outcome
Known network and sign-in misconfigurations now fail before commit, while the automation surface is exercised through positive and negative tests. Three-signal telemetry is configured, and recovery has written verification and restore criteria instead of an uptime claim.
Evidence and scope
Private repository snapshot verified on 19 August 2026. The case covers platform controls across four hosts, but its metrics exclude 22 separately owned or project stacks. No public source is available. Provider and host identifiers, domains, addresses, subnets, exact paths, physical role assignments, service inventory, and third-party, client, or family workloads are omitted.