Foresight

What this feature is for

Foresight combines blast radius and failure forecast. Blast radius connects dependencies to journeys so an operator can prioritize response by impact. Failure forecast estimates time-to-breach from observed signals such as error budget, usage, or reliability drift. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A dependency map, defined journeys, a signal with enough history, and a threshold that means something to the business.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Choose the degraded provider or the trending signal, inspect the impacted nodes or forecast inputs, and create a preventive action before the threshold becomes an incident.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The view should identify the dependency, impacted journey, severity, measured trend, threshold, forecast window, and model inputs. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

An incomplete map understates risk. A short horizon with low confidence is a prompt to investigate, not permission to panic.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use Foresight with Vendor outages, User journeys, Incidents & fixes, Health, and Automations. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.