Skip to main content
Some actions don’t just change one thing — they trigger waves. A button click recalculates prices, updates inventory, fires webhooks, and invalidates caches. A schema migration cascades through indexes, views, and downstream services. An agent that acts without predicting these chains makes costly mistakes. Stratus was benchmarked on exactly this problem. In the Cascade Reactor level — where every click triggers three waves of ripple effects at 700ms intervals — the Stratus agent solved the board in ≤10 moves. The baseline didn’t finish.

Predict Before Acting

The world model simulates cascade outcomes in embedding space before your LLM executes a single action.

Chain Reasoning

Stratus tracks multi-step consequence chains — not just “what does this action do” but “what does that effect cause next.”

Interference Avoidance

Identifies when two planned actions would collide in a downstream state — and reorders before execution.

The Pattern

Cascade-aware agents follow a loop: predict → verify → execute. Only commit to an action after the world model confirms the predicted outcome moves toward the goal.

Example: E-Commerce Checkout with Side Effects

A checkout flow that cascades: applying a coupon triggers price recalculation, eligibility checks, and a cart lock that expires in 30 seconds. An agent that doesn’t predict this chain will race against state it created.

Encoding Known Side Effects

The key to reliable cascade handling is forward-feeding observed effects into the next state description. Stratus uses this to build an accurate embedding of “where we are now, including what just changed.”

Using the Rollout API for Deep Chains

For cascades with many steps, use /v1/rollout to simulate the full chain before executing anything.
/v1/rollout doesn’t require an LLM provider key — it runs entirely on the Stratus world model. Use it for planning validation before committing to execution.

When to Use Cascade Prediction

Use It

  • Multi-step checkout flows
  • Form submissions with validation cascades
  • Database operations with constraint propagation
  • Workflow automation with dependent steps
  • UI interactions that trigger loading states

Skip It

  • Single-step actions with no side effects
  • Read-only operations (search, display)
  • Simple classification or extraction tasks
  • Stateless API calls

Next Steps

Temporal Sequencing

When action order matters — avoiding interference between concurrent operations.

Rollout API

Simulate full action chains before committing to execution.

Web Navigation

Full step-by-step navigation tutorial with state quality guidance.