Why: baseline pending customer order edge handlers and runtime assets before security wave. What: add submit order contracts/handlers, service adapter updates, and docs/docker assets. Rule: keep technical intent and align repository workflow.
675 B
675 B
Feature Epics
Repository
customer-orders-bff
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
- Order lifecycle consistency and state transitions.
- Kitchen queue and dispatch optimization hooks.
- Operations control-plane policies (flags, service windows, overrides).
- POS closeout and settlement summary alignment.
Documentation Contract
Any code change in this repository must include docs updates in the same branch.