# Internal Workflow Contracts

## Purpose

`operations-service` now exposes workflow-shaped internal endpoints that the restaurant BFFs can consume without inventing their own orchestration payloads.

## Endpoint Surface

- `GET /internal/operations/config?locationId=<id>`
- `POST /internal/operations/decision`
- `GET /internal/operations/waiter/assignments?contextId=<id>`
- `POST /internal/operations/orders`
- `GET /internal/operations/customer/status?contextId=<id>`
- `GET /internal/operations/pos/summary?contextId=<id>`
- `POST /internal/operations/pos/payments`
- `GET /internal/operations/admin/config?contextId=<id>`
- `POST /internal/operations/admin/service-window`

## Contract Depth Added In Stage 41

The new workflow contracts add enough shape for the next BFF layer tasks to expose richer responses:

- waiter assignments plus recent activity
- customer order status plus recent status events
- POS summary plus recent payment activity
- restaurant admin snapshot plus service windows and recent config changes
- workflow write responses that include status/message detail instead of only a boolean summary

## Current Runtime Shape

- The default implementation is still in-memory and deterministic.
- This repo remains orchestration-only; no DAL redesign is introduced by this task.
- Demo realism can deepen later without forcing BFF or SPA contract churn.