Dependencies Infrastructure Provider¶

Keep operational policy independent from a volatile provider integration.

Generated example

This page is generated from evaluations/scenarios/dependencies-infrastructure-provider.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¶

Leak provider request types into planning policy.
Add a generic repository unrelated to consumer needs.

Scenario source¶

schema_version: 0.10.0
id: dependencies-infrastructure-provider
description: Keep operational policy independent from a volatile provider integration.
input:
  skill: dependencies-and-boundaries
  mode: domain-centric
  profile: infrastructure-tool
  modifier: security-sensitive
  task: Separate a least-authority deployment plan from provider calls.
expected:
  active_principles:
  - clean-architecture-dependency-rule
  - dependency-inversion-principle
  - ports-and-adapters
  constrained_principles:
  - inversion-of-control
  suppressed_principles: []
forbidden:
- Leak provider request types into planning policy.
- Add a generic repository unrelated to consumer needs.
principles_under_test:
- clean-architecture-dependency-rule
- dependency-inversion-principle
- ports-and-adapters