Operator

What this feature is for

Operator reads workspace evidence, reports the tools it used, and requires approval before state-changing actions. It is a grounded assistant for triage and repeatable work. 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 connected workspace, a specific question, and a willingness to inspect evidence before acting on a recommendation.

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

Ask what changed, which risk matters most, or which check should run. Review the tool trace, approve only the intended write, and verify the result in its source feature.

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

Each answer should expose the evidence and tools behind it so the operator can audit the reasoning. 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

An answer without supporting evidence is not a diagnosis. Narrow the question, connect the missing provider, or open the source dashboard.

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 Operator with Activity, Health, Revenue Desk, Growth, and Automations. 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.