It only takes one combination to start the chain reaction. If someone identifies one combination of kernel, disk driver, file system, hardware, and syscalls that results in reliable durability then people who care about reliable durability will start using it, and that will eventually turn into a de facto standard which will eventually turn into an actual standard.
Until someone who doesn't care changes some code and that pattern is no longer durable.
All of it - these things aren't straightforward, you need to go knee-deep in this area of programming to have a good hnderstanding of it.