Keep Changes Simple

Follow KISS: Keep It Simple, Stupid. Choose the simplest clear solution that meets the actual requirement. Prefer an existing element, component, function, or mechanism over adding another layer. Do not introduce speculative infrastructure, unnecessary wrappers, files, configuration, or indirection. Keep genuinely distinct cohesive responsibilities separate; simplicity does not justify inlining a module, duplicating behavior, or weakening an established contract.

Philosophy

Solve the problem that exists with the least necessary complexity.

Correct

Put the initial busy state on the existing root element.
Reuse an existing component or mechanism when it already satisfies the requirement.

Fix

Remove unnecessary layers and use the existing mechanism when it meets the requirement. Retain separate modules only for distinct cohesive responsibilities.