Documentation preview

A release model that both engineers and automation can inspect.

RobotAtom represents configuration, evidence, policy and deployment decisions as connected, versioned records. This preview documents the intended interface; production API availability will be published separately.

Core concepts

Four records control the release path.

release

Release

The exact hardware, firmware, software, model and target environment.

evidence

Evidence

A result from simulation, replay, hardware or field evaluation with provenance.

policy

Policy

The evidence, thresholds and reviewers required for a deployment scope.

decision

Decision

An accountable approval, hold, block or rejection attached to the release.

Release manifest

Identify the candidate before evaluating it.

A manifest binds the versioned system configuration to an approved baseline and a target deployment environment.

release.manifest.jsonIllustrative
{
  "release_id": "REL-2841",
  "robot": "atlas-amr",
  "version": "2026.07.3-rc2",
  "baseline": "2026.06.8",
  "changes": {
    "model": "nav-4.8.0",
    "firmware": ["os1-3.1.0"],
    "software": ["planner-8.14.2"]
  },
  "target": {
    "environment": "warehouse-production",
    "fleet_scope": 184
  }
}

Evaluation evidence

Preserve result boundaries and provenance.

An evidence record describes what ran, against which release, under which conditions, with what result and where the supporting artifact remains available.

FieldMeaning
sourceSimulation, replay, hardware-in-the-loop or field test
suiteVersioned evaluation suite and scenario selection
conditionsHardware, environment and runtime parameters
metricsMeasured output, unit and acceptance threshold
provenanceRunner, timestamp, commit and artifact reference
limitationsKnown exclusions and non-covered operating conditions

Deployment decision

Make approval a durable engineering record.

A decision evaluates the release and its evidence against a policy scoped to a fleet, site or operating environment.

deployment.decision.jsonIllustrative
{
  "release_id": "REL-2841",
  "gate": "warehouse-production",
  "decision": "blocked",
  "reasons": [
    "2 replay regressions require disposition"
  ],
  "evidence_coverage": 0.94
}

Integration model

Connect events at the points your release already changes state.

1

CreateCI registers a release candidate and its manifest.

2

AttachEvaluation systems report evidence and artifact references.

3

EvaluateRobotAtom applies policy and exposes required dispositions.

4

DecideAn authorised reviewer approves or blocks promotion.

5

ObserveFleet events remain traceable to the deployed release.

Designing an integration?

Share one existing release pipeline and the systems that produce its evidence.

Request an integration review