Estimate dynamic execution factor

What it's for

Gives executives one uncertainty-aware execution state without averaging incompatible metrics or hiding the loadings behind a proprietary score.

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.

{
  "directions": {
    "cycle_time": "lower_is_better",
    "reliability": "higher_is_better",
    "throughput": "higher_is_better"
  },
  "forecast_periods": 8,
  "metric_names": [
    "throughput",
    "reliability",
    "cycle_time"
  ],
  "observations": [
    {
      "id": "execution-factor-0",
      "metrics": {
        "cycle_time": 0,
        "reliability": 0,
        "throughput": 0
      },
      "period": 0
    },
    {
      "id": "execution-factor-1",
      "metrics": {
        "cycle_time": 0.013333333333333332,
        "reliability": 0.145,
        "throughput": 0.07666666666666666
      },
      "period": 1
    },
    {
      "id": "execution-factor-2",
      "metrics": {
        "cycle_time": 0.026666666666666665,
        "reliability": 0.08,
        "throughput": 0.15333333333333332
      },
      "period": 2
    },
    {
      "id": "execution-factor-3",
      "metrics": {
        "cycle_time": -0.05,

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": [
    "Metrics are complete, comparable, consecutive aggregate time series and each declared direction maps improvement onto a common execution-positive orientation.",
    "One linear Gaussian latent factor plus a local linear trend adequately represents shared movement; metric-specific shocks, multiple factors, seasonality, and structural breaks can invalidate the summary.",
    "PCA loadings are descriptive covariance weights, not causal contributions, while variance parameters are selected by a bounded likelihood grid and require outcome calibration before operational use.",
    "The latent state describes an organization, portfolio, team, project, or service cohort above the privacy threshold and must not be interpreted as an individual performance score."
  ],
  "current_state": {
    "forecast_change_interval": [
      -0.16276,
      1.751114
    ],
    "forecast_horizon_change": 0.794177,
    "level": 2.904845,
    "velocity": 0.099272
  },
  "decision": "latent_execution_state_stable_or_uncertain",
  "forecast": [
    {
      "period": 60,
      "state_interval": [
        2.607073,
        3.401162
      ],
      "state_mean": 3.004117,
      "velocity_mean": 0.099272
    },
    {
      "period": 61,
      "state_interval": [
        2.639884,
        3.566895
      ],
      "state_mean": 3.10339,
      "velocity_mean": 0.099272
    },
    {
      "period": 62,
      "state_interval": [
        2.667509,
        3.737814
      ],
      "state_mean": 3.202662,
      "velocity_mean": 0.099272

How it works

Markov & state-space control — Choose a policy over evolving states when today's action changes tomorrow's options.

1. 1 Extract a direction-aligned latent execution factor from aggregate metric vectors and forecast its level and velocity with a likelihood-tuned local-linear-trend state-space model.
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": "extract a directionaligned latent execution factor" }
  → finds "estimate_dynamic_execution_factor"

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

gitrevio_capability_run
  { "capability_id": "estimate_dynamic_execution_factor", "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 Delivery forecasting & commitments →