Add design and product documentation

This commit is contained in:
2026-07-14 13:57:08 +03:00
parent 4c315e77e9
commit 7ec528ab89
2 changed files with 35 additions and 0 deletions

22
PRODUCT.md Normal file
View File

@@ -0,0 +1,22 @@
# Product — FreightOps Control
Status: approved baseline.
## Audience and job
Dispatchers and operations leads need to detect exceptions, understand shipment state, coordinate routes and returns, and act with an auditable operational picture.
## Primary journeys
1. Scan fleet and shipment health, alerts, and service-level risk.
2. Filter and inspect shipments, routes, returns, and responsible operators.
3. Resolve or escalate an exception and verify the resulting state.
## Non-goals
- No marketing landing-page patterns inside operations screens.
- No charts or statuses without definitions, timestamps, and empty/error states.
## Success criteria
Critical exceptions are visible quickly, tables remain usable at realistic density, and every action has feedback and audit context.