Utils Unification

Consolidate duplicated utility helpers by applying an extraction decision tree to search existing logic, reuse canonical utilities, or extract new shared helpers only when reuse is justified, ensuring consistent alignment with screaming architecture.

Classify shared utilities by distinguishing feature, domain, framework, and core categories, placing them where their meaning is clearest while obeying dependency direction rules to maintain discoverability and prevent architectural drift.

Extract new shared logic only when reuse is justified. Follow decision-tree guidance to search for existing logic first, reuse or extend canonical utilities, and audit duplication before creating new shared helpers to prevent utility drift.

Audit utility duplication and dependency violations by following a governance workflow that includes duplication auditing, testing seam guidance, and dependency tracking with visited-tracker discipline to keep utility drift in check.

Yes, this utility refactoring approach supports testing seams and shared logic governance by providing decision-tree extraction, screaming architecture placement, and visited tracker discipline to maintain consistent testing boundaries.