Modular Service Splitting¶

Reject independently operated services when only naming and repository size suggest separation.

Generated example

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

Create one service per domain noun.
Infer deployment boundaries from codebase size.

Scenario source¶

schema_version: 0.10.0
id: modular-service-splitting
description: Reject independently operated services when only naming and repository
  size suggest separation.
input:
  skill: modular-design
  mode: service-oriented
  task: Split a cohesive single-lifecycle module into services without isolation or
    scaling evidence.
expected:
  active_principles:
  - high-cohesion-low-coupling
  - information-hiding
  constrained_principles:
  - separation-of-concerns
  suppressed_principles: []
forbidden:
- Create one service per domain noun.
- Infer deployment boundaries from codebase size.
principles_under_test:
- high-cohesion-low-coupling
- information-hiding
- separation-of-concerns
- avoid-accidental-complexity