Profile Library Dry Versus Yagni¶
Introduce a narrow public extension seam when independent consumers demonstrate one stable variation point.
Generated example
This page is generated from evaluations/scenarios/profile-library-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¶
- Expose implementation machinery as the extension contract.
- Add hooks for consumer variations that have not been demonstrated.
Scenario source¶
schema_version: 0.10.0
id: profile-library-dry-versus-yagni
description: Introduce a narrow public extension seam when independent consumers demonstrate
one stable variation point.
input:
profile: reusable-library
skill: abstraction-and-reuse
mode: extensible-public-library
conflict: dry-versus-yagni
task: Independent consumers require two documented policies at one stable decision
point.
expected:
resolution: expose-narrow-extension-seam
active_principles:
- open-closed-principle
- single-source-of-truth
constrained_principles:
- yagni
- premature-generalization
suppressed_principles: []
forbidden:
- Expose implementation machinery as the extension contract.
- Add hooks for consumer variations that have not been demonstrated.
principles_under_test:
- dry
- yagni
- open-closed-principle
- single-source-of-truth
- premature-generalization