# Feature Specification: Localization work orders

**Feature ID**: 003
**Status**: draft

## Overview

A detected change produces a flag saying a content unit is stale, which states neither how much
of it existing approved translations already cover nor what about it is risky, so every change
costs a manual assessment before anyone can act.

## Functional Requirements

- **FR-001** When a change requires translation, the evaluator shall state the proportion of its
segments already covered by approved translations.
- **FR-002** When a change introduces a term with no approved rendering, the evaluator shall
flag the term for decision.
- **FR-003** If an approved rendering conflicts with agreed terminology, then the evaluator shall
report the conflict and shall not resolve it.
- **FR-004** The evaluator shall distinguish text legitimately identical in both languages from
text left untranslated in error.
- **FR-005** If translated text instructs a reader to select a named control, then the evaluator
shall flag the instruction when that control's label is translated elsewhere.
- **FR-006** Where evaluation is ambiguous, the evaluator shall escalate rather than assume the
lower-effort reading.


## Acceptance Criteria

- **003-localization-work-orders-AC-1** A work order states a coverage percentage; the sampled baseline is 89.5% on one page.
- **003-localization-work-orders-AC-2** A term absent from both the terminology authority and approved translations appears
as an escalation with a recommendation.
- **003-localization-work-orders-AC-3** A segment on the keep-in-source list is not reported as untranslated.
- **003-localization-work-orders-AC-4** Two approved translations currently carry retired wording; both are reported as
conflicts.


## Deferred Edge Cases

- **DEF-1** Effort estimation in time rather than segment counts. Deferred: no measured
throughput baseline exists.