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

# Grading

> Issue severity and the PR merge score.

Jina validates findings against the code and investigation evidence before grading them. It considers impact, likelihood, affected functionality, evidence strength, and unresolved limitations.

## Issue severity

Each validated issue receives a severity:

| Severity | Meaning | Illustrative example |
| - | - | - |
| **P0 — Critical** | Core flows or critical guarantees are broken; data integrity is threatened. | A common write path corrupts customer records. |
| **P1 — High** | Important functionality is materially broken. | A payment retry charges twice. |
| **P2 — Medium** | Bounded degradation with a workable alternative. | One filter returns incorrect results; another view works. |
| **P3 — Low** | Minor, rare, or limited impact. | A secondary status message is misleading. |

## Pull-request merge score

The `1`–`5` score is a holistic assessment of the PR's remaining merge risk. It is not a count of issues or an average of scenario scores.

| Score | Meaning |
| - | - |
| **5/5** | Merge ready: no substantive issues, or negligible impact. |
| **4/5** | Merge is probably fine: minor issues with limited practical impact. |
| **3/5** | Merge is okay, fixes recommended: meaningful but bounded, acceptable risk. |
| **2/5** | Fix before merge: a credible production failure, less severe, likely, or widespread than a `1`. |
| **1/5** | Fix before merge: severe production failure is likely. |

For example, an ordinary retry that duplicates a payment could warrant `2/5`; a minor display defect could warrant `4/5`. These are illustrative, not fixed mappings. Severity alone does not determine the PR score.

Scenarios have execution results and findings, not numeric grades. A failed or blocked investigation is not a pass; read its limitations alongside the score.

## Customize the rubric

Use `.jina/instruction.md` to describe how your product's risks affect grading. For example:

```markdown .jina/instruction.md theme={null}
- Block merge when a supported payment retry can charge twice.
- Treat receipt-formatting defects as minor when payment details remain correct.
```

You can customize the interpretation, but severities remain `P0`–`P3` and PR scores remain integers from `1` to `5`. Instructions cannot override evidence requirements.

The file is read from the PR's base commit. Use the [setup prompt](https://docs.usejina.com/simulations/customize-jina.md#generate-your-instruction-with-a-coding-agent) to choose repository-specific preferences.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.