> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/frontier-defense/mission-control.md).

# Mission Control

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FlJbOPhewiLsMLlyOP7jt%2Fimage.png?alt=media&amp;token=10f436dc-6493-4029-8d27-b524d58f5996" alt=""><figcaption></figcaption></figure>

Check your organization's elimination progress at a glance. See each project's and component's factory stage. Open the work that needs attention.

Mission Control is the CVEF dashboard and default home page. Four stage counters track work through Scan → Fix → Verify → Deliver. Each counter shows a live count and an action shortcut when needed.

| **Stage** | **What It Means**                      | **Action**                                                                                                                                                                        |
| --------- | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scan      | Projects that have finished scanning   | **AI Findings Pending Approval** opens scanned findings requiring approval.                                                                                                       |
| Fix       | Projects with a fix currently running  | **Premium fixes pending** opens hardened Gold rebuilds awaiting approval. These apply to components without a free Gold version. Approval queues the rebuild and raises a fix PR. |
| Verify    | Fixes being validated                  | None                                                                                                                                                                              |
| Deliver   | Fixes delivered as a pull request (PR) | **PRs pending Review & Merge** opens PRs for review and merging.                                                                                                                  |

The **Elimination Progress** dial shows eliminated vulnerabilities against the total found. For example, it can show 6,194 of 22,389. Summary cards link to the details on **Projects**, **Components**, and **Vulnerabilities**. A **Sources** panel lists project sources, such as GitHub repositories and Docker Hub images. Select **Add Source** to connect another source.

## Approving AI-Generated Fixes

Novel vulnerabilities and premium fixes always wait for your approval before CVEF changes anything. Approve them from the relevant Mission Control action.

### Approve a Novel Vulnerability (LVE) Fix

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2Fa0okAgVcanmretbxAKbw%2Fai-findings-pending-approval-gif.gif?alt=media&amp;token=0b7f39f7-a2df-41b1-b363-0a27de645fc8" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Open pending AI findings

From **Mission Control**, select **AI Findings Pending Approval** in the **Scan** stage. A list of pending LVEs opens, grouped by project.
{% endstep %}

{% step %}

#### Review the LVE

Click an LVE to open its detail panel and review the **Overview**, **Find Details**, and **Fix Details** tabs.
{% endstep %}

{% step %}

#### Approve the fix

Click **Approve — Raise Fix PR**. The finding moves from **Open** to **Pending Approval**, then **PR Raised**. CVEF prepares the fix in the background.
{% endstep %}

{% step %}

#### Review the pull request

CVEF opens a pull request in your repository. Its description lists resolved vulnerabilities, identifiers, severities, and descriptions. Merge after tests pass and the change is reviewed.
{% endstep %}

{% step %}

#### Merge the pull request

Review and merge the PR in your SCM. Merging changes the finding status to **PR Merged / Closed**. It also advances the project to **Deliver**.
{% endstep %}

{% step %}

#### Run a new scan

Run a new scan to confirm the vulnerability no longer appears.
{% endstep %}
{% endstepper %}

### Approve a Premium Fix

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FIdsctcEa9jaUYWB6jcyu%2Fpremium-fix-pending-approval-gif.gif?alt=media&amp;token=63286056-008f-46a2-92d7-ce813022e137" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Open pending premium fixes

From **Mission Control**, click **Premium fixes pending** on the Fix stage.
{% endstep %}

{% step %}

#### Review the pending item

Select a pending item to open its detail panel. The panel lists the affected component, current version, proposed Gold version, and project.
{% endstep %}

{% step %}

#### Review rebuild details

Review the vulnerabilities the rebuild resolves by exploitability and severity. Review the build-breaking-change risk, estimated effort, and premium-fix rationale.
{% endstep %}

{% step %}

#### Approve the premium fix

Click **Approve premium fix**. CVEF queues the rebuild and raises a pull request when ready. This workflow matches an approved LVE fix.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/frontier-defense/mission-control.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.