> ## Documentation Index
> Fetch the complete documentation index at: https://developers.foxcommand.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Governed Execution

# Governed Execution

## Purpose

Governed Execution is the first runtime step. A customer system submits selected governance material, setup mapping, and customer policy setup to FoxCommand and receives bounded runtime evidence.

Use the runtime API authority for exact request and response shapes.

## When To Use It

Use Governed Execution when the customer has:

* Selected a governance artifact or governance artifact reference.
* Selected a setup mapping.
* Selected customer policy setup.
* Confirmed the material targets the intended Decision Surface.
* Confirmed the integration actor has authorized runtime credentials.

## Request Boundary

Submit to the governed execution endpoint through the authenticated runtime boundary.

The submitted material should identify:

* Governed 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.

## Response Evidence

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.

Treat `execution_id`, `contract_reference`, and `replay_reference` as runtime evidence references. They are not customer governance versions, approval records, release records, branch names, or rollback targets.

## Customer Responsibilities

Customers should:

* Store returned runtime identifiers in customer-controlled systems of record.
* Preserve traceability to the submitted governance artifact, setup mapping, and policy setup versions.
* Keep bearer credentials out of committed files and shared logs.
* Use returned `replay_reference` for later Replay, Simulation, Comparison, or Governance RCA when needed.

## Boundary

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

## Next Step

Use [Replay](replay.md) when a returned `replay_reference` should be verified or reused.