> 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/overview.md).

# Overview

What Heeler is, the model it builds of your software, and how the Prevent, Fix and Operate layers use that model.

Heeler is an application security platform. It connects to your source control, cloud accounts and artifact registries, builds a model of your software from what it finds there, and uses that model to check code before it merges, generate and validate fixes, and track every finding through to a deployed remediation.

This section defines the product and the model behind it. To connect your first source, go to [Get Started](/mrecEO40m5D6bt7Pq5pE/get-started.md).

## The three layers

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Prevent</strong></td><td>Checks that run in the coding agent, in the CLI, and on every pull request.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/prevent.md">Prevent</a></td></tr><tr><td><strong>Fix</strong></td><td>Generated dependency and code changes, validated in your CI and opened as pull requests.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/fix.md">Fix</a></td></tr><tr><td><strong>Operate</strong></td><td>Continuous detection, SLOs, routing workflows, and dashboards over the open queue.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/operate.md">Operate</a></td></tr></tbody></table>

## In this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What Heeler Is</strong></td><td>What the product does, and the conditions it is built for.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/overview/what-is-heeler.md">What Heeler Is</a></td></tr><tr><td><strong>The Context Model</strong></td><td>The six inputs the model is built from, and how it stays current.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/overview/the-context-model.md">The Context Model</a></td></tr><tr><td><strong>Prevent, Fix and Operate</strong></td><td>What each layer does and where the three overlap.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/overview/three-layers-one-model.md">Prevent, Fix and Operate</a></td></tr></tbody></table>

## Related

* [Get Started](/mrecEO40m5D6bt7Pq5pE/get-started.md) — connect source control, cloud and registries.
* [Supported Technologies](/mrecEO40m5D6bt7Pq5pE/supported-technologies.md) — languages, package ecosystems, SCMs, clouds, registries and integrations.


---

# 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/overview.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.