identify-scenario-drivers git:20260923.cbc38aaA

Immutable. This exact content never changes and is served at /api/v1/blob/4880dbed85fdbb6c.

---
name: identify-scenario-drivers
description: "Identify high-impact/high-uncertainty drivers and rank them for scenario construction."
---

# identify-scenario-drivers

## Purpose

Identify high-impact/high-uncertainty drivers and rank them for scenario construction.

## Input contract

```yaml
required: [candidate_drivers, impact_assessments, uncertainty_assessments]
optional: [evidence, assumptions, prior_results]
constraints: [use named scientific objects; retain provenance and missingness; $\alpha$ = 0.05 and power = 0.8 where applicable]
```

## Procedure

1. Validate the typed inputs and state the decision this operation must support.
2. Apply the declared operation to the named object; record intermediate values that affect interpretation.
3. Check boundary conditions and counterexamples, then emit the result with uncertainty and source links.

## Output contract

```yaml
produces: [identify_scenario_drivers_result, evidence_trace, uncertainties]
delta_fields: [evidence_updates, uncertainties]
```

## Quality gates

- Inputs are named scientific objects with compatible schemas.
- Every material result has a derivation or source reference.
- Fixed statistical criteria remain exact where applicable: $\alpha$ 0.05 and power 0.8.

## Failure and counterexamples

Return a failed operation with the violated precondition when inputs are incomplete, assumptions are unsupported, or a counterexample defeats the result.

## Provenance map

- intermediate: experiment-execution/scenario-driver-identification