Order SLAs
Current API source catalogs three Order SLAs fields:
- order-deadline enforcement;
- deadline time; and
- delay-risk row highlighting.
The preserved labels and screenshot are fixture evidence. Catalog metadata does not prove configured values, seconds as a deployed unit, deadline computation, row highlighting, operational handling, or achieved service levels.
Reporting relationship
API source defines an SLA report read with aggregate classifications and filters. GET/HEAD is not safe by verb: no report, order, business, site, driver, group, type, count, or performance data was requested. The report contract does not prove a setting-to-report relationship, deployed classification, or achieved SLA.
Source-defined write boundary
The shared editor stages ordinary fields until Save and writes configs sequentially, so later failure can follow earlier persistence. No config write or report read was run.
SLA reporting can expose operational volume, performance and identifying filters. Runtime re-entry requires synthetic aggregate orders and masked dimensions, intercepted config/report requests, and immutable classification/effect receipts.
Related guides: Business reports · Delivery reports