Audit org health score integrity

Reconstruct the organization-health composite from frozen component evidence and block publication when source completeness, consent, versioning, construct balance, cross-group measurement invariance, redundancy, privacy or leave-one-component stability fails.

What it's for

Makes Gitrevio's flagship Org Health Score defensible: leaders can see whether its 20-signal story is complete, comparable and robust before trusting the number.

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.

Field Type Role Required
as_of_ms number ≥ 0 Your calibration Yes
component_definitions array of objects (9 fields) Evidence Yes
component_observations array of objects (11 fields) Evidence Yes
detail_limit integer ≥ 1, ≤ 1000 Your calibration Optional
evidence_cutoff_ms number ≥ 0 Your calibration Yes
invariance_certificates array of objects (9 fields) ≥ 0 items Evidence Yes
maximum_absolute_cross_construct_correlation number ≥ 0, ≤ 1 Your calibration Optional
maximum_component_weight number ≥ 0, ≤ 1 Your calibration Optional
maximum_construct_weight number ≥ 0, ≤ 1 Your calibration Optional
maximum_leave_one_out_score_change number ≥ 0, ≤ 100 Your calibration Optional
minimum_group_size integer ≥ 2, ≤ 100000 Your calibration Optional
minimum_healthy_score number ≥ 0, ≤ 100 Your calibration Optional
minimum_invariance_sample_size integer ≥ 2 Your calibration Optional
minimum_scope_coverage number ≥ 0, ≤ 1 Your calibration Optional
source_snapshots array of objects (6 fields) Evidence Yes
target_period integer ≥ 0 Your calibration Yes

Each component_observations record

Field Type Required
component_id string (non-empty) Yes
consent_verified boolean Yes
definition_version string (non-empty) Yes
evidence_verified boolean Yes
group_id string (non-empty) Yes
id string (non-empty) Yes
observed_at_ms number (≥ 0) Yes
period integer (≥ 0) Yes
scope_id string (non-empty) Yes
source_id string (non-empty) Yes
value number Yes
Example input
{
  "as_of_ms": 1000,
  "component_definitions": [
    {
      "construct_id": "construct-0",
      "definition_version": "org-health-v1",
      "direction": "higher_better",
      "evidence_verified": true,
      "id": "component-0",
      "reference_center": 5,
      "reference_scale": 2,
      "source_id": "git",
      "weight": 0.25
    },
    {
      "construct_id": "construct-0",
      "definition_version": "org-health-v1",
      "direction": "higher_better",
      "evidence_verified": true,
      "id": "component-1",
      "reference_center": 5,
      "reference_scale": 2,
      "source_id": "git",
      "weight": 0.25
    },
    {
      "construct_id": "construct-1",
      "definition_version": "org-health-v1",
      "direction": "higher_better",
      "evidence_verified": true,
      "id": "component-2",
      "reference_center": 5,
      "reference_scale": 2,
      "source_id": "delivery",
      "weight": 0.25
    },
    {
      "construct_id": "construct-1",
      "definition_version": "org-health-v1",
      "direction": "lower_better",
      "evidence_verified": true,
      "id": "component-3",
      "reference_center": 5,
      "reference_scale": 2,

Truncated for display — the full payload is 674 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.

Example output
{
  "decision": "publish_aggregate_org_health_score",
  "finding": "aggregate_org_health_pressure",
  "group_summaries": [
    {
      "group_id": "platform",
      "mean_score": 41.25,
      "p10_score": 35.75,
      "p90_score": 47.25,
      "scope_count": 5
    },
    {
      "group_id": "product",
      "mean_score": 42.5,
      "p10_score": 37.75,
      "p90_score": 49.75,
      "scope_count": 5
    }
  ],
  "integrity_diagnostics": {
    "missing_or_failed_invariance_certificate": 0,
    "missing_scope_component": 0,
    "suppressed_small_group": 0
  },
  "limitations": [
    "The composite is descriptive and is not a causal estimand or management target.",
    "Aggregate scores cannot rank people or authorize employment, compensation, or surveillance actions.",
    "A passed audit does not prove that the score predicts future business outcomes; validate that separately."
  ],
  "method": "point_in_time_composite_reconstruction_invariance_redundancy_and_leave_one_out_audit",
  "redundancy_pairs": [],
  "summary": {
    "aggregate_mean_score": 41.88,
    "complete_scope_count": 10,
    "component_count": 4,
    "construct_count": 2,
    "effective_component_count": 4,
    "expected_scope_count": 10,
    "maximum_leave_one_out_score_change": 10,
    "publishable_group_count": 2,
    "scope_coverage": 1,
    "suppressed_small_group_count": 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 the score version, target period, evidence cutoff, component direction/weight/reference distribution, source snapshots, expected aggregate scopes and lawful consent before reconstructing any score.
  2. 2 Require one complete version-consistent component vector per expected scope, reconcile every source snapshot, suppress small groups, and require current measurement-invariance certificates before comparisons across publishable groups.
  3. 3 Calculate construct concentration, effective component count, cross-construct correlation and leave-one-component-out score sensitivity; publish only aggregate distributions when the complete measurement system passes.

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

  • Metric definitions, weights, aggregate grain, sampling, missingness, dependence, and comparison windows correspond to the management claim being audited.
  • The composite is a defensible descriptive construct; components are directionally aligned, normalization references are frozen before observation, expected scopes include measured zeroes, and invariance certificates apply to the same definition and period.
  • Association, instability, or measurement quality is not a causal effect and must not be converted directly into an individual employment decision.
  • A passed composite is descriptive, not causal and not a management target. Never expose scope rankings or use it for employment, compensation, outsourcing, surveillance or security decisions.

Minimum evidence

  • component_definitions: required and organization-defined
  • component_observations: required and organization-defined
  • source_snapshots: required and organization-defined
  • invariance_certificates: at least 0 rows/items
  • target_period: required and organization-defined
  • as_of_ms: required and organization-defined
  • evidence_cutoff_ms: required and organization-defined

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 null-preserving point-in-time component row per expected aggregate scope and score period, normalized with a frozen definition/reference version and reconciled to immutable expected-source snapshots
  • construct map, direction, component and construct weights, reference distributions, score/version effective dates, consent/lawful purpose, expected scopes, group privacy threshold, measurement-invariance certificates, redundancy and leave-one-out limits

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": "reconstruct the organizationhealth composite from frozen" }
  → finds "audit_org_health_score_integrity"

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

gitrevio_capability_run
  { "capability_id": "audit_org_health_score_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

Forecast org health operating loss

Prove whether the company-local organization-health score leads later delivery, reliability and capacity losses, then simulate their correlated economic tail only after a latest-whole-period baseline challenge passes.

Forecasting & survival

Optimize org health intervention portfolio

Select an anti-Goodhart intervention portfolio using conservative causal lower bounds on real operating loss, never score movement, with design/transport/fidelity shrinkage, negative controls, interference, shared-loss, equity, resource and CVaR constraints.

Causal inference & experiment design

Analyze info gap robust satisficing

Select a robust-satisficing action under severe uncertainty with Info-Gap Decision Theory: evaluate worst and best payoff across a governed nested uncertainty envelope, maximize the radius before a critical requirement fails, report windfall opportuneness, and use no scenario probabilities.

Decision analysis

Audit attention fragmentation evidence integrity

Audit consented point-in-time contributor identity, availability, privacy-safe calendar metadata and work-session lineage before reporting aggregate meeting load, protected focus blocks or cross-project switching.

Statistical audit & measurement

Audit attrition risk prediction integrity

Audit an attrition model's complete eligible cohort, point-in-time features, supportive-use governance, intervention-contaminated labels, competing outcomes, calibration, false positives and authorized subgroup error before any person-level use.

Forecasting & survival

Audit code knowledge concentration integrity

Audit file, module, service, or repository knowledge concentration from point-in-time substantive changes, reviews, incident response and documentation using identity-confidence filtering, recency decay, Bayesian ownership uncertainty, entropy-effective owners, HHI and leave-top-owner-out resilience—without turning contribution evidence into a person-performance score.

Sequential Bayesian & bandits

See every tool in People, retention & knowledge →

Ready to See Your Engineering work clearly?

Request a free demo