Week ending 8/2

Executive summary

This week the pipeline had its biggest single-week jump yet: 19 more languages completed a full New Testament, taking the total from 38 to 57, while a bootstrap fix onboarded three brand-new languages (Afar, Amharic, Oromo). Translation Studio grew a full guided project workflow — Step 1/2/3 setup, reusable source documents, a 9-phase lifecycle display, and a Translator Worker API foundation for unattended execution — alongside private per-project document storage. A production deploy failure, the third deploy-time incident in three straight weeks, briefly kept one of this week's own UI fixes off production before being diagnosed and resolved the same day.

What's new

• Change

  19 more languages reached a complete New Testament this week, led by Odia, Sanskrit, Telugu, and Kannada. The total jumped from 38 to 57 languages.

  Impact

  Book pages live in the Library grew from 1,441 to 1,938. This is the pipeline's second major depth jump in three weeks.

  Next action

  Route this week's new Critical- and High-risk doctrine flags to reviewers.

• Change

  Fixed a bootstrap gap that blocked brand-new languages from starting. Romans then published for three first-timers: Afar, Amharic, and Oromo.

  Impact

  The Library now covers 66 languages total, up from 63 last week.

  Next action

  Carry these three through the same pipeline that reached 57 others.

• Change

  Shipped a guided Step 1/2/3 workflow with reusable documents and per-project rule overrides. Added a 9-phase lifecycle status display and manual start control.

  Impact

  Creating and running a translation project is now a single guided flow instead of scattered screens.

  Next action

  Walk a real ministry partner through creating their first project end to end.

• Change

  Gave each project its own private storage folder. Shipped a Translator Worker API foundation for unattended project execution. The worker never holds a database or storage credential.

  Impact

  Translation projects can now run unattended by an external process, not just interactively in the browser.

  Next action

  Connect a first real external worker to the new API.

• Change

  Fixed document upload, preview, and download reliability issues. Reorganized folders to collapse by default with a shared Uploaded folder.

  Impact

  Browsing a workspace's documents is faster and no longer implies uploads are unorganized.

  Next action

  Confirm the reorganized document picker still reuses uploads across multiple projects correctly.

• Change

  A production deploy failed when a migration hit a column already added by hand. Diagnosed and fixed the same day by making the migration idempotent.

  Impact

  This is the third straight week with a deploy-time database incident. It was self-healed the same day with no lasting downtime.

  Next action

  Add a pre-deploy check that catches non-idempotent migrations before they reach production.

Business impact

57 languages with a complete New Testament, up from 38, is the platform's largest content-depth jump since the pipeline scaling breakthrough two weeks ago, and it pushes to 57 the languages now needing doctrine-flag review capacity that leadership has not yet staffed. Translation Studio's new guided workflow, reusable documents, and Translator Worker API foundation move it from a dashboard prototype toward something that can run a translation project end to end, including unattended, non-human execution.

Metrics

• Languages with a complete New Testament

  57(was 38) ▲ Up from last period

• Languages with a complete Old Testament

  10(was 10) → No change from last period

• Book pages live in the Library

  1,938(was 1,441) ▲ Up from last period

• Languages with a published Library bundle

  66(was 63) ▲ Up from last period

Risks

This is the third consecutive week with a deploy-time production incident: a migration collided with a column that had already been added by hand directly to production earlier the same day, failing the deploy and leaving this week's own folder/Uploaded-folder UI fix invisible in production for several hours until it was diagnosed and resolved. Doctrine-flag review capacity, already a stated gap at 38 languages last week, now needs to cover 57 — the backlog leadership was asked to staff two weeks ago has grown by half again with no staffing decision yet.

Decisions needed

Leadership: the review-capacity staffing decision requested in each of the last two reports remains open while flagged content has grown from 2 to 38 to 57 languages; separately, consider requiring migrations that alter existing tables to be idempotent by default, after three straight weeks of deploy-time database incidents.

Next Week

• Staff or explicitly deprioritize doctrine-flag review capacity now spanning 57 languages, not 38
• Connect a first real external worker to the Translator Worker API
• Add a pre-deploy check for non-idempotent migrations, after three straight weeks of deploy-time incidents

Key dates

• August 4, 2026 — Target: begin theologian review pass on Turkish Matthew
• August 15, 2026 — Target: Translation Studio feature completion (per the site's own under-construction banner)