28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
# Internal Kitchen Workflow Contracts
|
|
|
|
## Purpose
|
|
|
|
`kitchen-service` now exposes a board-oriented internal workflow surface that the kitchen-ops BFF can consume directly.
|
|
|
|
## Endpoint Surface
|
|
|
|
- `GET /internal/kitchen/queue?queueName=<name>&limit=<n>`
|
|
- `POST /internal/kitchen/orders/transition`
|
|
- `GET /internal/kitchen/board?contextId=<id>`
|
|
- `POST /internal/kitchen/work-items/claim`
|
|
- `POST /internal/kitchen/work-items/priority`
|
|
|
|
## Contract Depth Added In Stage 41
|
|
|
|
The new kitchen workflow contracts add enough shape for downstream BFF and SPA work:
|
|
|
|
- board lanes with per-item station, claim, ETA, and priority details
|
|
- explicit claim/release-ready work-item ownership responses
|
|
- dedicated priority update responses separate from generic state transitions
|
|
- existing transition contract kept in place for order-state changes
|
|
|
|
## Current Runtime Shape
|
|
|
|
- The default implementation remains deterministic and in-memory.
|
|
- This repo still focuses on orchestration and contract shape, not kitchen persistence realism.
|