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

# Review and remediation

> Move from evidence to a verified fix

TurenOS combines conversational work with source review, diffs, line comments, terminals, and security evidence.

## Review workflow

1. Ask for a bounded review objective and risk model.
2. Require findings with file and line evidence.
3. Rank confirmed defects by impact rather than listing style preferences.
4. Apply the smallest safe change.
5. Run package-scoped tests, typechecks, or security checks.
6. Reinspect the final diff and report residual risk.

## Review panel

The review panel presents changed files and line-level context alongside the session. Comments remain attached to the relevant file and range where possible.

## Adversarial review

High-risk changes can be delegated to a read-only adversarial reviewer that reconstructs behavior independently and checks authorization, persistence, concurrency, retry, cancellation, recovery, and protocol compatibility.

## Evidence preservation

Prefer reproducible evidence: source locations, exact commands, test output, hashes, captured HTTP flows, or static analysis metadata. A security finding should distinguish confirmed behavior from hypotheses and unresolved external state.