Find Duplicate Ownership

Overview

Audit the codebase for multiply-owned rules instead of blindly grepping normalize. Classify each case as real SSOT drift, local dedupe cleanup, legitimate boundary work, or legitimate domain constraint.

Workflow

1. Define the audit target before searching. Narrow by feature, contract, package, service, or file slice when possible. Good targets: session state, persistence contracts, runtime geometry, provider options, path helpers, JSON canonicalization.

2. Build a taxonomy first. Use these buckets:

   • architecture / SSOT bug: same business rule owned in more than one layer
   • local dedupe cleanup: same helper semantics copied nearby
   • legitimate boundary adapter: wire, vendor, or untrusted input transformation with one clear owner
   • legitimate domain constraint: runtime clamp, math, security, or path logic that cannot be removed architecturally