Audit data sovereignty residency evidence integrity

What it's for

Turns Gitrevio's EU residency, BYOK and in-region backup promise into a customer-verifiable evidence control spanning every storage and processing surface.

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": 2000,
  "data_assets": [
    {
      "created_at_ms": 0,
      "data_class_id": "customer-code",
      "deleted_at_ms": null,
      "evidence_verified": true,
      "id": "asset-1",
      "required_location_type_ids": [
        "storage",
        "processing",
        "backup",
        "key"
      ]
    }
  ],
  "data_locations": [
    {
      "artifact_hash": "hash-storage",
      "asset_id": "asset-1",
      "evidence_verified": true,
      "id": "location-storage",
      "independently_verified": true,
      "location_type": "storage",
      "observed_at_ms": 1000,
      "provider_id": "provider-a",
      "region_id": "eu-west",
      "retention_until_ms": 31536000000,
      "satisfied_control_ids": [
        "tenant-kms"
      ],
      "source_system_id": "source-storage",
      "valid_from_ms": 0,
      "valid_until_ms": null
    },
    {
      "artifact_hash": "hash-processing",
      "asset_id": "asset-1",
      "evidence_verified": true,
      "id": "location-processing",
      "independently_verified": true,
      "location_type": "processing",
      "observed_at_ms": 1000,

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": "asset-1",
      "data_class_id": "customer-code",
      "disallowed_location_ids": [],
      "failed_gates": [],
      "missing_location_type_ids": [],
      "passed": true,
      "policy_id": "eu-v1",
      "retention_failure_location_ids": [],
      "stale_location_ids": [],
      "transfer_failure_ids": []
    }
  ],
  "configuration": {
    "as_of_ms": 2000,
    "maximum_observation_age_days": 2,
    "minimum_independent_location_observations": 1,
    "minimum_verified_asset_fraction": 0.95
  },
  "decision": "pass",
  "failed_gates": {
    "asset_failure_counts": {},
    "orphan_location_ids": [],
    "orphan_transfer_ids": [],
    "overlapping_active_policy_class_ids": []
  },
  "guardrails": [
    "Policy allowlists, transfer mechanisms and retention limits are governed inputs; this function does not infer law or provide legal advice.",
    "Passing means the submitted point-in-time evidence is internally consistent, not that every undiscovered copy or future transfer is compliant.",
    "The function never moves, deletes, re-encrypts, reroutes or exposes customer data."
  ],
  "method": "point_in_time_data_sovereignty_evidence_audit_v1",
  "summary": {
    "active_policy_class_count": 1,
    "asset_count": 1,
    "location_observation_count": 4,
    "policy_class_count": 1,
    "transfer_observation_count": 1,
    "verified_asset_count": 1,
    "verified_asset_fraction": 1
  }
}

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 one effective residency policy per governed data class at the as-of time; policies—not the algorithm—supply permissible storage, processing, backup and key regions, required controls, transfer-mechanism and retention rules.
2. 2 Reconcile the complete asset perimeter to active infrastructure, database, object-store, backup, logging, cache, processing and KMS observations using distinct source/artifact evidence and explicit validity intervals.
3. 3 Test required location-type completeness, allowed regions, encryption controls, retention, current independent evidence and evidenced cross-region mechanisms; surface orphans and policy overlap as repair gates.

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 every governed data assets pointintime" }
  → finds "audit_data_sovereignty_residency_evidence_integrity"

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

gitrevio_capability_run
  { "capability_id": "audit_data_sovereignty_residency_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 Security, access & compliance →