Optimize AI capability resilience portfolio

Choose unaided drills, work rotations, cross-training, dual running, fallback redesign or monitoring per aggregate capability class using exact binomial shortfall, common-provider unique loss, hard readiness/control/capacity gates and a CVaR Pareto frontier.

What it's for

Turns AI deskilling anxiety into an investable resilience frontier: exactly which drills, rotations, dual-running or redesign actions preserve the most operating value under scarce time and money.

What you give it

Every tool is a pure function: it computes from what you pass it and reads nothing on its own. Inputs split into evidence you supply from your connected systems, calibration your team owns, and numerical controls that affect precision but never the result's meaning.

Field Type Role Required
beam_width integer ≥ 1, ≤ 100000 Numerical control Optional
capability_classes array of objects (9 fields) Evidence Yes
exact_state_limit integer ≥ 1, ≤ 10000000 Your calibration Optional
implementation_budget number ≥ 0 Your calibration Yes
max_detail_rows integer ≥ 1, ≤ 500 Numerical control Optional
provider_groups array of objects (2 fields) Evidence Yes
resilience_options array of objects (14 fields) Evidence Yes
resource_capacities array of objects (2 fields) Evidence Yes
risk_aversion number ≥ 0 Your calibration Optional
scenarios array of objects (4 fields) Evidence Yes
tail_probability number > 0, < 1 Your calibration Optional

Each resilience_options record

Field Type Required
activation_time_hours_scenarios array of number Yes
capability_class_id string (non-empty) Yes
dependency_option_ids array of string Yes
evidence_verified boolean Yes
exclusion_option_ids array of string Yes
id string (non-empty) Yes
implementation_cost number (≥ 0) Yes
is_current_state boolean Yes
operating_cost_scenarios array of number Yes
policy_type one of "unaided_drill", "work_rotation", "cross_train", "dual_run", "fallback_redesign", "monitor" Yes
resource_demands object Yes
satisfied_control_ids array of string Yes
unit_readiness_probability_scenarios array of number Yes
value_retention_fraction number (≥ 0, ≤ 1) Yes
Example input
{
  "capability_classes": [
    {
      "ai_provider_group_id": "agent-provider",
      "business_value_scenarios": [
        20000,
        20000
      ],
      "fallback_unit_count": 10,
      "id": "deployment",
      "loss_per_shortfall_unit_scenarios": [
        5000,
        20000
      ],
      "maximum_activation_time_hours": 4,
      "maximum_shortfall_probability": 0.9,
      "required_control_ids": [
        "observed-unaided-drill"
      ],
      "required_fallback_units": 6
    }
  ],
  "implementation_budget": 100,
  "provider_groups": [
    {
      "id": "agent-provider",
      "unique_value_at_risk_scenarios": [
        20000,
        100000
      ]
    }
  ],
  "resilience_options": [
    {
      "activation_time_hours_scenarios": [
        3,
        4
      ],
      "capability_class_id": "deployment",
      "dependency_option_ids": [],
      "evidence_verified": true,
      "exclusion_option_ids": [],
      "id": "monitor",
      "implementation_cost": 0,

Truncated for display — the full payload is 113 lines.

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.

Example output
{
  "assumptions": [
    "Each option's scenario readiness probability is prospectively validated for a fungible aggregate capability unit under a real AI-unavailable exercise.",
    "Conditional unit readiness is binomial within a capability class; common provider outage states and unique provider value are priced once across dependent classes.",
    "Drills, rotations, cross-training, dual running and fallback redesign include complete value retention, operating cost, implementation, control, dependency and capacity effects."
  ],
  "decision": "execute_ai_capability_resilience_portfolio",
  "economics": {
    "expected_loss": 21.8331,
    "expected_net_value": 19178.1669,
    "expected_net_value_gain_vs_current": 8654.5791,
    "implementation_cost": 100,
    "loss_conditional_value_at_risk": 108.8443,
    "loss_value_at_risk": 108.8443,
    "risk_adjusted_score": 19150.9558
  },
  "fallback_readiness": {
    "deployment": {
      "expected_unit_shortfall_by_scenario": [
        0.0001,
        0.0018
      ],
      "shortfall_probability_by_scenario": [
        0.0001,
        0.0016
      ]
    }
  },
  "limitations": [
    "Correlated capability-unit failures beyond the represented provider state can understate shortfall; exact optimization proves only the supplied finite model and beam mode does not prove global optimality.",
    "Selection governs aggregate capability classes and does not authorize named-person monitoring, performance scoring, discipline, security accusations or employment decisions."
  ],
  "method": "multiple_choice_ai_capability_binomial_readiness_cvar_v1",
  "pareto_frontier": [
    {
      "expected_net_value": 19178.1669,
      "implementation_cost": 100,
      "loss_cvar": 108.8443,
      "option_ids": [
        "quarterly-drill"
      ]
    },
    {
      "expected_net_value": 10523.5877,

Truncated for display — the full payload is 85 lines.

How it works

Constrained optimization — Pick the best feasible option under real limits — budget, headcount, dependencies, capacity — rather than ranking a list and hoping it fits.

  1. 1 Convert each prospectively validated option's conditional unit-readiness probability into exact binomial shortfall probability and expected missing units for every scenario.
  2. 2 Reject options that breach shortfall, activation, control, dependency, exclusion, budget, evidence or resource constraints before economic ranking.
  3. 3 Price direct shortfall and common-provider unique value once through joint survival, then maximize expected net value minus loss CVaR with exact enumeration or a disclosed deterministic beam.

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.

Assumptions & guardrails

  • Objectives use commensurable locally governed value units, constraints reflect real feasibility, and uncertainty covers plausible adverse inputs.
  • Unit readiness is exchangeable within class conditional on represented provider states, option effects come from real AI-unavailable exercises and value/loss sources are unique.
  • The recommendation is optimal only for its stated objective, feasible set, evidence, and solver guarantee; it is not a universal management optimum.
  • The selected portfolio governs aggregate resilience investments; it does not rank people or authorize surveillance, discipline, security allegations or employment decisions.

Minimum evidence

  • capability_classes: required and organization-defined
  • provider_groups: required and organization-defined
  • resilience_options: required and organization-defined
  • scenarios: required and organization-defined
  • resource_capacities: required and organization-defined
  • implementation_budget: required and organization-defined

How to validate it

Backtest the chosen action against simple feasible baselines on held-out scenarios, sweep costs/constraints/risk tolerance, and require constraint feasibility under adverse inputs.

Calibrating it to your org

Same for everyone

The mathematical kernel, validation rules, method version, and JSON output semantics are organization-independent; no tenant-trained coefficients or company benchmark is embedded in the function.

Specific to you

  • versioned capability-resilience planning case joining atrophy forecasts and real AI-unavailable option trials to unique value/loss, complete costs and executable operational capacity
  • class/option completeness, lawful aggregate scope, conditional exchangeability, prospective effect transport, unique provider value, shortfall/activation/control limits, dependencies/exclusions, costs, budget/resources, tail appetite, solver boundary and implementation authority

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 20 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": "choose unaided drills work rotations crosstraining" }
  → finds "optimize_ai_capability_resilience_portfolio"

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

gitrevio_capability_run
  { "capability_id": "optimize_ai_capability_resilience_portfolio", "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 AI cost, routing & return →

Ready to See Your Engineering work clearly?