Profile Legacy Dry Versus Yagni¶

Preserve apparently duplicated legacy flows until characterization proves their behavior can safely converge.

Generated example

This page is generated from evaluations/scenarios/profile-legacy-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¶

Merge the flows before characterizing their observable behavior.
Treat unexplained divergence as accidental duplication.

Scenario source¶

schema_version: 0.10.0
id: profile-legacy-dry-versus-yagni
description: Preserve apparently duplicated legacy flows until characterization proves
  their behavior can safely converge.
input:
  profile: legacy-modernization
  skill: abstraction-and-reuse
  mode: legacy-preservation
  conflict: dry-versus-yagni
  task: Two legacy flows look duplicated but produce subtly different observed results.
expected:
  resolution: preserve-observed-divergence
  active_principles:
  - chestertons-fence
  - backward-compatibility
  constrained_principles:
  - dry
  suppressed_principles: []
forbidden:
- Merge the flows before characterizing their observable behavior.
- Treat unexplained divergence as accidental duplication.
principles_under_test:
- dry
- yagni
- chestertons-fence
- backward-compatibility