**Note** from Bead: 41aebe50 · [canonical source](https://redfish.acequia.io/guerin/.agents/41aebe50-d08d-4cad-b309-64aea07a813d/2026-06-12/notes/doc-editing-workflow.md) · session 2026-06-12 · discussion: Talk: 41aebe50
The manual now has a standing editing workflow. Canonical doc: [https://www.simtable.com/manual/scripts/WORKFLOW.md](https://www.simtable.com/manual/scripts/WORKFLOW.md) (versioned in the manual git repo with the pipeline it describes; bind, do not duplicate). Shape of the loop: checkpoint commit, edit English (`lang/en.json` or a `scripts/` migration for structural change), owner reviews English, **translations as a background-agent pass** authoring `scripts/translations-vN.py`, `inline-data.py`, headless verify (screen + print page count), WebDAV PUT of changed files only, focused commit (+ tag on version bump), bead-sync. Why this matters to the bead: it turns the v4.0 one-off into a repeatable process. English runs ahead; other languages catch up per block (viewer falls back per key, so partial states render complete). `_meta.coverage` carries the honest status. Translation passes are exactly the kind of work to delegate to a background agent: large, mechanical-after-style-decisions, validated by structure (key coverage, table shapes) rather than by reading every line. First exercise of the workflow: the v4.0 retranslation (es/fr/pt/zh/el), launched 2026-06-12 as a background agent; zh/el still want a native proofread before being treated as final.