20 lines
811 B
Markdown
20 lines
811 B
Markdown
# Feature Epics
|
|
|
|
## Repository
|
|
kitchen-service
|
|
|
|
## Core Epics
|
|
- Epic 1: Expand domain-aligned capabilities for restaurant operations.
|
|
- Epic 2: Stabilize service contracts for containerized runtime integration.
|
|
- Epic 3: Improve observability and operational readiness for demo compose environments.
|
|
|
|
## Domain-Specific Candidate Features
|
|
- Kitchen ticket orchestration over persisted linked tickets.
|
|
- Board and queue projections backed by shared restaurant identities.
|
|
- Claim ownership, priority updates, and kitchen transition history.
|
|
- Kitchen-to-restaurant lifecycle handoff for ready and served states.
|
|
- Kitchen board lanes, claim ownership, and priority updates aligned to operator workflows.
|
|
|
|
## Documentation Contract
|
|
Any code change in this repository must include docs updates in the same branch.
|