Predictika · Everpure Pure1 and Fusion agent actions

An AI operations agent's change to a storage array, checked before it runs

Everpure's Pure1 and Fusion MCP servers let AI agents see and reason about a fleet, and both are read-only by design: “No write operations are exposed.” Its June 2026 announcements put Copilot Workflow Execution and Fusion Compliance and Agentic Triage on the roadmap, which is where agents start to act. When they do, someone has to decide which actions an agent may take. Before the agent acts, it sends the action to Predictika, which checks it against the published SafeMode and Evergreen rules and returns a verdict and every reason. The validator is the governed write path.

Scope: agent actions on Everpure FlashArray and FlashBlade: SafeMode snapshot eradication and eradication window, Evergreen//One capacity and utilization, Ever Modern controller upgrades. See everything this validator covers

This validator checks actions an AI agent proposes on Everpure FlashArray (//X, //XL, //C, //E) and FlashBlade (//S, //E) arrays covered by SafeMode, Evergreen//One or Evergreen//Forever — any such action, not just the scenarios shown below.

  • SafeMode snapshots — An agent may not eradicate snapshots when SafeMode is on: that goes through Everpure Support with authorized contacts. At 80 percent full or more, the guidance is to discuss a capacity upgrade. Source: Everpure blog posts, not official documentation.
  • SafeMode eradication window — The default is 24 hours; a custom window must be longer, typically 7 days and up to 30. Changing it needs at least two authorized contacts working with Support. Source: Everpure blog posts, not official documentation.
  • Evergreen//One — Workloads balanced across the arrays in a License, each at 80 percent utilization or higher; 200 to 240 V power; infrastructure kept current under the Upgrade Policy; a buffer guarantee of 25 percent of the reserve, up to 1 PiB. Source: Evergreen//One product guide (official).
  • Ever Modern — Controller upgrades every 3 years (6 for FlashArray//E and FlashBlade//E) on Evergreen//Forever; receipt within 90 days of notice, return within 45 days. Source: Evergreen program description (official).

Supplied with the request, not Everpure facts: array fullness, utilization, voltage and reserve size (for example read from Pure1 through its read-only MCP server), and the customer's own policy, such as who signs off when SafeMode is off. Where the documents do not say what happens when a condition is missed (utilization below 80 percent, infrastructure not current, receipt or return too late), the validator sends the action to a person instead of deciding. Not covered: prices and quotes (see the quote promises validator), the minimum Evergreen//One commitments (the public documents give different figures), and actions on products outside these programs.

The AI operations agentReads the fleet through the read-only servers and proposes a change.
Predictika validatorChecks every rule at once and returns the verdict and each finding. The agent acts only on an allow, or after a person approves.

9 scenarios in 4 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI operations agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI operations agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where prompt-based guardrails get it wrong
Click to expand
    
Our assessment of what instructions in an agent's prompt, plus a read-only server, do with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtPrompt-based guardrailPredictika
An Evergreen//One capacity increase with several conditions at onceOnly with workarounds
The buffer guarantee is a computed cap (25 percent of the reserve, up to 1 PiB), site power is a range, and the infrastructure must be current. A prompt cannot compute the cap, and a read-only server checks none of it.		The cap is computed from the reserve, the power is compared with the 200 to 240 V range, and the infrastructure is checked, all in one call.
An agent that reclaims space by eradicating snapshotsOnly when someone is vigilant
A prompt can tell the agent never to eradicate snapshots, but the instruction is advice to a model that is also trying to free space. Nothing outside the model refuses the call.		The action is checked against SafeMode before it runs; with SafeMode on it is blocked every time.
A SafeMode window set below the defaultOnly when someone is vigilant
The 24 hour floor lives in documentation. A prompt or a read-only server does not enforce it, and a typo such as 12 for 72 gets through.		The proposed window is compared with the floor on every call.
A controller upgrade requested earlyOnly with workarounds
The cycle length differs by product (3 or 6 years). A generic guardrail does not know the product or where it is in the cycle.		Cycle length comes from the product, and the months into the cycle are checked.
Every problem returned in one answerOnly with workarounds
Guardrails tend to stop at the first problem, so the agent retries and meets the next.		All findings come back together, blocks first, then approvals.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the action; approval findings need a person to sign off.

    
1SafeMode is on; deleting or eradicating the 14 destroyed snapshots goes through Everpure Support with SafeMode authorized contacts, not through an agent.
2The array is 91 percent full; Everpure SafeMode guidance says to discuss a capacity upgrade when an array is 80 percent full or more.
3SafeMode is off on this array; eradicating 3 snapshots cannot be undone and needs a person to sign off under the customer policy.
4An eradication window of 12 hours is not longer than the 24 hour default; a custom window must be longer.
5Changing the SafeMode eradication window to 168 hours requires at least two authorized contacts working with Everpure Support.
6800 hours is beyond the 30 days (720 hours) that SafeMode guidance gives as the upper end of a custom window.
7After the move one array in the License would run at 76 percent utilization, below the 80 percent that Evergreen//One asks for on every array in a License.
8This array is not part of an Evergreen//One License, so Evergreen//One capacity and utilization actions do not apply.
9Site power is 120 V; Evergreen//One expects high line AC power of 200 to 240 V.
10The buffer guarantee covers 25 percent of the reserve up to 1 PiB (200 TiB here); the increase of 350 TiB needs confirmation from Everpure.
11Evergreen//One requires the infrastructure to be kept up to date under its Upgrade Policy and it is not current; confirm eligibility with Everpure.
12The upgrade is requested 20 months into a 36 month Ever Modern cycle; the next controllers are not due yet.
13Receipt of the new controllers is scheduled 120 days after Everpure notice; the program asks for receipt within 90 days.
14Ever Modern controller upgrades belong to Evergreen//Forever subscriptions, and this array is not on one.
15The old controllers would be returned 60 days after receipt; the program asks for return within 45 days.

  

  

    
Scenarios and results
Click to expand
    
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. Growing Evergreen//One capacity: Add 1,500 TiB of Evergreen//One capacity

    
The agent's request. The array is 88 percent full. Please add 1,500 TiB with an Evergreen//One capacity increase on the 8,000 TiB reserve, for the FlashArray//XL on the 415 V power feed.

    
Verdict: Blocked.

    
    
      
  • Site power outside 200 to 240 V. Site power is 415 V; Evergreen//One expects high line AC power of 200 to 240 V.
    • 
      
  • Increase above the buffer guarantee. The buffer guarantee covers 25 percent of the reserve up to 1 PiB (1,024 TiB here); the increase of 1,500 TiB needs confirmation from Everpure.
    • 
      
  • Infrastructure not current. Evergreen//One requires the infrastructure to be kept up to date under its Upgrade Policy and it is not current; confirm eligibility with Everpure.
    • 
    

    
2. Growing Evergreen//One capacity: The agent resubmits after fixing the errors

    
The agent's request. The array is 88 percent full. Please add 1,500 TiB with an Evergreen//One capacity increase on the 8,000 TiB reserve, for the FlashArray//XL on the 208 V power feed.

    
Verdict: Needs approval.

    
    
      
  • Increase above the buffer guarantee. The buffer guarantee covers 25 percent of the reserve up to 1 PiB (1,024 TiB here); the increase of 1,500 TiB needs confirmation from Everpure.
    • 
      
  • Infrastructure not current. Evergreen//One requires the infrastructure to be kept up to date under its Upgrade Policy and it is not current; confirm eligibility with Everpure.
    • 
    

    
3. Growing Evergreen//One capacity: The agent resubmits after fixing the errors

    
The agent's request. The array is 88 percent full. Please add 1,000 TiB with an Evergreen//One capacity increase on the 8,000 TiB reserve, for the FlashArray//XL on the 208 V power feed, with its infrastructure up to date.

    
Verdict: Allowed.

    
    
      
  • All rules satisfied. Every rule checked is satisfied.
    • 
    

    
4. Reclaiming space on a full array: Eradicate destroyed snapshots to free space

    
The agent's request. The array is 91 percent full. Please eradicate the 14 destroyed snapshots to free space.

    
Verdict: Blocked.

    
    
      
  • Snapshot eradication goes through Support. SafeMode is on; deleting or eradicating the 14 destroyed snapshots goes through Everpure Support with SafeMode authorized contacts, not through an agent.
    • 
      
  • Array is 80 percent full or more. The array is 91 percent full; Everpure SafeMode guidance says to discuss a capacity upgrade when an array is 80 percent full or more.
    • 
    

    
5. Reclaiming space on a full array: The agent resubmits after fixing the errors

    
The agent's request. The array is 91 percent full. Please add 300 TiB with an Evergreen//One capacity increase on the 2,000 TiB reserve.

    
Verdict: Allowed.

    
    
      
  • All rules satisfied. Every rule checked is satisfied.
    • 
    

    
6. SafeMode eradication window: Shorten the window to 12 hours

    
The agent's request. Please shorten the SafeMode eradication window to 12 hours.

    
Verdict: Blocked.

    
    
      
  • Eradication window too short. An eradication window of 12 hours is not longer than the 24 hour default; a custom window must be longer.
    • 
    

    
7. SafeMode eradication window: The agent resubmits after fixing the errors

    
The agent's request. Please set the SafeMode eradication window to 7 days (168 hours).

    
Verdict: Needs approval.

    
    
      
  • Window change needs authorized contacts. Changing the SafeMode eradication window to 168 hours requires at least two authorized contacts working with Everpure Support.
    • 
    

    
8. Ever Modern controller upgrade: Upgrade requested 20 months into a 36-month cycle

    
The agent's request. Please schedule the controller upgrade for the FlashArray//X, which is 20 months into its Evergreen//Forever cycle.

    
Verdict: Blocked.

    
    
      
  • Upgrade is not due yet. The upgrade is requested 20 months into a 36 month Ever Modern cycle; the next controllers are not due yet.
    • 
    

    
9. Ever Modern controller upgrade: The agent resubmits after fixing the errors

    
The agent's request. Please schedule the controller upgrade for the FlashArray//X, which is 36 months into its Evergreen//Forever cycle.

    
Verdict: Allowed.

    
    
      
  • All rules satisfied. Every rule checked is satisfied.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. Everpure's Pure1 and Fusion MCP servers let AI agents see and reason about a fleet, and both are read-only by design: “No write operations are exposed.” Its June 2026 announcements put Copilot Workflow Execution and Fusion Compliance and Agentic Triage on the roadmap, which is where agents start to act. When they do, someone has to decide which actions an agent may take. Before the agent acts, it sends the action to Predictika, which checks it against the published SafeMode and Evergreen rules and returns a verdict and every reason. The validator is the governed write path.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. The array is 88 percent full. Please add 1,500 TiB with an Evergreen//One capacity increase on the 8,000 TiB reserve, for the FlashArray//XL on the 415 V power feed.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with one finding and two approvals, all in one answer. Site power is 415 V; Evergreen//One expects high line AC power of 200 to 240 V.
    6. 
      
  6. The validator returned one blocking finding and two approvals 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. 
      
  7. What this shows: for an Evergreen//One capacity increase with several conditions at once, a prompt-based guardrail can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the site power to 208 V.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The one blocking finding is cleared; two approvals remain for a person: increase above the buffer guarantee and infrastructure not current.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the capacity increase to 1,000 TiB and the infrastructure status to up to date.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. Both earlier findings are cleared.
    18. 
      
  18. Three problems caught in one call, fixed in two passes, and a clean request. That is the value of Predictika's validator: catching mistakes before the action runs.
    19.