Profile Browser Dry Versus Yagni¶

Keep superficially similar interaction behavior local when no stable shared knowledge has been demonstrated.

Generated example

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

Extract a shared component based only on visual or structural similarity.
Move feature behavior away from its owner without shared knowledge evidence.

Scenario source¶

schema_version: 0.10.0
id: profile-browser-dry-versus-yagni
description: Keep superficially similar interaction behavior local when no stable
  shared knowledge has been demonstrated.
input:
  profile: browser-web-application
  skill: abstraction-and-reuse
  mode: conservative
  conflict: dry-versus-yagni
  task: Two interface features contain similar interaction code but have different
    behavior and owners.
expected:
  resolution: preserve-locality
  active_principles:
  - yagni
  - locality-of-behaviour
  constrained_principles:
  - dry
  suppressed_principles: []
forbidden:
- Extract a shared component based only on visual or structural similarity.
- Move feature behavior away from its owner without shared knowledge evidence.
principles_under_test:
- dry
- yagni
- locality-of-behaviour