Automating certificates for a publishing system exposed the larger migration hiding behind one change of scheme.
Blog, page 12
M31V cached articles enthusiastically, then removed the service worker when it could not explain freshness, coverage, updates, or recovery to readers.
M31V treated old URLs as maintained public identifiers, giving redirects source files, validation, preview, release identity, and retirement policy.
M31V separated build, upload, verification, and activation so an interrupted transfer could never become the public release.
M31V stopped approving an editor approximation and began reviewing the exact immutable build proposed for activation.
Promises, modules, and block scoping improved M31V only after the build stopped hiding cancellation, cleanup, and error ownership inside callbacks.
Multiplexing changed M31V’s request economics in 2015, but a large photograph still cost transfer, decoding, memory, and attention.
M31V stopped parsing articles separately for each output and built one normalized content graph that every publication surface consumed.
M31V’s build stopped handing writers stack traces and began reporting source, field, consequence, and correction in editorial language.
M31V needed editorial validation, preview, and atomic releases without inheriting a general CMS or trusting mutable uploads as a publishing protocol.
X8B6 completed its offline protocol by making every accepted operation produce a durable, queryable result that survived lost responses and repeated delivery.
Docker’s emerging image model gave X8B6 a repeatable server and database fixture, while leaving readiness, durable data, security, and lifecycle as application work.
X8B6 replaced version numbers and overwrite buttons with explanations of the local action, confirmed state, and intervening change.
X8B6’s server committed an inventory adjustment after the browser stopped waiting, turning a familiar error state into outcome unknown.
Building an offline field ledger revealed that dependable local work requires an operation log, reconciliation, and visible uncertainty.
A deterministic timestamp merge made X8B6 converge by silently erasing one legitimate inventory action, proving that conflict resolution needed domain verbs.