Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Quarter July 1, 2026 – September 30, 2026

Q3 2026

Executive summary

Q3-to-date opened with German and Turkish deepening from 1 to 8 New Testament books each, jumped sharply in July when a new multi-language pipeline took 38 languages to a complete New Testament (10 of them a complete Old Testament too), gained a second front in July's final week — an account menu, Projects, Teams, a Translation Studio hub, and a Platform Administrator dashboard — and then, in August's opening week, jumped again to 57 languages with a complete New Testament while Translation Studio grew a full guided workflow and a Translator Worker API foundation. August's second and third weeks pivoted from generation to consolidation: Library Review shipped end to end, then a Help section, database-backed newsletter/feedback with a real unsubscribe, and admin lead tooling followed, while content generation itself stayed flat for two straight weeks. September opened the same way, with a single active day that added Burmese to Library Review as a third queue and committed a long-flagged Help article, then went almost entirely quiet for two weeks. The quarter's final week reversed that pattern sharply: a Doctrine Knowledge Graph (a reviewed, AI-assisted claims workflow with a visual explorer) and a public Library Graph (an auto-derived doctrine-and-glossary map for all 67 published languages, later linked across books via a 1,311-entry canonical registry) both shipped, alongside the first two phases of a security architecture review that cut production npm audit advisories from 22 to 8 and put automated tests and a dependency gate in front of every future change.

What's new

  • Change

    57 languages reached a complete New Testament this quarter, 10 with a complete Old Testament too, up from German and Turkish alone at 8 books each. 19 of those 57 completed in August's first week alone.

    Impact

    The quarter's generation output now spans 57 languages of doctrine-checked content instead of two.

    Next action

    Prioritize theologian review recruitment at this new scale for the rest of Q3.

  • Change

    Shipped account/identity, Projects, Teams, Translation Studio, and Platform Administrator infrastructure in July's final week, then a guided project workflow and Translator Worker API foundation in August's first week.

    Impact

    Ministry partners now have a real place to organize workspaces, projects, and teams, with a path toward unattended project execution by an external worker.

    Next action

    Onboard the first partner workspace and connect a first external worker before Q3 closes.

  • Change

    German and Turkish each grew from 1 to 8 New Testament books in July, then both completed their full New Testament, with 57 languages total now joining them at complete New Testament coverage.

    Impact

    Ten flagship languages have complete Bible coverage, with 47 more at complete New Testament coverage.

    Next action

    Carry review recruitment lessons from these languages into the rest of the 57.

  • Change

    Shipped Library Review end to end in August's second week, then a Help section, database-backed newsletter/feedback with a real unsubscribe, and admin lead tooling in the third.

    Impact

    Contested terminology has a working review tool, and volunteers, partners, and admins now have written guides and visible lead/feedback data instead of a spreadsheet.

    Next action

    Name the first volunteer reviewers so the review tool has people using it.

  • Change

    Shipped a Doctrine Knowledge Graph and a public Library Graph in the quarter's final week, then linked doctrines across books via a 1,311-entry canonical registry.

    Impact

    Doctrine claims now go through a reviewed, AI-assisted workflow with a visual explorer, and every published language has a public, cross-book doctrine-and-glossary map.

    Next action

    Get theologian reviewers using the new claims queue; extend registry coverage to languages that diverge from the Spanish reference set.

  • Change

    Carried a security architecture review through Phases 1 and 2 in the quarter's final week: input validation, rate limiting, security headers, and a CI/dependency-audit gate.

    Impact

    Closes an open redirect, an email header-injection path, and an unauthenticated log-injection bug; production npm audit advisories fell from 22 to 8.

    Next action

    Confirm the mail and bot-check vendor decisions and schedule administrator MFA enforcement.

Business impact

Nearly 2,000 book-level pages are now live across 57 languages with complete New Testament coverage, a scale of doctrine-checked content depth that materially strengthens the platform's credibility with prospective ministry partners, who now also have real workspace, project, and admin infrastructure — soon including unattended, non-human execution — to organize their own work once onboarded. Partners and volunteers can now find written answers instead of needing a live explanation, and leads reach admin by email instead of sitting unseen. Two knowledge-graph systems added in the quarter's final week give partners a direct, explorable answer to whether doctrine stays consistent across books and languages, and the security remediation closes real vulnerabilities (an open redirect, an email header-injection path, an unauthenticated log-injection bug) while putting automated tests in front of every future change for the first time.

Metrics

  • Languages with a complete New Testament, quarter-to-date

    57(was 38) Up from last period

  • Languages with a promoted Library bundle

    67(was 63) Up from last period

  • Canonical doctrine concepts linking doctrines across books

    1,311(was n/a) Up from last period

    New this quarter.

  • Production npm audit advisories (high or above)

    8(was 22) Down from last period

  • Countries reached, quarter-to-date (Plausible)

    48(was n/a) Up from last period

    377 visitors over the 91 days to 5 September, 36 percent outside the United States, across five continents.

Risks

Theologian review capacity, a known gap for German and Turkish since early July, is now a gap across 57 languages of Critical/High-risk doctrine flags — the single largest risk to converting this quarter's generation output into content ministries can actually use, and it has now gone the entire quarter's second half without a named reviewer since the review tool shipped, with the 539-decision queue unchanged for the last month. The build/deploy pipeline needed four separate incident fixes in Q3's first half, plus a fifth in its final week (a migration-numbering collision between two features built in the same session, fixed the same day with no production impact). Content generation itself has now been flat since early August, with the quarter's final three weeks split between two entirely silent ones and a single three-day burst that shipped both knowledge-graph systems and the security work's first two phases at once, leaving little time to observe any of it live before quarter close. The security plan's vendor decisions (mail provider, bot-check provider) remain assumed, not confirmed, and its administrator login policy has no real effect until MFA is enforced at Google and Microsoft.

Decisions needed

Leadership: approve a review-capacity plan sized to 57 languages, not two, before Q3 closes, so this quarter's generation output does not sit idle into Q4. Decide the shape of the public Bible-study product direction that's been under discussion but not committed to a plan. Confirm the mail and bot-check vendor choices and schedule administrator MFA enforcement so the security work's remaining controls can be turned on.

Next Quarter

  • Recruit theologian reviewers at a scale matched to 57 languages, not two
  • Onboard a first real partner workspace onto the new workspace/Studio infrastructure before Q3 closes
  • Connect a first real external worker to the Translator Worker API
  • Decide the shape of the public Bible-study product direction

Key dates

No key dates recorded for this period.

In this quarter

Give feedback

How would you rate this page?

0 / 500 words