> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/operate.md).

# Operate

Run the remediation lifecycle without an operator — see the state of the queue, automate the response, set the clock, and query from Slack — with Heeler running the loop, not a person.

**Operate** covers the surfaces that run the remediation lifecycle without a person dispatching each step: workflows that act on new findings, SLOs that put each one on a deadline, dashboards over the open queue, and a Slack interface for queries. Each is configurable, and each reports what it did.

Heeler continuously detects and scores risk across the four [Findings](/mrecEO40m5D6bt7Pq5pE/findings.md) domains; the pages here are the surfaces where that loop is **visible and, where you want it, tunable**:

* **Automate the response** — [Workflows](/mrecEO40m5D6bt7Pq5pE/operate/workflows.md) open tickets, notify the right owners, apply SLO changes, and trigger agentic fixes — automatically.
* **Set the clock** — [Service Level Objectives](/mrecEO40m5D6bt7Pq5pE/operate/service-level-objectives-slos.md) put every finding on a deadline by risk or severity, and [Exceptions and Overrides](/mrecEO40m5D6bt7Pq5pE/operate/exceptions-and-overrides.md) is where you review what's been let off it.
* **See the state of the loop** — [Dashboards](/mrecEO40m5D6bt7Pq5pE/operate/dashboards.md) show where risk concentrates, what's on the clock, and how fast it's closing.
* **Query from anywhere** — [Heeler in Slack](/mrecEO40m5D6bt7Pq5pE/operate/heeler-in-slack.md) answers findings, SLO, and vulnerability questions right in your workspace.

{% hint style="info" %}
The loop only runs as well as it can see and act. If findings aren't routing, aren't on a clock, or aren't getting fixed, the cause is usually a missing connection — see [how to check each part of the loop](/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/run-unattended-dependency-remediation.md#check-its-working).
{% endhint %}

## In this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Workflows</strong></td><td>Trigger → condition → action automation — ticketing, notifications, SLO changes, and agentic remediation.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/workflows.md">Workflows</a></td></tr><tr><td><strong>Service Level Objectives (SLOs)</strong></td><td>The remediation clock every finding runs against.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/service-level-objectives-slos.md">Service Level Objectives (SLOs)</a></td></tr><tr><td><strong>Exceptions and Overrides</strong></td><td>The register of live risk and SLO exceptions — who granted each one and when it lapses.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/exceptions-and-overrides.md">Exceptions and Overrides</a></td></tr><tr><td><strong>Campaigns</strong></td><td>Declare CVEs as a campaign and track every affected instance to closure.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/campaigns.md">Campaigns</a></td></tr><tr><td><strong>Developer Agent Activity</strong></td><td>Coding-agent sessions, workstation tooling, and workstation security posture.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/developer-agent-activity.md">Developer Agent Activity</a></td></tr><tr><td><strong>Dashboards</strong></td><td>Priorities, remediation planning, coverage, and trend reporting.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/dashboards.md">Dashboards</a></td></tr><tr><td><strong>Heeler in Slack</strong></td><td>Query findings, SLO status, and vulnerabilities from Slack — slash commands, the <code>@Heeler</code> assistant, and link previews.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate/heeler-in-slack.md">Heeler in Slack</a></td></tr></tbody></table>

## Worked example

See this inside a full SLO-driven program:

{% content-ref url="/pages/qXynZJ6ysecRvAHjNFOM" %}
[Run an SLO-Driven AppSec Program](/mrecEO40m5D6bt7Pq5pE/solutions-and-use-cases/run-an-slo-driven-appsec-program.md)
{% endcontent-ref %}

## Related

* [Findings](/mrecEO40m5D6bt7Pq5pE/findings.md) — what Heeler detects, how it's scored, and the Active → Fixed → Deployed lifecycle.
* [Fix → Prioritize](/mrecEO40m5D6bt7Pq5pE/fix/prioritize-heeler-risk.md) — turn priorities into an ordered backlog.
* [Respond & Govern](/mrecEO40m5D6bt7Pq5pE/administer-and-monitor/program-policy.md) — the license, routing, and ticket-closing policy behind the automation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/operate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.