Modular Library Consumers¶

Shape reusable boundaries around focused consumer dependencies and hidden volatile implementation.

Generated example

This page is generated from evaluations/scenarios/modular-library-consumers.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¶

Require every consumer to depend on unrelated capabilities.
Expose volatile implementation details for convenience.

Scenario source¶

schema_version: 0.10.0
id: modular-library-consumers
description: Shape reusable boundaries around focused consumer dependencies and hidden
  volatile implementation.
input:
  skill: modular-design
  mode: library-oriented
  task: Split a reusable package whose consumers use distinct capability subsets.
expected:
  active_principles:
  - common-reuse-principle
  - interface-segregation-principle
  - information-hiding
  constrained_principles:
  - common-closure-principle
  suppressed_principles: []
forbidden:
- Require every consumer to depend on unrelated capabilities.
- Expose volatile implementation details for convenience.
principles_under_test:
- common-reuse-principle
- interface-segregation-principle
- information-hiding
- common-closure-principle