Start Here

Purpose

FoxCommand gives customer-owned systems a bounded runtime surface for producing deterministic governance evidence.

This is an onboarding entry point for an experienced software engineer preparing a customer integration. Runtime API details, runtime behavior, authentication behavior, and runtime operations remain authoritative in foxcommand-runtime.

What You Are Integrating

FoxCommand does not become the customer's governance system of record.

Customer systems bring:

• Governance artifact versions.
• Policy setup and setup mapping versions.
• Customer-owned traceability context.
• Credential handling controls.
• Approval, promotion, rollback, release, experiment, reporting, and CI/CD decisions.

FoxCommand provides bounded runtime evidence through the authenticated runtime surface:

• Governed Execution.
• Replay.
• Simulation.
• Comparison.
• Governance RCA.

First Decisions

Before making runtime calls, identify:

1. The customer-owned system of record for governance artifacts, policy setup, mapping material, corpus references, release records, and approvals.
2. The engineering owner for the integration and the operational owner for credential handling.
3. The customer-controlled location where runtime identifiers will be stored.
4. The initial governance artifact, setup mapping, and policy setup versions to evaluate.
5. The customer traceability metadata that should travel with evaluation evidence where supported.

These are customer decisions. FoxCommand evidence may support them, but FoxCommand does not own them.

Onboarding Path

Use the onboarding documents in this order:

1. Quick Start for the shortest practical integration path.
2. Integration Overview for the responsibility model and runtime boundary.
3. Integration Journey for the full lifecycle from onboarding through governance evolution.
4. Runtime Authority for the runtime source-of-truth rule.

Then continue into preparation and runtime usage:

• Customer Decision Architecture
• Customer Configuration
• Business Semantics
• Decision Mapping
• Decision Surfaces
• Runtime Capabilities
• Validation
• Customer Ownership Boundaries

Runtime Authority

Use the runtime repository for:

• Runtime API request and response details.
• Authentication requirements.
• Runtime endpoint behavior.
• Replay, Simulation, Comparison, and Governance RCA behavior.
• Runtime operations.

This repository provides customer-facing onboarding guidance derived from runtime authority. It does not independently define runtime architecture or runtime behavior.

Next Step

Continue to Quick Start.