Governance RCA

Overview

Need to understand why an outcome changed? Use Governance RCA.

Governance RCA produces bounded attribution evidence for material governance outcome differences. It helps customer systems understand whether a candidate policy change is responsible for a changed runtime outcome where current runtime behavior can provide that attribution.

When To Use It

Use Governance RCA when:

A valid replay_reference is available.
Candidate policy setup is available.
Simulation or Comparison output indicates a difference that needs bounded attribution.
Runtime evidence is needed to support review, remediation, approval, rollback, or release decisions.

Governance RCA is for bounded governance attribution. It is not an enterprise-wide explanation engine.

What You Provide

Provide:

replay_reference
candidate_policy_setup

Governance RCA composes Replay, Simulation, Comparison, and bounded attribution. It does not bypass those runtime paths.

What FoxCommand Returns

A successful Governance RCA response may include:

Status
replay_reference
Baseline outcome
Simulated outcome
Comparison summary
root_cause
Bounded errors

The root_cause object may indicate:

status: "attributed" when Comparison reports a material governance outcome difference.
status: "no_material_difference" when Comparison reports no material governance outcome difference.
Responsible governance change identity where attribution is available.
Attribution type.

What To Do Next

Store RCA evidence with related Replay, Simulation, Comparison, governance, policy, review, and approval records.

Use customer-owned systems to decide remediation, approval, promotion, rollback, release, or governance update outcomes. Treat Governance RCA as bounded runtime evidence, not as an automatic decision.

Runtime Source of Truth

Use FoxCommand runtime documentation and the OpenAPI specification for exact request bodies, response bodies, authentication requirements, errors, and operational limits.

Governance RCA is limited to bounded governance attribution. It is not organizational RCA, clinical RCA, financial RCA, infrastructure diagnosis, or customer lifecycle automation.

Next Steps

Use Runtime API Reference for authentication, endpoints, request sequence, and where to find the complete API specification.