Governed Execution

Overview

Need to evaluate customer-owned decision material and create the first runtime evidence record? Use Governed Execution.

Governed Execution is the first runtime capability in the FoxCommand workflow. A customer system submits selected governance material, setup mapping, and policy setup through authenticated runtime access. FoxCommand returns bounded runtime evidence where current runtime behavior supports it.

When To Use It

Use Governed Execution when:

• You have selected the Governance Artifact or governance material to evaluate.
• You have selected setup mapping and customer policy setup.
• Decision Mapping has produced FoxCommand-compatible inputs.
• The material targets the intended Decision Surface.
• The integration actor has authorized runtime credentials.

A Governance Artifact is customer-owned source material for a governed decision or policy context. Decision Mapping is the customer-owned translation from business meaning into FoxCommand-compatible inputs.

What You Provide

Submit material through the governed execution endpoint using the exact request shape defined by the runtime source of truth.

The submitted material should identify the customer-owned context needed for evaluation, such as:

• Governance Artifact or review material.
• Source operational input or source record.
• Source facts to evaluate.
• Evidence references.
• Lineage.
• Data classification.
• Setup mapping.
• Customer policy setup.

Customer systems own the meaning, versioning, and approval state of this material.

What FoxCommand Returns

A successful response may include:

• execution_id
• status
• Governed outcome
• Surface reference
• Policy identifier and version
• Source artifact reference
• contract_reference
• replay_reference
• Bounded metadata and errors

An Execution Contract is runtime contract material returned where current runtime behavior supports it. Treat execution_id, contract_reference, and replay_reference as runtime evidence references.

These identifiers are not customer governance versions, approval records, release records, branch names, or rollback targets.

What To Do Next

Store returned runtime identifiers in customer-controlled systems. Preserve traceability to the submitted Governance Artifact, setup mapping, policy setup versions, and customer correlation metadata where supported.

Use the returned replay_reference for Replay, Simulation, Comparison, or Governance RCA when your workflow needs later verification, candidate evaluation, structured comparison, or bounded attribution.

Runtime Source of Truth

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

Governed Execution does not make FoxCommand the customer's governance repository, approval workflow, lifecycle engine, or system of record.

Next Steps

Use Replay when a returned replay_reference should be verified or reused.