Editor's Guide
For editors and translators who review AI drafts and finalize translations
1Your Role
As an editor, you are the quality gatekeeper. Every passage already has an AI-generated v0.1 draft. Your job is to review it against the source text and community feedback, then revise and finalize. Every version after v0.1 is a human-driven result. You are assigned specific books and chapter ranges.
2Editing Workflow
A. Discuss & Adopt
Check the discussion panel for community comments and replies to understand reader feedback on the current translation. Share your own views and toggle the 'Adopt' switch on helpful suggestions.
B. Review Translation
With discussion feedback in mind, review the current translation on the pericope page. Use the reference panels (Greek interlinear, exegesis rules, cross-references) to verify accuracy and identify what needs changing.
C. Edit Text
Click 'Edit' to open the USFM editor. Choose between Rendered view (WYSIWYG), Raw USFM (text with markers), or Diff view. You can switch between views while editing.
D. Submit Version
Add a commit message and click 'Submit' to create a new version. Each submission generates a unique version record that can be viewed and compared in the version history.
3AI Review Tool
On any comment, click 'AI Review' to get an AI analysis covering: theological accuracy against source text, lexical consistency with the exegesis rules, and contextual coherence within the pericope. You can post the AI analysis as a reply for transparency.
4Version Control
Every submission creates a commit with a unique hash. The version timeline shows all commits chronologically. You can compare any two versions to see exactly what changed — additions in green, deletions in red.
5Adopting Comments
When a community suggestion improves the translation, toggle the 'Adopt' switch on the comment. This logs the decision and notifies the commenter. Adopted suggestions are tracked in the commenter's profile stats.