Detect operational critical slowing down
Detect early-warning patterns associated with an aggregate system losing resilience before a possible regime transition: locally detrend rolling windows, track rising lag-one autocorrelation, variance, and spectral reddening, compare endpoint shifts with a frozen reference regime, and control multiplicity under a circular moving-block bootstrap.
What it's for
Adds an unusual early-warning layer for leaders and investors: Gitrevio can look for statistically governed signs that an operating system is taking longer to recover before a visible breakdown appears.
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 |
|---|---|---|---|
| block_length | integer ≥ 2, ≤ 200 | Your calibration | Optional |
| bootstrap_draws | integer ≥ 200, ≤ 10000 | Numerical control | Optional |
| false_discovery_rate | number ≥ 0.001, ≤ 0.3 | Your calibration | Optional |
| max_detail_rows | integer ≥ 1, ≤ 500 | Numerical control | Optional |
| maximum_reference_abs_tau | number ≥ 0, ≤ 1 | Your calibration | Optional |
| minimum_confirming_indicators | integer ≥ 2, ≤ 3 | Your calibration | Optional |
| minimum_endpoint_shift_mad | number ≥ 0, ≤ 20 | Your calibration | Optional |
| minimum_kendall_tau | number ≥ 0, ≤ 1 | Your calibration | Optional |
| observations | array of objects (4 fields) ≥ 80 items | Evidence | Yes |
| seed | integer | Numerical control | Optional |
| window_periods | integer ≥ 10, ≤ 500 | Your calibration | Optional |
| window_step | integer ≥ 1, ≤ 100 | Your calibration | Optional |
Each observations
record
| Field | Type | Required |
|---|---|---|
| id | string (non-empty) | Yes |
| period | integer | Yes |
| split | one of "reference", "monitor" | Yes |
| value | number | Yes |
{
"block_length": 8,
"bootstrap_draws": 200,
"observations": [
{
"id": "batch2-critical-0",
"period": 0,
"split": "reference",
"value": 0.3
},
{
"id": "batch2-critical-1",
"period": 1,
"split": "reference",
"value": 0.8505306089080445
},
{
"id": "batch2-critical-2",
"period": 2,
"split": "reference",
"value": 0.3064026688324719
},
{
"id": "batch2-critical-3",
"period": 3,
"split": "reference",
"value": -0.2529082189332362
},
{
"id": "batch2-critical-4",
"period": 4,
"split": "reference",
"value": 0.21103110817528797
},
{
"id": "batch2-critical-5",
"period": 5,
"split": "reference",
"value": 0.3693242593082133
},
{
"id": "batch2-critical-6",
"period": 6,
"split": "reference", Truncated for display — the full payload is 585 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.
{
"decision": "aggregate_critical_transition_warning_material",
"executive_summary": {
"confirming_indicators": 3,
"minimum_confirming_indicators": 2,
"reference_regime_stable": true,
"strongest_bh_q_value": 0.0075,
"strongest_indicator": "log_variance"
},
"guardrails": [
"Critical slowing is an early-warning pattern, not a forecast that a transition will occur or proof of its cause.",
"The block-bootstrap null assumes the governed reference regime is representative and sufficiently stationary.",
"Autocorrelation, variance, and spectral reddening can rise because of measurement, seasonality, or exogenous shocks; investigate those alternatives.",
"Use aggregate system metrics only; this function does not infer individual stress, intent, performance, or employment risk."
],
"indicator_diagnostics": [
{
"bh_q_value": 0.0075,
"bootstrap_p_value": 0.005,
"confirmed": true,
"endpoint_shift_mad": 3.9903,
"indicator": "log_variance",
"monitor_kendall_tau": 0.5714,
"reference_kendall_tau": -0.0714
},
{
"bh_q_value": 0.0075,
"bootstrap_p_value": 0.005,
"confirmed": true,
"endpoint_shift_mad": 3.3235,
"indicator": "spectral_reddening",
"monitor_kendall_tau": 0.5,
"reference_kendall_tau": -0.0714
},
{
"bh_q_value": 0.01,
"bootstrap_p_value": 0.01,
"confirmed": true,
"endpoint_shift_mad": 3.8338,
"indicator": "lag_one_autocorrelation",
"monitor_kendall_tau": 0.5714,
"reference_kendall_tau": -0.1429
}
], Truncated for display — the full payload is 110 lines.
How it works
Decision analysis — Turn uncertainty, cost and risk appetite into a defensible choice, with the reasoning left inspectable.
- 1 Freeze one aggregate system metric, cadence, direction, reference regime, later monitoring interval, window/step, seasonality treatment, and transition-response protocol before inspecting warning indicators.
- 2 Locally detrend rolling reference and monitoring windows, calculate lag-one autocorrelation, log residual variance, and low/high-frequency spectral reddening, then measure monitoring Kendall trends and robust endpoint shifts from the reference median/MAD.
- 3 Resample circular blocks from the frozen reference to construct a dependence-preserving no-warning distribution for the joint trend/shift score, convert exceedances to p-values, and control false discovery across the three indicators.
- 4 Require a stable reference and multiple prespecified confirming indicators before warning; otherwise report no sampled signal or abstain, never an inevitable transition claim.
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
- Actions, outcomes, utilities, evidence boundaries, uncertainty representation, and accountable ownership match the actual decision.
- The reference interval is a sufficiently stable and representative regime after governed seasonality, instrumentation, missingness, and cadence treatment.
- The monitored aggregate has a plausible dynamical interpretation where slower recovery can raise autocorrelation, variance, or spectral reddening; structural metric revisions are absent.
- Block length preserves relevant dependence and the monitoring interval is long enough for multiple rolling windows without post-hoc boundary selection.
- The result structures a governed choice; it does not replace accountable judgment or authorize action outside the declared decision boundary.
- Critical slowing is a precursor pattern, not proof that a transition will occur, when it will occur, or what will cause it.
- Measurement changes, seasonality, common shocks, and nonlinear forcing can mimic the indicators and must be investigated before action.
- This is an aggregate system-resilience diagnostic and must never become an individual stress, intent, productivity, employment, or security score.
Minimum evidence
- observations: at least 80 rows/items
How to validate it
Validate on future periods or held-out aggregate units, compare with a simple baseline, and require stability across plausible metric definitions and decision thresholds.
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
- one directionally stable and seasonally governed scalar system series with consecutive zero-preserving periods
- rolling detrended autocorrelation, variance, and spectral-reddening indicators plus reference-block bootstrap samples
- system interpretation, metric/version/direction, cadence, missingness and seasonality, reference/monitor boundaries, window/step/block lengths, tau and MAD shifts, FDR, confirming count, reference stability, and alert response
Calibration workflow
- 1 Define the management decision, target outcome, aggregate unit, privacy boundary, cadence, and prediction/intervention horizon for this organization.
- 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 Estimate statistical parameters on training history, but obtain costs, utilities, risk tolerance, practical-effect thresholds, capacity, and policy constraints from accountable decision owners.
- 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 Deploy only if the returned decision clears evidence, overlap, calibration, robustness, and guardrail checks; warning, unsupported, schema-gap, and fallback decisions are abstentions.
- 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": "detect earlywarning patterns associated with an" }
→ finds "detect_operational_critical_slowing_down"
gitrevio_capability_describe
{ "capability_id": "detect_operational_critical_slowing_down" }
→ returns the input schema and agent guidance shown on this page
gitrevio_capability_run
{ "capability_id": "detect_operational_critical_slowing_down", "arguments": { ... } }
→ returns the result shown above Works in Claude Desktop, Claude Code, Cursor, Cline, Continue.dev, Goose and Aider. See the MCP server.