Explore in 3DBook a demo
The Release wing · 1 agent

Ship it, with a way back.

Release promotes exactly what was verified. The Prod deployment agent moves the same build that passed Verify into production in steps, checks health between every one, and keeps the previous version ready. If a step looks wrong, it stops and steps back before your users notice.

Book a 30-minute demoMeet the agents
PDProd deployment agent#0622
Reads
The verified build, its test evidence, health thresholds
Produces
A staged rollout to production, with a way back
Approval
Given at the Verify gate. No second gate: health checks guard every step

The way back is prepared before the way forward, never written during an incident.

How it works

Small steps. Checked every time.

A small share of traffic first, then more, with error rate and latency checked against thresholds before every step.

Reads

Verified build
Test evidence
Health thresholds

Agents

PDProd deployment agentAgent #0622

Produces

Stepwise rollout
Health check per step
Rollback, ready
Live in production

Checks

Health checked at every stepApproved at Verify · 16:05
Operate
The agents

Meet the agent.

Each one has a codename, one job and a record of everything it did. These views show a sample project.

PDProd deployment agentAgent #0622

Promotes the build that passed. Nothing else.

It confirms the build in front of it is exactly the one Verify approved, then rolls it out in steps, a small share of traffic first, with error rate and latency checked against thresholds at every step. The previous version stays warm, so stepping back is one action, not an incident.

Reads

  • The verified build
  • Health thresholds
  • The Verify gate sign-off

Produces

  • A stepwise rollout
  • Health evidence for every step
  • An instant way back
Prod deployment agent · sample project, illustrative
Health checks · every step

No second gate. Every step earns the next.

The person who signed the Verify gate approved this build for release, so nothing waits between Release and Operate. What guards production is the rollout itself: error rate and latency checked against thresholds before every step, and a step back the moment one fails.

Rollout checksRelease → Operate
  • The build is exactly the one signed at the Verify gate
  • Error rate under threshold before every step
  • Latency under threshold before every step
  • A failed check steps back to the previous build
LM
L. MoreauQA lead
Signed at Verify · 16:05
Guardrails

What the Release wing never does.

  • Only the verified build is promoted. Nothing is rebuilt on the way to production.
  • A failed health check stops the rollout.
  • Rollback is prepared before the deploy, not during an incident.
The red thread

One ID, through Release.

  1. Build1.4.0
  2. Signed16:05
  3. Canary5% → 25%
  4. Live100%
  5. DeliveredBRQ-0014

When the rollout completes, the requirements it carried are marked delivered, and the goal they serve can be measured in production.

  1. AnalyzeRead the system you already have
  2. PlanTurn the goal into testable requirements
  3. BuildTests first, then the code
  4. StageStand it up somewhere real
  5. VerifyProve it works, requirement by requirement
  6. ReleaseShip it, with a way back
  7. OperateKeep watching, close the loop
See it on a real project

Watch Release run, in thirty minutes.

We open Orlian on a live project and walk you through the Release wing: what goes in, what the agents produce, and where a person signs. No slides.

Book a 30-minute demoSee it on the campus