connascence-guidelisted

# Connascence: a Precise Coupling Vocabulary Grade a seam by naming its worst coupling and its strongest connascence, then weaken or localize it: "tight/loose" is unactionable. ## Essentials - **Name the connascence, don't say "tight"** - classify the form and rate strength/locality/degree, see [references/connascence.md](references/connascence.md) - **Two moves: weaken and localize** - rule of degree (strong→weak forms) and rule of locality (distance→weakness), see [references/connascence.md](references/connascence.md) - **Push every seam down the coupling ladder** - content→common→control→stamp→data, worst to best, see [references/coupling-ladder.md](references/coupling-ladder.md) - **Aim for functional cohesion** - one job per module; temporal cohesion is the package-by-layer trap, see [references/cohesion-ladder.md](references/cohesion-ladder.md) - **Don't reach through strangers** - Law of Demeter as the call-site detector for content coupling, see [references/law-of-demeter.md](references/law-of-demeter.md) ## Gotchas - "Tightly coupled" is not actionable: name the connascence form and the coupling rung, then you know the fix. - Strong connascence is fine _inside_ one module; it's only a problem _across_ a boundary (rule of locality). - Law of Demeter is a heuristic, not a law: pure data pipelines are a deliberate exception; it targets reaching through a stranger to depend on or mutate its internals. - Coupling and cohesion trade off: splitting a module to "loosen