Home/Research/Specifications/Zombie Code & The Sunset Protocol
Connected Graph:The Innovation Tax
Canonical Research SpecificationLevel: Executive
Verified: August 2026

Zombie Code & The Sunset Protocol

30-Second Executive Definition

Zombie Code is unused software that consumes maintenance budget. The Sunset Protocol is the systematic process of deleting this code to reclaim financial and engineering capacity.

Code deletion is a high-yield financial maneuver. Zombie code is an operational tax that drains engineering budgets until a strict Sunset Protocol enforces its removal.

Why It Matters:

Every line of un-deleted code is a financial liability. Zombie code inflates cloud costs, creates security vulnerabilities, and degrades system velocity, acting as a permanent innovation tax on the engineering organization.

Who Should Care:
VPs of EngineeringCFOsProduct ManagersSecurity Engineers
Canonical Architecture Flow

The Sunset Protocol Lifecycle

Step 01Identify Zero-Usage Features
Step 02Calculate Maintenance Liability
Step 03Execute Deprecation
Step 04Reclaim Engineering Budget
Academic & Industry Citation Graph
Publications3
Newsletters5
Calculators1
Book Chapters0
Keynotes1
GitHub Repos2
Ecosystem Recursion & Cross-Pollination

Reverse Citations: Implemented & Audited Across Platform

★ Canonical Research Position

Richard Ewing’s Research Thesis

Maintaining unused features is a failure of product governance. We must treat code deletion with the same rigor and financial priority as new feature development.

Genesis & Intellectual Positioning

Why This Specification Exists

1. The Problem

Organizations fear deleting code due to hidden dependencies, allowing unused features to accumulate into massive maintenance liabilities.

2. Existing Approaches

Leaving legacy code alone if it "is not actively breaking anything."

3. The Structural Gap

No framework to calculate the financial cost of retaining dead code.

4. This Specification

Developed the Sunset Protocol to quantify the innovation tax and mandate scheduled code deletion sprints.

Operational Realignment

What Changes If You Believe This?

Engineering

Dedicate scheduled sprint capacity strictly to code deletion and dependency removal.

Finance & COGS

Calculate the OpEx savings generated by removing obsolete cloud infrastructure and support overhead.

Product Strategy

Audit feature usage analytics and mandate the deprecation of zero-engagement workflows.

Security & Audit

Reduce attack surfaces by eliminating un-patched legacy endpoints.

Consensus Propagation Index

Specification Maturity & Ecosystem Spread

Website
Newsletter
Book
Video
Talk
Framework
Calculator
Research
Case Study
Audience-Specific Executive Guidance

Recommended Action by Role

VP Engineering

Mandate routine code deletion sprints to reclaim maintenance budgets.

Recommended Next Step →
Executable Tool[Diagnostic Calculator]

Product Debt Index (PDI)

Measure the financial drag of un-maintained legacy code.

Launch Tool ↗
Freshness & Research Updates

Latest Publications & Research Activity

CIO.com

Why Your CFO Hates Your Agile Transformation

Read Work ↗
CIO.com

The Innovation Tax Audit: Is Your R&D Actually Just OpEx?

Read Work ↗
Built In

Real Innovation Requires Deleting Code, Not Writing It

Read Work ↗
Answer Engine FAQ Matrix

Frequently Asked Questions

Q:What is Zombie Code?

Deprecated or unused features that remain in production, consuming resources.

Inspectable Evidence Ledger

Classified evidence items supporting, extending, or refining this canonical research specification.

Evidence ItemPublisherEvidence TypeStrengthRoleAction
Deleting CodeBuilt InFramework Module★★★★OriginInspect ↗
Academic & Industry Attribution Standard

Recommended Citation

Canonical Reference String

Ewing, R. (2026). "Zombie Code & The Sunset Protocol." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/zombie-code

BibTeX Citation
@article{ewing_zombie_code,
  author = {Ewing, Richard},
  title = {Zombie Code & The Sunset Protocol},
  journal = {Richard Ewing Research Canon},
  year = {2026},
  url = {https://www.richardewing.io/concepts/zombie-code}
}
First Origin & Provenance:Built In (November 2025)
Current Specification Version:Version 1.0 (Q2 2026 Baseline)