Semantic evaporation in software supply chains
Identity continuity and selection determinacy after verification. Draft preprint, version 0.5.
Read the damage reportStorage systems / failure engineering / unwanted operating systems
Storage opinions,
mostly unwanted.
Notes from the awkward bit between “it booted” and “we can prove it is safe.”
STATUS OPERATIONALLY SUSPICIOUSAUTHORGRUMPY STORAGE GUYDEFAULT MODESHOW RECEIPTS
Latest field notes
Writing
The Ceph cluster you never wanted
A ZFS pool needed to move six metres. The standard answer was Ceph. That was a much larger answer than the problem required.
Read the damage report![[censored]](https://grumpystorageguy.com/images/editorial-censor.png "Corporate identity confiscated by editorial policy.")
OS / 01 / SolverThere is no --force in my package manager
Why a dependency solver that can refuse a request also owes the operator a reason.
Read the damage report OS / 02 / FoundryNo package in my OS is allowed to run a script
Four deliberately pathetic actuator verbs replace arbitrary maintainer code.
Read the damage report OS / 03 / LoomThe most destructive thing my OS can do reported itself as the most innocuous
A correct solver and a correct reconciler combined to delete an operating system and print applied 0 files.
Read the damage report OS / 04 / RecoveryMy recovery command was structurally incapable of recovering
Six crash boundaries on real ZFS exposed a recovery loop that could never terminate.
Read the damage report OS / 05 / HealthBooted is not healthy
Why node-local boot success and a fleet health verdict must remain separate facts.
Read the damage reportOngoing series Building a bloody OS From constraint solver to recovery contract →“Yes, I realise how this looks. Here is the proof that I have not completely lost my mind.”