Release desk

What this feature is for

Release desk is where a team decides whether the evidence supports a deployment. It brings together recent audits, provider checks, GitHub signals, journeys, incidents, and policy so the gate reflects the actual app. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A candidate release, the app it belongs to, and a policy that distinguishes blockers from accepted warnings.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Open Release desk before promotion, review each blocker, run the missing check, and record an explicit waiver only when the owner and expiry are understood.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The verdict links each blocker to its source and gives CI or a reviewer a stable decision rather than a screenshot of a dashboard. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

If the desk cannot decide, look for stale evidence, a missing provider, an unreachable environment, or a policy that is stricter than the release intent.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use GitHub checks and Journey Canary for the candidate, then Health and Revenue for post-deploy observation. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.