subsystem-removal-checklist

To safely remove a subsystem, you must first map its public surface and entrypoints, then prune code and rehome imports to prevent broken references across multi-package ecosystems.

Decommissioning a subsystem requires adjusting API contracts, updating documentation and tests to reflect the new state, and running validation gates to ensure stability and prevent drifting contracts.

Use a removal checklist during decommissioning, refactoring, or modularization across repositories with public surfaces to prevent broken imports, stale docs, and drifting API contracts.

Prevent stale documentation by updating docs to reflect the new system state immediately after code removal, ensuring all references to the decommissioned subsystem's entrypoints are pruned.

Yes, removing subsystems across multi-package ecosystems requires identifying public surfaces, managing re-exports, and enforcing validation gates to preserve stability and prevent broken builds.

Mapping a public surface involves identifying all entrypoints, CLI commands, exports, and documentation references to prevent orphaned references during subsystem removal and maintain a coherent surface.