Design balanced stepped wedge rollout

What it's for

Turns a phased deployment into a practical, balanced experiment plan instead of letting operational convenience silently determine the causal comparison.

What you give it

Inputs split into evidence read from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.

{
  "clusters": [
    {
      "baseline_metrics": {
        "cycle_time": 0,
        "failure_rate": 0,
        "throughput": 0
      },
      "cluster_size": 8,
      "id": "rollout-design-0",
      "rollout_risk": 0
    },
    {
      "baseline_metrics": {
        "cycle_time": 1.85,
        "failure_rate": 0.17525773195876287,
        "throughput": 2.9
      },
      "cluster_size": 9,
      "id": "rollout-design-1",
      "rollout_risk": 0.13
    },
    {
      "baseline_metrics": {
        "cycle_time": 3.7,
        "failure_rate": 0.35051546391752575,
        "throughput": 5.8
      },
      "cluster_size": 10,
      "id": "rollout-design-2",
      "rollout_risk": 0.26
    },
    {
      "baseline_metrics": {
        "cycle_time": 0.5,
        "failure_rate": 0.5257731958762887,
        "throughput": 8.7
      },
      "cluster_size": 11,
      "id": "rollout-design-3",
      "rollout_risk": 0.39
    },
    {
      "baseline_metrics": {

What you get back

This is the actual output of running the example above — computed by the same function the platform calls, not an illustration.

{
  "assumptions": [
    "Every cluster is eligible for every declared wave, adoption is irreversible after its assigned wave, and capacities are fixed before optimization.",
    "Baseline metrics, cluster sizes, and rollout-risk scores are frozen before assignment; the design balances declared features but cannot balance omitted causes.",
    "The pair-exchange heuristic preserves exact wave counts and reports its remaining imbalance; it does not claim a global optimum.",
    "Production inference still needs randomized execution, assignment logging, no anticipatory treatment, stable outcomes, interference policy, and cohort-aware analysis."
  ],
  "balance": {
    "initial_objective": 0.0788,
    "maximum_allowed": 0.25,
    "maximum_cumulative_standardized_imbalance": 0.0855,
    "optimized_objective": 0.0041,
    "relative_improvement": 0.9478,
    "represented_population_cv_across_waves": 0.0308,
    "risk_weighted_population_cv_across_waves": 0.0623
  },
  "computation": {
    "accepted_improving_swaps": 15,
    "optimization_iterations": 500,
    "seed": 26
  },
  "decision": "balanced_stepped_wedge_design_ready",
  "detail": {
    "returned_rows": 40,
    "total_rows": 40,
    "truncated": false
  },
  "method": "capacity_constrained_stepped_wedge_pair_exchange_v1",
  "sample": {
    "clusters": 40,
    "metrics": 3,
    "represented_population": 400,
    "waves": 4
  },
  "schedule": [
    {
      "cluster_id": "rollout-design-12",
      "cluster_size": 10,
      "rollout_risk": 0.73,
      "rollout_wave": 1
    },
    {
      "cluster_id": "rollout-design-19",
      "cluster_size": 12,

How it works

Causal inference & experiment design — Separate what a change caused from what merely moved alongside it.

1. 1 Assign teams or other aggregate clusters to capacity-constrained rollout waves with pair-exchange optimization of cumulative causal balance, represented population, and rollout risk.
2. 2 Evaluate the method-specific diagnostics and gates returned by the function, then abstain unless the declared decision clears them under locally governed thresholds.

Before you trust it

Every tool in the catalog ships with the conditions under which its answer is meaningful — and the conditions under which it should abstain instead of guessing.

Calibrating it to your org

Calibration workflow

1. 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
2. 2 Build a tenant-scoped historical cohort using only information available before each prediction or decision; preserve zero periods, censoring, assignment probabilities, and unresolved outcomes when the method requires them.
3. 3 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
4. 4 Validate on later time windows or held-out aggregate units at the deployment grain, against a simple baseline and the function-specific validation strategy.
5. 5 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
6. 6 Monitor realized outcomes, data drift, coverage, and decision regret; recalibrate at a governed cadence or after a detected regime/definition change, never merely because a stakeholder dislikes the result.

Call it from your AI

You don't wire up 388 tools in your MCP client. The GitRevio MCP server exposes 18 tools, three of which let an agent search the catalog, read a tool's schema, and run it — so the assistant finds this one on its own.

gitrevio_capabilities_search
  { "q": "assign teams or other aggregate clusters" }
  → finds "design_balanced_stepped_wedge_rollout"

gitrevio_capability_describe
  { "capability_id": "design_balanced_stepped_wedge_rollout" }
  → returns the input schema and agent guidance shown on this page

gitrevio_capability_run
  { "capability_id": "design_balanced_stepped_wedge_rollout", "arguments": { ... } }
  → returns the result shown above

Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.

Related tools

See every tool in Causal evidence & experiments →