---
updatedAt: 2026-07-08T22:30:58.000Z
agentTools:
  projectIndex: https://developers.foxcommand.ai/llms.txt
---

# Templates

# Templates

## Overview

Templates help turn the FoxCommand integration model into working material for your application.

Use templates after you understand the workflow and need a concrete place to organize Customer Configuration, Decision Mapping, readiness checks, or minimal integration code. Templates are preparation aids; Runtime API contracts still define exact request and response behavior.

## Available Templates

| Template                                        | Best for                                                                                                            |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| `integration/customer-integration-checklist.md` | Confirming material, credentials, mapping, and evidence retention before runtime calls.                             |
| `customer-app-skeleton/`                        | Separating configuration, mapping, runtime call construction, and evidence handling in a minimal application shape. |

## When To Start From A Template

Start from a template after you have:

* Identified Customer Configuration references, including the Customer Profile context.
* Defined Business Semantics for the decision.
* Prepared Decision Mapping for the selected Decision Surface.
* Confirmed credential handling responsibilities.
* Decided where returned runtime evidence should be retained.

If those decisions are not ready, start with [How FoxCommand Works](how-foxcommand-works.md) and the [Customer Integration Reference Architecture](customer-integration-reference-architecture.md).

## What To Customize

Customize templates with your information:

* Customer identifiers and ownership context.
* Governance Artifact references and versions.
* Policy setup and setup mapping references.
* Decision Mapping rules.
* Customer traceability metadata.
* Evidence retention locations.
* Credential handling and secret management practices.
* Customer review, release, rollback, reporting, or CI/CD workflow links.

Keep credentials out of committed files and shared logs.

## How Templates Fit Runtime Use

Use templates to organize your preparation before runtime calls.

Then use [Runtime Capabilities](runtime-capabilities.md) and the [Runtime API Reference](runtime-api-reference.md) to follow the runtime sequence:

```text
Governed Execution
    -> Replay
    -> Simulation
    -> Comparison
    -> Governance RCA
```

## Runtime Boundary

The [OpenAPI specification](https://github.com/joelliptondesign/foxcommand-adapter-kit/blob/main/customer-reference/openapi/foxcommand-runtime-api.openapi.json) defines exact request and response contracts, authentication requirements, endpoint behavior, and operational limits.

Templates do not change runtime behavior or define runtime APIs.

## First Integration Step

Complete the [Customer Integration Checklist](https://github.com/joelliptondesign/foxcommand-adapter-kit/blob/main/customer-reference/templates/integration/customer-integration-checklist.md), adapt the [Customer Application Skeleton](https://github.com/joelliptondesign/foxcommand-adapter-kit/blob/main/customer-reference/templates/customer-app-skeleton/README.md), then validate prepared material before forming runtime requests.