The Sunset Protocol
The Sunset Protocol is a 4-step governance framework for auditing and deleting zombie features to reclaim engineering capacity.
“Real innovation requires deleting code, not writing it.”
Software organizations suffer from an accretion bias where features are continuously added but never removed. Over time, zombie features compound testing overhead, create security attack vectors, and inflate the Product Debt Index.
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
The Sunset Protocol
The Sunset Protocol is a 4-step governance framework for auditing and deleting zombie features to reclaim engineering capacity.
Direct Relationships (3)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
Richard Ewing’s Research Thesis
We must build an institutional muscle for deleting code with the same enthusiasm we have for shipping it.
Why This Specification Exists
Companies continually add code, resulting in ballooning maintenance costs and stalled innovation.
Occasional unfunded refactoring sprints that never delete features.
No cross-functional protocol balancing customer impact, contract risk, and engineering ROI.
The Sunset Protocol establishing formal governance for code deletion.
What Changes If You Believe This?
Engineers spend less time maintaining brittle legacy code and running slow test suites.
Reallocates R&D capital from maintenance OPEX to forward-looking innovation.
Creates a leaner, higher-converting user experience with less interface clutter.
Eliminates unmaintained attack surfaces and deprecated dependencies.
Recommended Action by Role
Implement quarterly Sunset Audits to keep your feature portfolio economically viable.
Innovation Tax Calculator
Calculates the capital drag of zombie features across your R&D budget.
Frequently Asked Questions
Q:What is the Sunset Protocol?
A 4-step framework (Audit, Announce, Deprecate, Delete) designed to safely remove legacy SaaS features and reduce technical carrying costs.
Q:When should a feature be sunset?
When its direct compute COGS, support overhead, and maintenance hours exceed its customer retention value.
Canonical Specification Origin
Systematic code deletion reclaims engineering capacity.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
Recommended Citation
Ewing, R. (2026). "The Sunset Protocol." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/sunset-protocol
@article{ewing_sunset_protocol,
author = {Ewing, Richard},
title = {The Sunset Protocol},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/sunset-protocol}
}