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

# Customer Configuration

# Customer Configuration

## Purpose

Customer Configuration is the durable customer-owned context used by a customer integration system to call FoxCommand consistently over time.

It lets customers configure stable references once, submit selected material repeatedly through runtime-authoritative contracts, and retain runtime evidence in customer-controlled systems of record.

## Customer Profile

A Customer Profile is the minimum durable customer-owned configuration envelope for a FoxCommand integration.

It may contain references to:

* Customer identity and ownership context.
* Customer-owned governance source records.
* Customer-owned execution input records.
* Customer-owned mapping records.
* Customer-owned traceability identifiers.
* Customer credential relationship context.
* Customer retention and lifecycle references for submitted material and returned evidence.

A Customer Profile is not a FoxCommand governance repository, lifecycle engine, deployment target, storage schema, or administration surface.

## Durable Configuration Areas

| Area                          | Customer-owned content                                                                                                 | FoxCommand treatment                                                                                    |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Customer identity context     | Customer identifier, organization context, system-of-record reference.                                                 | Accepted as customer context through authorized integration boundaries.                                 |
| Governance references         | Governance artifact identifiers, versions, repository references, approval records, owner references.                  | Accepted as submitted material or opaque references where current runtime contracts support them.       |
| Execution references          | Policy setup references, setup mapping references, selected input references, execution intent metadata.               | Used as request material for bounded deterministic execution.                                           |
| Mapping references            | Links between governance artifacts, policy setup, releases, cases, corpora, experiments, reviews, or runtime evidence. | Preserved as opaque customer traceability where current runtime evidence supports correlation metadata. |
| Credential relationship       | Relationship between customer-owned integration systems and authorized runtime credentials.                            | Enforced through Runtime Gateway and Customer Authority behavior.                                       |
| Evidence retention references | Records for returned execution, replay, comparison, and RCA identifiers.                                               | Runtime identifiers remain evidence references, not customer governance versions or approvals.          |

## Customer-Owned Semantics

Customers own the meaning of Customer Configuration.

That includes:

* Governance artifact identity and version meaning.
* Policy setup identity and version meaning.
* Setup mapping identity and meaning.
* Case, corpus, experiment, release, review, approval, and rollback identifiers.
* Operational ownership, retention, privacy, and audit context.
* Interpretation of returned runtime evidence.

FoxCommand may receive selected customer material and return supported correlation metadata unchanged. FoxCommand does not interpret customer configuration as lifecycle state, approval status, release status, experiment assignment, corpus authority, or customer system-of-record truth.

## Configuration Lifecycle

Use this lifecycle:

1. Define or update customer-owned governance, policy, execution, and mapping references in customer-controlled systems.
2. Authorize the integration path through Customer Authority credential lifecycle controls.
3. Select stable Customer Profile references for a runtime request.
4. Submit bounded material through the authenticated Runtime Gateway using runtime-authoritative contracts.
5. Store returned runtime evidence and identifiers in customer-controlled systems of record.
6. Decide in customer systems whether configuration, governance, policy, release, experiment, approval, rollback, reporting, or CI/CD records should change.

FoxCommand consumes submitted material and returns bounded runtime evidence. It does not manage the customer configuration lifecycle.

## Relationship To Business Semantics

Customer Configuration holds durable references.

Business Semantics explain what the referenced customer material means.

For example:

* A governance artifact reference identifies customer-owned material.
* Business Semantics explain the customer meaning of the governed decision.
* Decision Mapping translates that meaning into material for the FoxCommand Decision Surface.

## Relationship To Decision Mapping

Decision Mapping uses Customer Profile references, governance references, execution references, mapping references, and traceability identifiers to select FoxCommand-compatible execution material.

The mapping remains customer-owned. FoxCommand receives submitted material through current runtime contracts and returns bounded evidence.

## Credential Boundary

Credentials are access control material. They are not governance semantics, policy semantics, approval records, release records, lifecycle state, or customer configuration source truth.

Customer systems decide which internal services or operators may use authorized credentials. Credential secrets must stay out of committed files and shared logs.

## Implementation Checklist

Before repeated runtime use, confirm the customer system can identify:

* Customer Profile owner.
* Governance artifact source record.
* Governance artifact version.
* Policy setup or setup mapping version.
* Decision Mapping reference.
* Credential relationship owner.
* Evidence retention location.
* Customer traceability metadata.
* Change-control owner for configuration updates.

## Boundary

Customer Configuration supports runtime interaction only through existing authenticated runtime contracts and supported evidence fields. It does not add runtime endpoints, modify request bodies, create FoxCommand persistence requirements, or prescribe customer repository layout.

## Next Step

Define the meaning of the configured material in [Business Semantics](business-semantics.md), then translate it through [Decision Mapping](decision-mapping.md).