Rolling upgrade

Locked

There is no certified public sequence for upgrading a Monolythium operator fleet. Historical host order, timing, quorum assumptions, flags, and rollback commands are not a production runbook.

A future upgrade guide must be bound to exact signed releases and the selected registered network identity. It must define compatibility, health gates, maximum simultaneous disruption, state migration, rollback, incident authority, and a rehearsal using value-less infrastructure. Every stage must require explicit operator approval and independently observable success criteria.

Public operator enrollment is not available; the development testnet remains Foundation operated, value-less, and resettable.