Skip to content
WorkspaceLet's simulate→
CortexSim/Use cases/Risk & stress scenario analysis
Risk & governance / Risk & stress scenario analysis

Pressure the assumptions.
Clarify the decision.

Explore authored adverse scenarios and sensitivity ranges in a transparent model with independently reviewed business rules.

Design your evaluation
01Assumption versions are retained02Adverse cases are explicit03Domain review remains independent
The authored stress envelope
The authored stress envelope — AssumptionsAgree the scenario dimensions and their bounds with the domain owner. The shape is qualitative, not a risk estimate.DemandFailureDelayPolicyRecoveryDeclare the assumption setQualitative illustration, not a risk estimate
Interactive concept illustration · authored examples, not measured results
01/ 03
Assumptions

Agree the scenario dimensions and their bounds with the domain owner. The shape is qualitative, not a risk estimate.

THE BUSINESS DECISION

Which assumptions change the decision?

Explore the supporting capability

Stress analysis is useful when it reveals which assumptions change a decision. It becomes misleading when an adverse scenario is presented as a forecast, or when independent domain judgments are hidden inside an unexplained output.

WHEN THIS MATTERS

A planned change depends on uncertain demand, dependency availability or authored business-policy assumptions.

A DECISION NEEDS EVIDENCE
BRING THESE PERSPECTIVESRisk ownerDomain specialistScenario analystIndependent reviewer

Agree the scenario assumptions with the domain owner.

THE CHECK

Assumption versions are retained

THE ARTIFACT TO RETAIN

Versioned scenario assumptions

INSIDE THE DECISION

A service plan depends on a stable level of incoming demand.

Authored scenario · not a customer case study
01

The hidden risk

A combined demand burst and dependency delay changes the apparent viability of the candidate.

02

The experiment

Compare the declared adverse case with the baseline while retaining the policy and workload assumptions.

03

The review conversation

A sensitivity finding and a set of independent review questions, rather than a probability claim or automatic approval.

FROM QUESTION TO EVIDENCE

A method your reviewers can follow.

Explore authored adverse scenarios and sensitivity ranges in a transparent model with independently reviewed business rules.

01

Agree the scenario assumptions with the domain owner.

QUESTION TO RESOLVE

Assumption versions are retained

ARTIFACT TO RETAIN

Versioned scenario assumptions

02

Vary demand, failure and policy inputs within declared bounds.

QUESTION TO RESOLVE

Adverse cases are explicit

ARTIFACT TO RETAIN

Sensitivity and failure thresholds

03

Inspect sensitivity and identify the evidence needed for acceptance.

QUESTION TO RESOLVE

Domain review remains independent

ARTIFACT TO RETAIN

Independent domain-review requirements

WORK WITH YOUR EXISTING SYSTEMS

Keep the source. Make the boundary explicit.

Scenario illustrations are not forecasts, actuarial valuations or regulatory acceptance. Qualified domain review remains necessary.

Explore MCP connectivity
YOUR ENVIRONMENTDeclared assumptionsReviewed source and access scope
SIMULATION BOUNDARYSensitivity comparisonDomain review remains independent

MCP can expose permitted simulation tools and evidence to an approved client. Source adapters, grants and deployment compatibility must be reviewed separately.

BUILD YOUR EVALUATION BRIEF

Decide what the evidence must answer.

A baseline, an agreed adverse scenario family and explicit boundaries for interpreting the comparison.

Select the checks to include in your downloadable planning brief. This prepares a scope; it does not run a simulation.

3 checks selected
Checks for your evaluation
BEFORE YOU BEGIN

Set expectations with the whole team.

What should our first evaluation include?

A baseline, an agreed adverse scenario family and explicit boundaries for interpreting the comparison.

What does this evidence not establish?

Scenario illustrations are not forecasts, actuarial valuations or regulatory acceptance. Qualified domain review remains necessary.

What should an independent reviewer inspect?

A reviewer should be able to reconstruct the exact assumptions behind a conclusion.

LEARN BEFORE THE DECISION BECOMES EXPENSIVE

Bring a real question. Leave with an evaluation plan.

A baseline, an agreed adverse scenario family and explicit boundaries for interpreting the comparison.

Frame your evaluation