Modernization without erasure.

The replacement narrative

The loudest modernization narrative in government technology is replacement. Sunset the mainframe. Lift and shift to cloud. Rewrite the forty-year-old claims processor in a language the new team prefers. The narrative is tidy, and it is usually wrong.

What legacy actually holds

Legacy systems persist because they encode institutional knowledge that took decades to accumulate. Eligibility logic refined through thousands of edge cases. Reporting pipelines shaped by regulatory history no current staffer fully remembers. Interfaces whose peculiarities exist because some failure mode in 2003 required them.

Replace the system and you lose the knowledge. Extend it, and you keep what works.

The point

The point of modernization is not to look modern. It is to preserve the function that matters while letting the form evolve.

Eden's modernization practice draws on direct delivery experience across federal and state health and administration programs. We have watched replacements succeed, and watched replacements quietly lose capability the agency only notices a year later. The difference is almost always in what the replacement chose to carry forward.

This is why Build for the century is the companion posture to this one. Durable infrastructure and careful modernization are two faces of the same discipline: refusing to treat institutional memory as an inconvenience.