Predictika · Everpure Evergreen//One catalog
An AI sales agent prepares an Evergreen//One quote for a customer beyond FlashArray: a file, object, block or AI tier, the reserve, performance and term, and sometimes the ransomware recovery SLA. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published tier minimums, fixed terms, protocol fit and SLA eligibility, and returns a verdict and every reason.
This validator models the Evergreen//One service catalog on the tiers below and handles any quote involving them — not just the scenarios shown on this page.
Placeholders and inferences: the discount limits (5, 15 and 25 percent) are Predictika placeholders because Everpure does not publish its discount matrix, and the AI tier serving file and object is inferred, not stated in Everpure's documents. The tier minimums and terms come from Everpure's public documents; no prices are used.
Any Evergreen//One quote on these tiers is in scope, not only the scenarios pictured here. Not covered: prices and per-TiB rates (the deal value is an input, so this validator produces no price build-up or line-item quote), the other Evergreen//One SLAs beyond the ransomware recovery add-on, and Evergreen//Forever, //Foundation and //Flex (see the FlashArray validator). Assumptions: the AI tier is assumed to serve file and object, which is inferred; the discount limits (5, 15 and 25 percent) are placeholders.
7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator caught | Typical rules-based CPQ | Predictika |
|---|---|---|
| Adaptive tier quoted with too little throughput | Only with care Capacity passes. The GB/s minimum is a second threshold that differs by tier, so each tier needs its own validation rule, and the performance reserve is easy to leave blank. | Blocks on the GB/s minimum, 5 for Adaptive file and object and 1 for Adaptive block and file. |
| Unified Data Repository quoted at a short term | Only with care The term is a free-entry field. A rule per tier can compare it with the fixed 36 months, but it must be written and kept for every fixed-term tier. | Blocks; the fixed term is stored on the tier record and compared on every call. |
| S3 object on a block and file tier | Only with care Protocol support has to be recorded per tier and checked against a customer need that is rarely a field on the quote. | Blocks on protocol fit; the need travels with the request. |
| Ransomware recovery SLA added for a customer who is not on Evergreen//One | Only with workarounds Eligibility belongs to the customer account, not the quote. A rule can check it only if the program is copied onto the quote as a field. | Blocks on eligibility. |
| Tier minimums stated in the quote that differ from the catalog | Only with workarounds A validation rule can compare a stated figure with a catalog value only if the stated figure is a field on the quote, which it rarely is. | The stated minimums travel with the quote and are compared with the catalog on every call. |
| Combination the public documents do not cover (SLA on the AI tier) | Only with workarounds A CPQ allows or rejects. It has no way to say that nothing published covers the combination and a person must decide. | Routes to a person for approval and says why. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off.
| 1 | the Adaptive (Unified Fast File and Object) tier needs a performance reserve of at least 5 GB/s; the quote has 3 GB/s. |
| 2 | the quote states a minimum performance reserve of 3 GB/s; the Adaptive (Unified Fast File and Object) tier minimum is 5 GB/s. |
| 3 | the Unified Data Repository (Block and File) tier is a 36-month term; the quote has 24 months. |
| 4 | the Premium (Unified Block and File) tier does not serve S3 object; the customer needs it. |
| 5 | the ransomware recovery SLA is an add-on for Evergreen//One customers; this customer is not on Evergreen//One. |
| 6 | availability of the ransomware recovery SLA on the AI tier is not published; product management must confirm. |
| 7 | the Performance (Unified Block and File) tier has a minimum of 50 TiB; the quote reserves 40 TiB. |
| 8 | the quote states a minimum reserve of 100 TiB; the Capacity (Unified Block and File) tier minimum is 200 TiB. |
| 9 | the AI tier needs a performance reserve of at least 30 GB/s; the quote has 20 GB/s. |
| 10 | 30 percent discount exceeds the 25 percent anyone can approve on a deal of $1,500,000. |
| 11 | 20 percent discount is above the 5 percent a rep can give; approvable up to 25 percent on this deal ($1,500,000). |
| 12 | the Performance (Unified Fast File and Object) tier does not serve block; the customer needs it. |