> ## 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.

# Decision Mapping

# Decision Mapping

## Purpose

Decision Mapping is the customer-owned translation from Business Semantics into FoxCommand-compatible execution material.

The Decision Mapping Layer sits between customer business language and the FoxCommand Decision Surface. It keeps customer meaning in customer systems while giving FoxCommand normalized material for bounded runtime execution.

## Decision Architecture

Use this customer-side progression:

```text
Customer Workflow
-> Customer Business Language
-> Decision Mapping Layer
-> FoxCommand Decision Surface
-> Governed Execution
-> Replay / Simulation
-> Comparison
-> Governance RCA
```

The FoxCommand Decision Surface is the stable normalized execution surface targeted by mapped customer material. Runtime API details remain authoritative in `foxcommand-runtime`.

## Mapping Inputs

Decision Mapping starts with customer-owned inputs:

* Customer workflow context.
* Business Semantics.
* Customer Profile references.
* Governance artifact references.
* Policy setup and setup mapping references.
* Candidate policy setup references where needed.
* Evidence and lineage references.
* Customer traceability metadata such as case, corpus, experiment, release, review, or approval identifiers.
* Data handling constraints.

## Mapping Outputs

A customer-owned mapping should produce enough material for the customer integration system to select and submit runtime-compatible inputs.

Expected outputs may include:

* Selected Decision Surface.
* Governance artifact and policy setup material selected for evaluation.
* Setup mapping references or material.
* Candidate policy setup for evaluation flows.
* Replay references retained from prior execution where applicable.
* Customer correlation metadata for traceability where current runtime contracts support it.
* Evidence and lineage references retained in customer systems.

## Mapping Responsibilities

Customers own:

* Which business workflow should use FoxCommand runtime evaluation.
* How customer concepts map to governance artifacts, policy setup, setup mappings, candidate policy setup, replay references, and correlation metadata.
* Traceability from runtime evidence back to customer workflows and systems of record.
* Updates to mappings when customer language, policy, governance artifacts, or lifecycle systems change.
* How returned execution, replay, comparison, or RCA evidence affects customer lifecycle records.

FoxCommand owns deterministic runtime evidence production over submitted material. FoxCommand does not own customer mapping rules or their business meaning.

## Mapping Workflow

1. Select the customer workflow or decision to evaluate.
2. Confirm the customer-owned Business Semantics.
3. Select the Customer Profile references needed for this workflow.
4. Select governance artifact, policy setup, and setup mapping versions.
5. Choose the Decision Surface targeted by the mapped material.
6. Attach evidence, lineage, and customer traceability metadata.
7. Review ambiguous terms or values with the customer owner before runtime submission.
8. Submit only through runtime-authoritative request contracts.
9. Store returned runtime identifiers in customer systems of record.
10. Update mappings through customer-owned change controls when business language or governance material changes.

## Mapping Rules

* Preserve customer ownership of source facts and Business Semantics.
* Map customer meaning before runtime submission.
* Treat customer correlation metadata as opaque customer-owned traceability context.
* Keep runtime evidence distinct from customer governance source truth.
* Do not infer missing business meaning inside FoxCommand.
* Do not treat runtime identifiers as customer governance versions, release versions, approval records, or rollback targets.

## Terminology

Use:

* Decision Mapping Layer for the customer-owned translation layer.
* FoxCommand Decision Surface for the normalized execution surface.
* Business Semantics for customer-owned meaning.
* Runtime evidence for FoxCommand output.

Avoid terms that imply FoxCommand owns customer meaning, customer lifecycle state, or semantic normalization.

## Next Step

Review [Decision Surfaces](decision-surfaces.md), inspect [Decision Mapping examples](https://github.com/joelliptondesign/foxcommand-adapter-kit/tree/main/customer-reference/examples/decision-mapping), then use [Runtime Capabilities](runtime-capabilities.md) when mapped material is ready for runtime evaluation.