Execution model

From intent to ground pass

Agents ask for outcomes. Groundpasse owns execution, safety, and proof. Here is the full path from a natural-language goal to an audited episode on real or simulated hardware.

Your agents & operators

Describe the job — not the steering.

Groundpasse

Verify, execute, protect, record.

Your robots

Move only after a ground pass.

  1. 1

    Request a job

    An AI agent or operator submits an intent — what should happen (e.g. “inspect aisle three”), not how to drive there. The intent names a goal, optional contract hint, inputs, deadline, and requester identity.

    Groundpasse accepts the request, validates the payload, and assigns the right robot if you run a fleet with capability routing.

  2. 2

    Match a verified behavior

    Groundpasse selects a behavior contract — a pre-approved, versioned recipe with safety rules, preconditions, and invariants already defined. The contract reference is pinned on the intent so audits always know which recipe ran.

    No ad-hoc instructions at runtime. If no contract fits, the intent fails fast with a clear reason.

  3. 3

    Check before moving

    Before any motion starts, the precondition engine evaluates gates defined in the contract: battery level, localization confidence, human clearance, equipment state, and custom expressions.

    If a check fails, the job stops safely — no partial motion, no silent override. The episode records exactly which gate blocked execution.

  4. 4

    Execute under guard

    The behavior executor runs the contract while the safety governor watches every command. Too fast? Clamped. Someone too close? Stopped. Zone violation? Blocked.

    The agent cannot bypass this layer — only a physical e-stop or operator override can halt motion outside the governor. Every intervention is logged.

  5. 5

    Record the episode

    When the job finishes — success, failure, or cancel — Groundpasse finalizes an episode: a complete diary of the run from intent acceptance through outcome.

    Replay it in the viewer, diff two runs to catch regression, or export a certification report for compliance and customer audit.

Nothing touches ground without a pass. The ground pass is explicit safety approval — preconditions satisfied, governor active, contract verified — before actuators move.

Key terms

Intent
A structured request describing what should happen. Agents submit intents; they do not drive motors.
Behavior contract
A versioned, reusable behavior definition with inputs, preconditions, invariants, and outputs.
Governor
The safety layer that enforces limits on every motion command in real time.
Episode
The full audit record of one intent execution — events, interventions, sensors, and outcome.
Ground pass
Approval to move: preconditions met, contract matched, governor armed.

Dive into the product capabilities behind each step.

Explore features Sim & Real