For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
An AI factory is a production system, not a collection of accelerators. Its software design must align workload demand, data movement, platform services, security, operations, and the capabilities supplied by the selected Enterprise Hardware Reference Architecture.
Principles
Workload First
Begin with model, data, traffic, quality, latency, throughput, concurrency, availability, recovery, and growth requirements.
Stable Interfaces
Define contracts between layers before choosing products, platforms, or partner implementations.
Balanced System
Treat compute, network, storage, host resources, software, and facilities as one demand path.
Policy Outside the Model
Enforce identity, credentials, network access, data policy, and audit below or around the model trust boundary.
Observable Outcomes
Correlate model and agent quality with service, platform, GPU, fabric, storage, and facility signals.
Lifecycle by Design
Define promotion, change, upgrade, rollback, backup, recovery, and ownership before production use.
Design Boundaries
Resolve the following questions before selecting implementation products:
Who owns facilities, hardware, network, storage, cluster, AI services, applications, and escalation?
Implementation Flexibility
The core describes required capabilities and interfaces. It does not select one Kubernetes distribution, inference engine, gateway, scheduler, registry, security product, or observability backend. Product and partner choices belong to an implementation and must be checked against current support documentation.
Keep Provider Integrations Replaceable
Keep application-facing contracts separate from provider-specific APIs. Use adapters behind stable inference, data, tool, identity, and telemetry interfaces where implementations differ. Preserve authorization, error handling, audit, and lifecycle behavior when replacing a provider; a matching API shape alone does not establish equivalent behavior or support.
Before selecting a component, record its required inputs, outputs, dependencies, owner, failure behavior, and replacement path. Use a published example implementation or catalog candidates to investigate concrete options, then confirm the complete composition with the responsible publishers.