Validation Guide

Overview

Validation catches preparation issues before and after runtime calls.

Validation helps you confirm that configuration, mappings, request data, and returned evidence are ready for the next workflow step. It does not replace runtime execution, approval, or the runtime API.

Before Runtime

Validate the material your integration will submit:

1. Confirm Customer Configuration has the required customer, credential, source record, mapping, and evidence retention references.
2. Confirm Business Semantics are resolved for the decision being evaluated.
3. Confirm Decision Mapping selects the intended Governance Artifact, policy setup, setup mapping, Decision Surface, and traceability metadata.
4. Validate request data against the applicable schema, example, or Runtime API contract.
5. Confirm credentials are handled outside committed files and shared logs.

Fix source material before making runtime calls.

After Runtime

Validate the returned evidence before continuing the workflow:

1. Confirm expected identifiers are present where returned, such as execution_id, contract_reference, replay_reference, or comparison_id.
2. Store returned identifiers in your systems.
3. Preserve the relationship between runtime evidence and your Governance Artifacts, policy setup, mapping material, cases, releases, reviews, or approvals.
4. Run Replay, Simulation, Comparison, or Governance RCA only when the previous step returned the evidence required for that capability.
5. Record lifecycle decisions outside FoxCommand.

Validation Inputs

Use these inputs when they match your workflow:

• Schemas: Governance Artifact, Readiness Assessment, and Validation Report.
• Validators: Artifact Validation Tools.
• Examples: customer-reference/examples/

Use the OpenAPI specification for runtime request and response shapes used by customer integrations.

What Validation Does Not Do

Validation does not:

• Execute runtime behavior.
• Define runtime API responses.
• Modify customer source facts.
• Approve lifecycle decisions.
• Replace review, release, rollback, reporting, or CI/CD workflows.

First Integration Step

After validation, make the next runtime call only when the required source material, credentials, and prior runtime evidence are available.