Audit service continuity recovery evidence integrity

What it's for

Shows executives whether a recovery plan was actually exercised across the full critical path and achieved its RTO/RPO, instead of treating a runbook or backup checkbox as resilience.

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.

{
  "as_of_ms": 10000,
  "continuity_plans": [
    {
      "critical_capability_ids": [
        "charge",
        "refund"
      ],
      "effective_from_ms": 1000,
      "effective_until_ms": null,
      "evidence_verified": true,
      "id": "plan-payments",
      "independently_reviewed": true,
      "owner_present": true,
      "plan_version": "v3",
      "recovery_point_objective_minutes": 5,
      "recovery_time_objective_minutes": 60,
      "required_dependency_ids": [
        "primary-db"
      ],
      "service_id": "payments"
    }
  ],
  "recovery_evidence": [
    {
      "achieved_recovery_point_minutes": 3,
      "achieved_recovery_time_minutes": 45,
      "artifact_hash": "sha256:backup",
      "dependency_id": null,
      "evidence_type_id": "backup",
      "evidence_verified": true,
      "exercise_id": "exercise-1",
      "id": "evidence-backup",
      "independently_observed": true,
      "observed_at_ms": 9000,
      "plan_id": "plan-payments",
      "source_system_id": "source-backup",
      "successful": true,
      "valid_until_ms": null
    },
    {
      "achieved_recovery_point_minutes": 3,
      "achieved_recovery_time_minutes": 45,
      "artifact_hash": "sha256:restore",

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": [
    "The service/capability/dependency perimeter was frozen before review; plans, exercises and artifacts are immutable, tenant-scoped and point-in-time, and production-representative means the declared failure and recovery path was actually exercised.",
    "RTO and RPO are owner-governed objectives; independent source/artifact pairs establish distinct evidence, while required dependencies and customer communications remain inside the exercise perimeter."
  ],
  "decision": "service_continuity_evidence_ready_for_governed_reliance",
  "exercise_diagnostics": [
    {
      "exercise_id": "exercise-1",
      "failed_gates": [],
      "integrity_pass": true,
      "plan_id": "plan-payments"
    }
  ],
  "failed_gates": [],
  "limitations": [
    "Passing establishes submitted recovery-evidence integrity, not guaranteed availability, future recovery, contractual compliance, regulatory assurance, vendor solvency or customer retention.",
    "The function does not trigger failover, alter production, notify customers, waive contractual duties or authorize procurement; accountable continuity owners must rehearse and approve execution."
  ],
  "method": "point_in_time_service_continuity_recovery_evidence_audit_v1",
  "plan_diagnostics": [
    {
      "active_at_as_of": true,
      "failed_gates": [],
      "integrity_pass": true,
      "plan_id": "plan-payments",
      "service_id": "payments"
    }
  ],
  "service_continuity_integrity_ready": true,
  "summary": {
    "dependencies": 1,
    "evidence_rows": 5,
    "exercises": 1,
    "minimum_verified_evidence_fraction": 0.95,
    "plans": 1,
    "plans_passing": 1,
    "services": 1,
    "verified_evidence_fraction": 1
  },
  "truncated_detail_rows": 0
}

How it works

Statistical audit & measurement — Check whether a number is fit to decide on: coverage, timing, reconciliation, and the gaps a dashboard hides.

1. 1 Freeze effective plan versions, critical capabilities, required dependencies, owners, RTO/RPO and complete exercise/evidence scope at the as-of cutoff.
2. 2 Select the latest qualifying exercise per active plan, require production-representative capability/dependency coverage plus backup, restore, failover, dependency and customer-communication evidence from distinct verified source/artifact pairs.
3. 3 Reconcile achieved recovery time and recovery point against governed objectives, dependency failover paths and verified-evidence coverage; return repair gates rather than an uptime 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.

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": "audit whether each critical service has" }
  → finds "audit_service_continuity_recovery_evidence_integrity"

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

gitrevio_capability_run
  { "capability_id": "audit_service_continuity_recovery_evidence_integrity", "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 Risk, tails & resilience →