Production Workflows
Processes that survive contact with a real release
These workflows use the windows and services that exist in 1.0.0. Where a step is manual, it says so. None of them assumes a feature that is not shipped.
The workflows
| Workflow | Use it when |
|---|---|
| First Multilingual Release | You are taking a monolingual project into its first set of locales |
| Translator Round-Trip | You send strings out and receive translations back |
| Narrative Iteration | Writers change dialogue while translations are in flight |
| Hotfix & Patch | You need to ship a small correction to a live build |
| CI Release Gates | You want automated evidence, with a custom headless entry point |
The shared spine
All five workflows follow the same spine:
source strings
│ ingest (adapter or your own script)
▼
workspace revisions ──► review states ──► approvals
│ │
├── handoff export ──► translator ──► import plan ──► apply
│ │
├── capture matrix ──► visual findings │
├── voice / subtitles ─────────────────┤
│ ▼
└──────────────────────────────► release gate report
If a step is missing from your project, the spine still works — it just has a manual gap. The most common gap is source ingestion: 1.0.0 has no import window.
Rules that keep the process honest
- Never carry an approval across a source change without re-review.
- Never treat an unvisited capture tile as a pass.
- Prefer JSON for three-way imports; CSV is lossy.
- Archive the gate report with the build, not in a chat message.
- Record who applied an import; the journal records the reviewer label.
- Decide explicitly what the gate does not check (text rules, glossary, duration mismatch) and cover it elsewhere.