Optimize technical asset lifecycle portfolio

What it's for

Turns aging technical assets into a board-ready retain/modernize/migrate/retire portfolio while protecting the unique product value streams those assets jointly support.

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.

{
  "budget": 25,
  "capacity_units": 2,
  "lifecycle_options": [
    {
      "asset_id": "api-asset",
      "available_scenario_ids": [
        "base"
      ],
      "capability_ids": [
        "public-api"
      ],
      "capacity_units": 0,
      "decision": "retain",
      "dependency_option_ids": [],
      "evidence_verified": true,
      "exclusion_option_ids": [],
      "id": "api-retain",
      "is_current_state": true,
      "operating_cost_scenarios": [
        5,
        5
      ],
      "residual_obsolescence_loss_scenarios": [
        0,
        20
      ],
      "stranded_carrying_value_scenarios": [
        0,
        0
      ],
      "transition_cost_scenarios": [
        0,
        0
      ],
      "upfront_cost": 0
    },
    {
      "asset_id": "api-asset",
      "available_scenario_ids": [
        "base",
        "stress"
      ],
      "capability_ids": [

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.

{
  "asset_diagnostics": [
    {
      "asset_id": "api-asset",
      "current_option_id": "api-retain",
      "option_count": 2,
      "selected_decision": "modernize",
      "selected_option_id": "api-modernize"
    },
    {
      "asset_id": "data-asset",
      "current_option_id": "data-retain",
      "option_count": 1,
      "selected_decision": "retain",
      "selected_option_id": "data-retain"
    }
  ],
  "assumptions": [
    "Each asset receives exactly one executable retain, modernize, migrate or retire option; capability availability, costs, residual obsolescence and stranded carrying value share one coherent scenario, currency and horizon.",
    "A value stream is retained only when every required capability is supplied by an available selected option; if several capabilities are missing, that unique stream is still lost once. Upfront spend, transition, operating, obsolescence and stranded-value effects are complete and non-overlapping.",
    "Exact mode certifies only the supplied finite model. Beam search uses a deterministic optimistic capability/cost bound but is not globally certified; neither mode establishes accounting impairment, causal action effectiveness, legal availability or permission to retire or migrate an asset.",
    "Assets and value streams are aggregate technical/economic units, never proxies for employee, customer or vendor quality. Architecture, product, security, finance/controller and operating owners approve execution."
  ],
  "constraints": {
    "budget": 25,
    "capacity_units": 2,
    "maximum_cvar_total_loss": null,
    "maximum_expected_value_stream_loss": null,
    "risk_aversion": 0,
    "tail_probability": 0.1
  },
  "decision": "technical_asset_lifecycle_portfolio_supported",
  "lifecycle_pareto_frontier": [
    {
      "cvar_total_lifecycle_loss": 130,
      "expected_net_value": 54,
      "expected_unique_value_stream_loss": 30,
      "risk_feasible": true,
      "selected_option_ids": [
        "api-retain",
        "data-retain"
      ],
      "upfront_cost": 0
    },

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 Freeze assets, current states, executable lifecycle options, capability supply, unique value-stream requirements and common scenario economics on one decision horizon.
2. 2 For each complete portfolio, enforce one option per asset plus dependencies/exclusions, form scenario-available capability coverage, and lose each uncovered unique value stream once even when several capabilities are missing.
3. 3 Combine upfront, operating, transition, residual-obsolescence and stranded-value costs; enforce budget, capacity, expected stream-loss and CVaR gates; maximize risk-adjusted net value and disclose exact or deterministic optimistic-bound beam search.

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": "choose exactly one retain modernize migrate" }
  → finds "optimize_technical_asset_lifecycle_portfolio"

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

gitrevio_capability_run
  { "capability_id": "optimize_technical_asset_lifecycle_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 Finance & unit economics →