Security & human governance
Operational authority is enforced outside model reasoning. Identity, role scope, tool permission, action policy, approval and current-state checks form a control chain that a prompt or retrieved note cannot override.
| Control | Enforcement point | Failure behavior |
|---|---|---|
| Least privilege | Service identity + tool policy | Deny tool/action outside assigned scope |
| Read/write separation | Separate retrieval and action tools | Model cannot write through read tools |
| Human approval | Approval service / role policy | Protected action remains PREPARED, not executed |
| Stale-state protection | Version/freshness check immediately before execution | Approval invalidated; investigation refreshed |
| Prompt/data boundary | System policy + tool contract | Customer/product notes treated as data, never authorization |
| Auditability | Correlation ID + immutable action event | Protected execution fails if required audit context cannot be recorded |
Maps Orders, Inventory, Warehouse, Purchase Orders, customer rules and fulfilment actions to permitted AI assistance and retained human authority.
Role + resource scopeSeparate action toolsRequired for protected actionRequired before execution150 protected-action tests cover order changes, allocation changes, shipment release and customer-rule boundaries; zero unauthorised writes execute.
150 designed cases0 authorization bypassRole · action · approval · stale state · write boundaryRequires reproducible security runCorrelation trace records user role, order, SKUs, warehouses, tools, source versions, rule results, evidence references, recommendations, approval state and action status.
SOAI-REQ-004817SO-12547ORDER_LINE_SHORTAGE4NONENOT_REQUESTEDPrimewayz AI enablement for enterprise operations