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

# Customer Decision Architecture

## Purpose

This overview connects Customer Configuration, Business Semantics, Decision Mapping, and the FoxCommand Decision Surface.

It is a customer-facing orientation guide for engineers deciding how customer-owned configuration and meaning become runtime-compatible execution material.

## Concept Chain

Use this chain:

```text
Customer Configuration
-> Business Semantics
-> Decision Mapping Layer
-> FoxCommand Decision Surface
-> Runtime evidence
-> Customer lifecycle decision
```

Each step has a different owner and purpose.

## Ownership Summary

| Concept                     | Customer-owned responsibility                                                                                              | FoxCommand responsibility                                             |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Customer Configuration      | Maintain durable references, Customer Profile context, credential relationship context, and evidence retention references. | Accept submitted material through current runtime contracts.          |
| Business Semantics          | Define customer meaning, source facts, vocabulary, lifecycle context, and systems of record.                               | Do not infer, normalize, or adjudicate customer meaning.              |
| Decision Mapping Layer      | Translate customer meaning into FoxCommand-compatible execution material.                                                  | Preserve a stable normalized execution surface.                       |
| FoxCommand Decision Surface | Submit mapped material to runtime-authoritative contracts.                                                                 | Execute deterministic runtime primitives and return bounded evidence. |
| Customer lifecycle decision | Decide approval, promotion, rollback, release, experiment, reporting, or CI/CD impact.                                     | Provide evidence only; do not become the lifecycle authority.         |

## Working Sequence

1. Define durable Customer Profile references.
2. Confirm Business Semantics for the governed decision.
3. Map those semantics through the customer-owned Decision Mapping Layer.
4. Target the appropriate FoxCommand Decision Surface.
5. Submit mapped material through runtime-authoritative contracts.
6. Store runtime evidence identifiers in customer systems of record.
7. Apply evidence to customer lifecycle decisions outside FoxCommand.

## Boundary

This overview does not define runtime API details, runtime capability behavior, customer lifecycle automation, or publication behavior. Runtime engineering documentation in `foxcommand-runtime` remains authoritative.

## Next Step

Prepare durable references with [Customer Configuration](customer-configuration.md), then define customer-owned meaning with [Business Semantics](business-semantics.md).