Skip to content

OPEN SPECIFICATION

Community Draft 0.1

CARS Chemistry AI Recipe Specification

An open, vendor-neutral initiative for describing, sharing, validating, and connecting AI-powered chemistry workflows.

View the Specification Join the Discussion
Build a CARS Manifest in WorkBuddy
Third-party service

About WorkBuddy

This feature is provided by WorkBuddy, a third-party service, and is not an official ChemAI Atlas runtime.

Opens an external website. Data processing and service use are governed by WorkBuddy’s own terms.

This experimental app supports setup assistance for some Recipes; direct execution is not guaranteed.

Why CARS?

Describe the chemistry. Share the workflow.

A shared description of purpose, data, and evidence can make chemistry AI workflows easier to understand and reuse across tools.

Interoperability
Describe a Recipe independently of any single tool, model, or execution environment.
Scientific Transparency
Record inputs, outputs, methods, limitations, validation evidence, and data sources.
Reusability
Reduce the effort of repeatedly assembling similar chemistry AI workflows.

THE RECIPE MODEL

Define → Validate → Connect

Separate the scientific intent of a task from its implementation, then describe the checks and connections it needs.

  1. Define

    State the task, chemical inputs and outputs, units, capabilities, and dependencies.

  2. Validate

    Distinguish structural checks from semantic consistency, execution tests, and scientific evidence.

  3. Connect

    Explore mappings to existing tools and workflow runtimes through optional adapters.

This is a conceptual flow, not an executable pipeline. The reference validator currently checks L0 structure only; execution adapters remain exploratory.

molecular-descriptors.yamlManifest excerpt
cars_version: "0.1.0"
task: "molecular_descriptor_calculation"
inputs:
  - id: "molecule"
    type: "chemical_structure"
    required: true
    formats: ["smiles"]
    constraints:
      stereochemistry: "preserve_if_present"
      mixture_policy: "reject"
outputs:
  - id: "descriptors"
    type: "molecular_properties"
    formats: ["application/json"]
    properties:
      - name: "molecular_weight"
        unit: "g/mol"
        result_kind: "deterministic_calculation"
scientific:
  method: "Structure validation followed by descriptor calculation"
  applicability: "Single-component organic molecules supported by the chosen toolkit"
  limitations:
    - "Input representation and normalization affect computed values"
  validation_status: "not_assessed"

Source on GitHub ↗ChemAI Atlas · CC BY 4.06c2049c

FROM THE REPOSITORY

Molecular Descriptor Calculation

An illustrative Recipe published in the CARS repository. It describes a molecular structure input and a calculated molecular property output.

Input contract
A required chemical structure in SMILES format. Mixtures are rejected; stereochemistry is preserved if present.
Output contract
JSON molecular properties, including molecular weight in g/mol, declared as a deterministic calculation.
Evidence status
not_assessed — the example does not claim scientific validation or provide tested numerical results.

Selected fields are shown verbatim from a pinned repository snapshot. Other fields are omitted; refer to the original for the complete example. Its declared CWL binding does not demonstrate an implemented adapter.

View the Specification

Design Principles

Open and vendor-neutral, chemistry-aware, and built around existing standards. Describe provenance, assumptions, and limitations explicitly; keep schema validity, semantic consistency, execution success, and scientific evidence distinct. Extensions should remain transparent.

CWL, MCP, Agent Skills, and OpenAPI/Arazzo are interoperability discussion topics, not claims of implemented support or certification.

OPEN RFCS

Help Shape the Specification

CARS 0.1 welcomes feedback from chemists, researchers, scientific software developers, and AI practitioners.

Join GitHub Discussions
  1. Ideas & Proposals

    RFC: Chemistry-Specific Data Types

    How should CARS describe molecular structures, reactions, spectra, and scientific units?

    Discuss this RFC
  2. Scientific Validation

    RFC: Scientific Validation Framework

    How should CARS distinguish schema checks, execution success, and scientific credibility?

    Discuss this RFC
  3. Ideas & Proposals

    RFC: Execution Adapters and Interoperability

    Which existing workflow protocols and runtimes should CARS connect to first?

    Discuss this RFC

Project Status

Community Draft 0.1View Roadmap ↗
  1. Current

    Draft specification

    Open review, RFC discussions, and iteration on the provisional schema and examples.

  2. In progress

    Reference examples & validation

    Initial examples and an L0 structural validator are available. Broader validation and compatibility checks remain under development.

  3. Exploratory

    Execution interoperability

    Evaluate adapters, interoperability, and reference implementations; the draft is not a workflow engine.

Contribute to CARS

Help make chemistry AI workflows more reusable, transparent, and interoperable.

View Pull Requests

Discuss

Ask questions, share chemistry use cases, and give feedback on the draft design.

Report & Propose

Submit clear bugs, feature requests, or improvements that can be tracked through Issues.

Contribute Code & Docs

Read the contribution guide and use Pull Requests to improve schemas, examples, and documentation.

Cite the specification

ChemAI Atlas. Chemistry AI Recipe Specification (CARS). Community Draft 0.1. https://github.com/chemaiatlas/chemistry-ai-recipe-spec/blob/main/SPECIFICATION.md

Use the repository revision or release that you consulted when citing the draft. The repository remains the authoritative source.

What Is CARS? A Guide to the Chemistry AI Recipe Specification