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

# How Jina Works

> See how Jina turns system context into targeted runtime investigations, validated findings, and a merge score.

# How Jina Works

From pull request to merge decision in four steps.

## 1. Build the context layer

* Map code, infrastructure, runtime behavior, and past issues.
* Connect the services, state, and flows behind the change.

**Outcome:** A review grounded in your system, not just the diff.

## 2. Plan from blast radius

* Trace what changed and everything that depends on it.
* Prioritize the product flows most likely to break.

**Outcome:** Time spent on the highest-risk paths.

## 3. Investigate with execution

* Run targeted probes, simulations, and checks.
* Follow new evidence into the next investigation round.

**Outcome:** Runtime proof instead of theoretical warnings.

## 4. Review and score

* Remove unsupported findings and group related failures.
* Report root cause, impact, evidence, and merge risk.

**Outcome:** A concise issue list and a clear merge score.

`Pull request` → `context layer` → `blast radius` → `runtime investigation` → `validated issues and merge score`

Next, learn how the [context graph](/concepts/context-layer) guides each investigation.