> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/quality-improvement/getting-started.md).

# Getting Started

SeaLights helps organizations and teams build a culture of continuous quality improvement by providing two approaches:

* **Release Quality Improvement** prioritizes immediate stability and release readiness.
* **Over Time Quality Improvement** builds long-term code quality and proactive risk reduction.

{% hint style="info" %}
SeaLights provides powerful data, but unlocking its full potential requires **thoughtful planning and process adjustments.** Here's what to consider:

* **Define processes:** Establish routines for analyzing test gaps, writing targeted tests, and determining appropriate test amounts.
* **Set KPIs:** Implement new metrics to track progress towards your quality goals.
* **Define release criteria:** Establish clear benchmarks for go/no-go release decisions, including coverage levels and acceptable risk thresholds.
* **Plan and checkpoint:** For the "over time" approach, plan a timeline, set coverage goals, prioritize improvements, and define clear release criteria.

[**Read more about SeaLights' Quality Improvement approaches**](/knowledgebase/guides/quality-improvement/challenges-and-approach-comparison/quality-improvement-approaches.md)
{% endhint %}

### Discover Quality Improvement

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quality Challenges &#x26; Approach Comparison</strong> </td><td>Explore common challenges hindering your path to quality excellence and discover powerful approaches that unlock sustained quality improvement. </td><td></td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/Vg4CdebglYSVRCFkBJB4/Royal%20Pink.png">Royal Pink.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/challenges-and-approach-comparison.md">Challenges &amp; Approach Comparison</a></td></tr><tr><td><strong>Quality Improvement Solution Overview</strong></td><td>Learn how to unravel your code's quality with granular coverage insights, and master two quality approaches for confident releases and long-term excellence. </td><td></td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/9ep80qmYsDaV0uWKu34y/Electric%20Lime.png">Electric Lime.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview.md">Quality Improvement Solution Overview</a></td></tr></tbody></table>

<table data-view="cards"><thead><tr><th></th><th data-hidden data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Managers</strong> use cases</td><td><a href="/knowledgebase/guides/user-story-coverage/use-cases-by-persona/managers.md">Managers</a></td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/p1hc9i8Jgo4mailUVTBf/Ocean%20Deep.png">Ocean Deep.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/use-cases-by-persona/managers.md">Managers</a></td></tr><tr><td><strong>Developers</strong> use cases</td><td><a href="/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers.md">Developers</a></td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/KxLRmuStX6nRl3Sssp7t/Ocean%20Deep%20copy.png">Ocean Deep copy.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/use-cases-by-persona/developers.md">Developers</a></td></tr><tr><td><strong>QA Engineers</strong> use cases</td><td><a href="/knowledgebase/guides/user-story-coverage/use-cases-by-persona/qa-engineers.md">QA Engineers</a></td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/2owC9rLj4bfJVzr9zfh8/Ocean%20Deep%20copy%202.png">Ocean Deep copy 2.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/use-cases-by-persona/qa-engineers.md">QA Engineers</a></td></tr></tbody></table>

### Technical Overview

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Report Mechanism</strong></td><td>Understand the high-level workings of Quality Improvement.</td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/ziCNGuoJop1bJMiRv0wn/Resemblance.png">Resemblance.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/technical-overview/solution-mechanism.md">Solution Mechanism</a></td></tr><tr><td><strong>Technical Architecture</strong></td><td>Delve into the intricate architecture of Quality Improvement solutions.</td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/CbPRHE9RXLQz0Xu72nIH/Resemblance%20copy.png">Resemblance copy.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/technical-overview/technical-architecture.md">Technical Architecture</a></td></tr><tr><td><strong>Deployment Guide</strong></td><td>Learn how to integrate Quality Improvement solutions in your teams.</td><td><a href="https://content.gitbook.com/content/Ysudbcd27UHLa2tTHHbh/blobs/pf7vv2n6Lu7WTSaPNdSj/Resemblance%20copy%202.png">Resemblance copy 2.png</a></td><td><a href="/knowledgebase/guides/quality-improvement/technical-overview/deployment-guide.md">Deployment Guide</a></td></tr></tbody></table>


---

# 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.sealights.io/knowledgebase/guides/quality-improvement/getting-started.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.
