Contracts

This section describes the stable promises Atlas intentionally makes.

flowchart LR
    Contracts[Contracts] --> API[API compatibility]
    Contracts --> Output[Structured output]
    Contracts --> Config[Runtime config]
    Contracts --> Plugin[Plugin surface]
    Contracts --> Artifacts[Artifact and store]
    Contracts --> Ops[Operational contracts]
    Contracts --> Ownership[Ownership and versioning]

This map names the stable promises Atlas chooses to publish. A page belongs in this section only when it describes behavior that reviewers, operators, or downstream users are expected to rely on.

flowchart TD
    Promise[Promise] --> Docs[Documentation]
    Promise --> Tests[Test enforcement]
    Promise --> Review[Review and release decisions]

This diagram explains how Atlas treats a contract: it is not just prose. A contract should connect to test enforcement and release decisions so the promise remains credible over time.

Pages in This Section

• API Compatibility
• Automation Contracts
• Structured Output Contracts
• Runtime Config Contracts
• Plugin Contracts
• Artifact and Store Contracts
• Operational Contracts
• Ownership and Versioning

Purpose

This page defines the Atlas contract expectations for contracts. Use it when you need the explicit compatibility promise rather than a workflow narrative.

When to Reach for This Section

• a change might alter a documented compatibility promise
• you need to know whether a behavior is intentionally stable
• a release, review, or downstream integration decision depends on a clear promise

Stability

This page is part of the checked-in contract surface. Changes here should stay aligned with tests, generated artifacts, and release evidence.