Transparency
Revisions
Every approved edit is kept as a public record. This page shows the most useful numbers — significant approved revisions, the larger applied-revision history, and where each change appears in context.
How a revision happens
1. A change is proposed
A reader note, maintainer proposal, or review pass points to a source-grounded improvement.
2. Evidence is weighed
Source text, context, AI review, and human judgment are checked.
3. Approved edits land
Accepted wording, rationale, and any public credit stay in history.
What counts as a revision?
A revision is a targeted change to a committed verse — an English polish, a restored rhetorical force, a preserved wordplay, or a project-wide consistency fix (like the Χριστός → Messiah normalization). Revisions don't overwrite the original draft; they layer on top, and the previous rendering is kept as a footnote on every revised verse. Detailed policy in REVISION_METHODOLOGY.md.
What do the tiers mean?
Tier 1 is mechanical stylistic polish — awkward English cleaned up where the suggested rewrite shares most of its words with the draft. These are auto-applied with a word-overlap safety check.
Tier 2 is Claude Opus 4.7 adjudicating Gemini's flagged majors — mistranslations, lexical fixes, and grammar losses whose rationale cites specific Hebrew / Greek evidence. A Tier-2 rewrite is only applied if the rationale grounds the change in BDAG, HALOT, BDB, or in source-language grammar.
Anything requiring policy judgment (theological weight, cross-verse consistency) is escalated to a human rather than auto-applied.