# 2026-05-14 — Tier 1-A Translation Schema

## Result

Tier 1-A completed across four executor sprints:

- Sprint 1: `axis-implementation-map.md` split into `axis-implementation-map.json` + JSON Schema.
- Sprint 2: `prop-aliases.md` split into `prop-aliases.json` + JSON Schema.
- Sprint 3: `divergences.md` split into `divergences-decisions.json` + JSON Schema.
- Sprint 4: added `audit:translation-completeness` as the 10th strict release gate.

The translation layer now has machine-checkable JSON SoT files while the Markdown files remain as narrative context.

## Gate

New strict gate:

```bash
pnpm run audit:translation-completeness
```

The audit checks:

- JSON Schema validity for the three Tier 1-A JSON files.
- Production Figma component coverage against translation metadata.
- Translation prop aliases against canonical/base Vue files.
- Axis and resolved-divergence verify hints.
- `icon-aliases.ts` references against the published icon manifest.
- `token-aliases.ts` bidirectional consistency and Figma token/style references.

Current result: `activeFindings: 0`, with 10 explicit allowlisted findings for known Tier 1-A out-of-scope production sets or pre-existing verify-hint/alias decisions.

## Follow-Up

- `BreadcrumbItem.showIcon` in `prop-aliases.json` is allowlisted because code currently exposes `showSeparator`; this needs a dedicated plan-owner decision before mutating translation SoT.
- Popup Box / Drop down List / Chart / Slider / Rating coverage findings are allowlisted until those published sets enter the current canonical/Figma alignment scope.
- Two divergence verify hints remain prose/script-level rather than grep/rg; the new audit documents this without changing existing decisions.

## Impact

v0.3.0 no longer carries Tier 1-A as active work. Remaining v0.3 scope is Phase 6.3, Phase 6.4, and BRIDGE-005.