MODELS · AUTOPILOT · DESCRIBE THE RUN. SIGN THE GATE.

Describe the run. Set the check.

Describe the workflow in plain language. Inspect the plan. Set the checks the agent cannot skip. Every run leaves a record of who approved what.

DESCRIBE
Plain language in

State the job, the risk, the handoff — once.

APPROVE
Set the check

Reviewers, thresholds, evidence — set before launch.

RUN
On the record

Same check. Same review record. Every time.

THE PLAN

The plan, before it runs.

Input, review at the gate, approval out. Every node is named. Every gate has a reviewer. Nothing runs until the plan carries an identity-verified signature. That signature is the gate the agent cannot skip.

HOW IT WORKS

Three steps. One reviewed gate.

Describe the workflow. Sign the gate. Run it.

STEP 01
DESCRIBE

Describe the workflow

State the job in plain language. The risk threshold. The handoff. Autopilot turns the brief into a structured spec.

STEP 02
APPROVE

Sign the gate

The plan shows the steps, the reviewers, the escalations, and the record it will leave. You sign before anything runs.

STEP 03
RUN

Run it

The approved workflow runs on the same checks, the same reviewers, the same review record — every time it is used.

WHAT COMES OUT

What your team leaves with.

Every run leaves something the team can act on — and something the next launch has to clear.

01

Workflow specs

The structured brief — task, risk posture, handoffs, evidence rules — written down before anything runs.

↳ ARTIFACT
02

Approval gates

Named reviewers. Named thresholds. Named escalations. The plan everyone signs before launch.

↳ ARTIFACT
03

Run logs

Every node, every retry, every guardrail trip. The workflow's own readout, written as it runs.

↳ ARTIFACT
04

Signed run records

The approved plan, the inputs, the outputs, and the reviewer's signature — ready when someone asks who approved what.

↳ ARTIFACT
WHERE IT FITS

In the loop, this is where you test.

Five stages carry a model from change to release: test it, review the hard cases, recruit the right specialist, remember the misses, approve what ships. Autopilot owns the first stage — it describes the run, plans it, and puts it up for review.

01
Test
● YOU ARE HERE
02
Review
03
Recruit
04
Remember
05
Approve
RELATED MODULES

More of the Models toolkit.

TRAINING

The training run, written down.

Every run a record. Every record a fact.

See the page →
RL ENVIRONMENTS

Environments that hold still.

Deterministic worlds so the score means the same thing twice.

See the page →
CONTROL CENTER

The last check before it ships.

Tests, reviews, regressions, and compliance converge on one call.

See the page →
AUTOPILOT

Describe the run. Sign the gate.

Bring the workflow your team still rebuilds by hand. We'll turn it into a gate the team signs — and a run that leaves the record of who approved what.

Autopilot | Governed automation for repeatable workflows | AuraOne