> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entelligence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Code Reliability

> Use production incident patterns and observability audits to find recurring risk, propose fixes, and monitor whether fixes hold.

<video src="https://mintlify.s3.us-west-1.amazonaws.com/entelligence-c3217b42/videos/Clipboard-20260727-164345-613-compressed.mp4" controls />

Code Reliability turns production signals and repository context into two focused workflows: learn from recurring incidents and find observability gaps before they become incidents.

## Choose a workflow

<CardGroup cols={2}>
  <Card title="Incident Knowledge" icon="wave-pulse" href="/code-reliability/incidents">
    Group repeated detections into patterns, connect them to the owning repository, and track fixes after deployment.
  </Card>

  <Card title="Observability Audit" icon="radar" href="/code-reliability/observability">
    Score a repository, inspect coverage, and turn P0–P3 workstreams into an improvement plan.
  </Card>
</CardGroup>

## What you can do

* See which production patterns are active, growing, dormant, or regressing.
* Open the evidence behind a pattern before acting on it.
* Generate a fix pull request and keep normal review and branch protection.
* Audit logging, metrics, tracing, health checks, and related observability practices.
* Compare coverage and recommendations across a repository.

<Warning>
  **Fix Now** creates repository work. Review the evidence, target repository, generated diff, tests, and rollout plan before merging.
</Warning>

## Start here

Open [Incident Knowledge](/code-reliability/incidents) for production patterns, or run an [Observability Audit](/code-reliability/observability) for a repository.