Before an AI agent sends a storage array quote, the quote is checked against the vendor’s configuration and pricing rules

Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the request; approval findings need a person to sign off first.

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. Platform fit: File archive on a block-only array

The agent's request. I'm sending Larkfield Imaging a quote with two HA pairs of 55 drives each, file protocols and a write-once vault for their imaging archive, and a 5 percent discount. The capacity is well above the 1200 TiB they need.

Verdict: Blocked.

• File protocols on a block-only array. Corvane B700 is a block-only system; file and object protocols are not available on it.
• Write-once vault on a block-only array. Block-only systems do not support write-once vaults; Corvane B700 cannot be quoted with one.

2. Platform fit: The same archive on the F700

The agent's request. I'm sending the same quote on the flash array: two HA pairs of 55 drives each, file protocols and a write-once vault, and a 5 percent discount.

Verdict: Allowed.

3. Stretched clusters: A stretched cluster, two switches

The agent's request. I'm sending Tidewater Logistics a stretched cluster quote with 3 HA pairs of 47 drives each and 2 inter-site switches, on standard support. It covers the 500 TiB they need.

Verdict: Blocked.

• Stretched cluster of the wrong size. A stretched cluster is four or six controllers in total; 3 HA pairs per site is not supported.
• Inter-site switches missing. A stretched cluster needs four inter-site switches; 2 are quoted.
• Stretched cluster without top-level support. A stretched-cluster deal needs Assure Critical (4 hour) support, the standard for disaster recovery; the quote has a lower level, so it needs approval.

4. Stretched clusters: Two pairs, four switches

The agent's request. I'm sending the same sites as a stretched cluster of 2 HA pairs with 4 inter-site switches on critical support.

Verdict: Allowed.

5. Guarantees and quoted figures: A guarantee promise and the wrong capacity

The agent's request. I'm sending Northgate Media a quote that states 3000 TiB of effective capacity with the strongest data reduction guarantee, even though 60 percent of their data is already compressed or encrypted.

Verdict: Blocked.

• Stated capacity does not match. The quote states 3000.0 TiB effective capacity; the configuration gives 1548.51 TiB.
• Reduction ratio above the guarantee. The data reduction guarantee for this workload is 35 (ratio times 10); the quote promises 50.
• Reduction guarantee on a lot of ineligible data. 60 percent of the data is encrypted, already compressed or otherwise ineligible for the data reduction guarantee; sales management must approve the guarantee.

6. Guarantees and quoted figures: A guarantee at the standard ratio

The agent's request. I'm sending the quote again with the standard guaranteed ratio and the correct capacity. 45 percent of their data is ineligible.

Verdict: Needs approval.

• Reduction guarantee on a lot of ineligible data. 45 percent of the data is encrypted, already compressed or otherwise ineligible for the data reduction guarantee; sales management must approve the guarantee.

7. Subscriptions: A subscription for the wrong array

The agent's request. I'm sending Brightwater Utilities a subscription quote for 50 TiB on the Perf level with a 30 percent burst limit and 72 drives. A subscription includes support, so I left it off.

Verdict: Blocked.

• Subscription level for the wrong array. The subscription level does not match Corvane C600; Perf and Balanced are for flash and block-only systems, Capacity is for capacity flash, Archive is for disk.
• Subscription capacity not in the required steps. Subscription Perf capacity must be in 20 TiB increments; 50 TiB is not.
• Burst limit not allowed. The subscription burst limit must be 10, 25 or 50 percent of committed capacity; 30 percent was requested.

The text of the narrated walkthrough, step by step.

1. Welcome to a demo of Predictika's Validator. Corvane Storage, a fictional enterprise storage vendor, lets an AI sales agent put together quotes for its flash, capacity flash, block-only and disk arrays. Before the agent sends one, the call goes to Predictika’s Storage Array Quote Check. It checks that the platform carries the protocols and features the customer needs, that drives, RAID layout, spares and cluster size are within limits, that capacity and the data reduction guarantee hold, that stretched-cluster and subscription rules are met, that licensing and discounts are allowed, and that the capacity and price the agent stated match the computed ones. Then it returns one verdict: allow, needs approval, or block.
2. I will start with the first request by the agent.
3. The agent says. I'm sending Larkfield Imaging a quote with two HA pairs of 55 drives each, file protocols and a write-once vault for their imaging archive, and a 5 percent discount. The capacity is well above the 1200 TiB they need.
4. Before it goes out, the agent calls the validator.
5. Blocked, with two findings, all in one answer. Corvane B700 is a block-only system; file and object protocols are not available on it. Block-only systems do not support write-once vaults; Corvane B700 cannot be quoted with one.
6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the request are checked against each other.
7. What this shows: for file protocols on a block-only array, a tool can do this only with workarounds.
8. Now the agent resubmits.
9. The corrected request. It changes the array to Corvane F700 (flash).
10. It calls the validator again.
11. This time the validator clears it.
12. Both earlier findings are cleared.
13. Two problems caught in one call, fixed in one pass, and a clean request. That is the value of Predictika's validator: catching mistakes before the action runs.