Run inside the enterprise boundary.
Private environmentAgent Hive, the operating context and the model runtime stay in a private cloud, VPC or on-premises environment.
- Approved read-only connectors
- Enterprise SSO and roles
- Source and decision trace
The same research, applied to each domain’s evidence, rules and owners.
A worked example: an order for 100 cases was confirmed at 80 and delivered at 60. Agents follow every quantity change, show the rule behind it and draft an answer the customer team can stand behind.
The questionThe customer asked for 100 cases. Why were 80 confirmed and only 60 delivered?
Pull together the order, customer, stock and delivery records.
Show which customer, stock or priority rule cut the requested quantity.
Check batch eligibility, freshness, storage location and delivery constraints.
Write a plain explanation with each change linked to its rule and record.
An owner approves, corrects or escalates. Corrections join the test set.
20 cases were cut by the fair-share rule during a constrained allocation. 20 more failed the customer's 60% shelf-life term at picking.
The service owner approves, corrects or escalates the explanation before anything goes to the customer.
Allocation and fulfilment rules belong to supply planning. Agents can flag a rule; they never edit one.
The waterfall is the answer: requested, cut by allocation, confirmed, cut by fulfilment, delivered. Each step opens the record and the rule.
Stock for SKU 220 was short at the 03:00 run, so every tier-2 customer got 80% of the request.
Batch 7740 had 52% shelf life left. Customer B requires 60%, so FEFO picking skipped it.
Load 5520 delivered 60 cases; the proof of delivery matches the pick list.
Agent Hive gathers only the context needed for this order. The first version stays read-only: no write-back until an owner says so.
Agent Hive
Agent HiveOrder lines, confirmations and allocation runs from the ERP.
Batches, reservations, shelf life and picking records.
Terms, service levels and the original request from CRM and email.
Allocation and fulfilment are traced in parallel, then joined into one explanation that waits for the service owner.
Orders, lines, allocation runs, batches, deliveries and the rules that govern them, each linked to its source table or document.
Show which customer, stock or priority rule changed the requested quantity.
Check batch eligibility, freshness, storage location and delivery constraints.
Compare similar orders across customers, products, locations and weeks.
Representative orders and expert review check that each explanation is correct, complete, useful and supported by the right evidence.
| Question | v1 | v2 | v3 |
|---|---|---|---|
| Why was order 4471 confirmed at 80 of 100?Allocation | ✓ | ✓ | ✓ |
| Which priority rule applied to Customer B?Allocation | ✗ | ✓ | ✓ |
| Why did 20 cases fail the shelf-life check?Fulfilment | ~ | ✗ | ✓ |
| Was the short delivery a picking or a stock issue?Fulfilment | ~ | ✓ | ✓ |
| Which DC shorted the most lines last month?Pattern | ✓ | ~ | ✓ |
| Do other customers on the same SKU see the same cut?Pattern | ✗ | ✗ | ✓ |
| Draft the reply to the customer teamAnswer | ✓ | ~ | ✓ |
Service and planning review real explanations.
Corrections become repeatable test cases.
Every change reruns the whole set.
Only versions that hold the bar go live.
The first workflow can use approved read-only access. Any later action or write-back stays behind permissions, review and audit.
Agent Hive, the operating context and the model runtime stay in a private cloud, VPC or on-premises environment.
The order context stays private while selected requests pass through redaction, routing and audit controls.
| Runs in | QpiAI managed environment | A dedicated network in your cloud | Your data centre (Docker / Compose) | An isolated network |
|---|---|---|---|---|
| Operated by | QpiAI | Agreed per engagement | Your team | Your team |
| Tenancy | Multi-tenant, isolated | Single-tenant | Single-tenant | Single-tenant |
| Data at rest | Managed environment | Your cloud and region | Your network | Inside the perimeter |
| Models | Managed models | Approved endpoints | Local, or via a policy gateway | Local models only |
| Outbound | Operated by QpiAI | Private connections | One controlled egress path (hybrid) | None |
| Identity | Your identity rules | Enterprise identity | SSO and RBAC | Local SSO and RBAC |
| Updates | Rolled out by QpiAI | Agreed per engagement | New image version, pulled | Signed offline packages |
| Audit | Audit history | Audit history | Local audit history | Local audit history |
Air-gapped Graph, agents and models run inside an isolated network; updates arrive as signed offline packages.