Audit technology diligence evidence integrity

What it's for

Creates an evidence-grade technology diligence room: buyers and investors see exactly which target claims are independently supported, qualified, missing, stale or outside the frozen scope.

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": 12000,
  "diligence_cases": [
    {
      "conflict_review_complete": true,
      "cutoff_at_ms": 10000,
      "data_room_snapshot_hash": "sha256:data-room-v7",
      "evidence_verified": true,
      "id": "acquisition-alpha",
      "independent_reviewer_id": "review-firm-a",
      "management_assertion_ledger_complete": true,
      "required_domain_ids": [
        "architecture"
      ],
      "scope_system_ids": [
        "billing"
      ],
      "target_id": "target-alpha"
    }
  ],
  "diligence_claims": [
    {
      "asserted_at_ms": 8000,
      "assertion_value_hash": "sha256:inventory-v2",
      "case_id": "acquisition-alpha",
      "claim_status": "supported",
      "claim_type": "inventory",
      "domain_id": "architecture",
      "evidence_verified": true,
      "id": "claim-inventory",
      "management_asserted": true,
      "subject_system_id": "billing"
    },
    {
      "asserted_at_ms": 8000,
      "assertion_value_hash": "sha256:scalability-v2",
      "case_id": "acquisition-alpha",
      "claim_status": "supported",
      "claim_type": "scalability",
      "domain_id": "architecture",
      "evidence_verified": true,
      "id": "claim-scalability",
      "management_asserted": true,
      "subject_system_id": "billing"

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 buyer defines the complete system/domain/claim perimeter before review; the frozen data-room snapshot, management assertion ledger, reviewer conflicts and artifact provenance are immutable and tenant-scoped.",
    "Independent evidence means distinct source systems and artifact hashes, observed by the cutoff, effective and fresh at that cutoff, reviewed by the declared independent reviewer and rights-cleared where required."
  ],
  "claim_diagnostics": [
    {
      "case_id": "acquisition-alpha",
      "claim_id": "claim-inventory",
      "claim_type": "inventory",
      "domain_id": "architecture",
      "failed_gates": [],
      "qualifying_independent_evidence_count": 1,
      "subject_system_id": "billing",
      "target_id": "target-alpha"
    },
    {
      "case_id": "acquisition-alpha",
      "claim_id": "claim-scalability",
      "claim_type": "scalability",
      "domain_id": "architecture",
      "failed_gates": [],
      "qualifying_independent_evidence_count": 1,
      "subject_system_id": "billing",
      "target_id": "target-alpha"
    }
  ],
  "counts": {
    "diligence_cases": 1,
    "evidence_artifacts": 2,
    "passing_claims": 2,
    "required_claims": 2,
    "scoped_systems": 1,
    "targets": 1
  },
  "decision": "technology_diligence_evidence_ready_for_investment_committee",
  "evidence": {
    "gate_pass": true,
    "minimum_required_fraction": 0.95,
    "verified_fraction": 1
  },
  "failure_counts": {},
  "integrity_pass": true,
  "limitations": [

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 each target, data-room snapshot, cutoff, scoped systems, required domains, management-assertion ledger and independent reviewer before evaluating evidence.
2. 2 Expand domain requirements into every mandatory case- or system-level claim and reject missing, duplicate, late, qualified, unsupported, unasserted or unverified claims.
3. 3 Count only distinct source systems and artifact hashes that were known, effective, fresh, target-independent, rights-cleared where required and verified by the declared reviewer at the cutoff.

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 a frozen technology diligence case" }
  → finds "audit_technology_diligence_evidence_integrity"

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

gitrevio_capability_run
  { "capability_id": "audit_technology_diligence_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 Investment & portfolio choice →