Profile Backend Dry Versus Yagni¶

Centralize a verified transaction rule inside its cohesive service owner without creating a new deployment boundary.

Generated example

This page is generated from evaluations/scenarios/profile-backend-dry-versus-yagni.yaml. The scenario YAML remains the executable source of truth.

Request¶

Repository evidence¶

No repository signals.

Expected resolution¶

Resolution layer	Expected
Profile	—
Modifiers	—
Language adapters	—
Framework adapters	—

Normalized context¶

{}

Skill modes¶

None.

Conflict decisions¶

None.

Significant decisions¶

None.

Principles under test¶

Forbidden outcomes¶

Create a separately operated service only to remove source duplication.
Generalize unrelated transaction behavior behind the same abstraction.

Scenario source¶

schema_version: 0.10.0
id: profile-backend-dry-versus-yagni
description: Centralize a verified transaction rule inside its cohesive service owner
  without creating a new deployment boundary.
input:
  profile: backend-service
  skill: abstraction-and-reuse
  mode: balanced
  conflict: dry-versus-yagni
  task: Two service operations repeat the same transaction policy and change for the
    same business reason.
expected:
  resolution: centralize-within-owner
  active_principles:
  - single-source-of-truth
  - high-cohesion-low-coupling
  constrained_principles:
  - dry
  - yagni
  suppressed_principles: []
forbidden:
- Create a separately operated service only to remove source duplication.
- Generalize unrelated transaction behavior behind the same abstraction.
principles_under_test:
- dry
- yagni
- single-source-of-truth
- high-cohesion-low-coupling