KEEL

24 notes filed under KEEL, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.

codename KEEL · 24 notes · 24 themes · all codenames

all themes alert-delivery 1 backup-and-restore 1 bootstrap-ordering 1 certificate-issuance 1 certificate-lifecycle 1 declarative-imperative-gap 1 drift-detection 1 exposure-defaults 1 identity-services 1 incident-tooling 1 leadership-naming 1 lockout-safe-provisioning 1 machine-identity 1 mail-and-webmail 1 migration 1 one-writer 1 posture 1 redundancy-judgement 1 reproducibility 1 scheduled-jobs 1 secret-delivery 1 service-discovery 1 storage-layout 1 verification-design 1

KEEL · drift-detection · 2 min read

the replacement inherited the configuration and not the habits

When new machines are built to replace an old one, the old one becomes the reference, and the comparison that matters is not between files. A parity audit set the retiring member against the freshly built replacements, and the configuration…

read

elsewhere

Other codenames

Each codename is a project. The theme is the class of problem the note is about — the same theme recurs across projects, which is usually the interesting part.

ABACUS 60 FLINT 12 KEEL 24 LARDER 24 LATTICE 36 MERIDIAN 24 MISE 24 SCRIBE 12 TROUPE 12 UMBRA 24 browse 244 themes

KEEL

KEEL notes

the replacement inherited the configuration and not the habits

Other codenames