Concepts & principles / principle

Single Responsibility Principle

A module should have one coherent reason to change, understood in relation to the actors or policies it serves.

Canonical graph nodesingle-responsibility-principle

More precise than “do one thing”

SRP is not a command to put every line in a separate function. It asks whether unrelated change pressures have been coupled. A graph index and a visual card layout evolve for different reasons; separating them makes those changes easier to reason about.

In AI-generated code

Ask which requirement or actor would cause each module to change. Keep graph validation separate from rendering and deployment policy separate from content. Then verify that the separation removes coupling rather than merely multiplying files.

Source

Robert C. Martin on SRP

Part of a connected world

Follow the meaning.

View the graph →

Outgoing connections

applies-toCode Generation Contract

Connected from

explainsOld principles. New leverage.
depends-onSOLID

Node data identity, meaning & relationships

The complete semantic record, rendered from root node: front matter.

semantic_node:
  description: A module should have one coherent reason to change, understood in relation to the actors or policies it serves.
  id: single-responsibility-principle
  kind: principle
  name: Single Responsibility Principle
  relationships:
  - predicate: applies-to
    target: code-generation-contract
  type: concept

Publishing metadata

description: A module should have one coherent reason to change, understood in relation to the actors or policies it serves.
draft: false
title: Single Responsibility Principle
url: /graph/concepts/single-responsibility-principle/