- WHY: establish Stage 3 task-001 execution baseline per repo intent - WHAT: add minimal solution/project skeleton and boundary docs - RULE: apply stage3 execution runtime and repository workflow directives
14 lines
499 B
Markdown
14 lines
499 B
Markdown
# Furniture Service Use-Case Boundaries
|
|
|
|
## Orchestration Responsibilities
|
|
|
|
- Application use cases orchestrate domain workflows.
|
|
- Use cases depend on DAL-facing ports, not persistence implementations.
|
|
- Transport handlers map to use-case contracts and do not own orchestration logic.
|
|
|
|
## Current Skeleton
|
|
|
|
- `IGetFurnitureAvailabilityUseCase`: orchestration boundary contract.
|
|
- `GetFurnitureAvailabilityUseCase`: orchestration implementation.
|
|
- `IFurnitureAvailabilityReadPort`: DAL-facing port.
|