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:

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

Define durable Customer Profile references.
Confirm Business Semantics for the governed decision.
Map those semantics through the customer-owned Decision Mapping Layer.
Target the appropriate FoxCommand Decision Surface.
Submit mapped material through runtime-authoritative contracts.
Store runtime evidence identifiers in customer systems of record.
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, then define customer-owned meaning with Business Semantics.