translationCore 4.1.0-preview2

The project format is now final. This build freezes project format 1.0. Every project saved by this preview, or by the first one, opens in 4.1.0 and in every later version with every verse, alignment, check decision, comment, conflict and history entry as it was. You will not have to import your work again. The previous version is 4.1.0-preview. It also writes format 1.0, but preview builds are for testing only, and going back from one preview to an earlier one promises nothing. If this build gives you trouble, report it rather than go back.

Download

File	For	Signed
translationCore4-4.1.0-preview2-windows-x64.exe	Windows 10 and later, x64. Installs for you only, no administrator needed	Yes
translationCore4-4.1.0-preview2-macos-arm64-unsigned.pkg	macOS 13 and later, Apple silicon	No, not notarized
translationCore4-4.1.0-preview2-linux-x64.zip	Ubuntu 22.04 and later, x64. Unzip and run translationCore4 in the translationCore 4 folder	No

macOS can block the unsigned installer. Open System Settings, then Privacy & Security, and choose Open Anyway.

It installs as translationCore 4, beside any tC4 4.0 beta you already have. On Windows and macOS it installs over 4.1.0-preview. On Linux, delete the old translationCore 4 folder and unzip the new one. Your projects are in the translationCore4/projects folder in your home folder. Removing or updating the app leaves your projects and settings where they are.

What is new since 4.1.0-preview

• The project format is frozen. From this build on, nothing in a project's files that another build reads changes without a new format version, and every later version keeps opening what this one wrote. The checks that keep this promise run on every change to the app.
• Start a new Bible project from USFM files or from a Scripture Burrito (#844, #845). The first preview could not.
• The Mac app starts. The first preview's Mac app linked a library from the build machine that most Macs do not have, so it could fail to start (#883). This build links only system libraries, and the build installs and starts it on a fresh macOS machine of its own.
• Every interface sentence is translated in all nine languages (#848). Hindi brings its own Devanagari font (#613). The app starts in your computer's language until you choose one (#525).
• Sync tells the truth. A sync that could not record your work no longer reports it as sent to Door43 (#961). The project's format file, if deleted or damaged on Door43, is put back and reported (#941). The Share dialog loads your organizations faster (#897).
• Story frame conflicts. When two teammates change the same Open Bible Stories frame, the app says so and offers Review, as it does for a verse (#761).
• Align: Clear alignments starts a verse over, after a confirmation (#758).
• Translation helps. Notes and word cards keep their formatting (#910) and read in their own direction in a right-to-left set (#836). In Understand, a note on one verse of a passage lights only that verse's words when the source marks which verse each word belongs to (#409). A passage clicked while the helps load lights its words (#946). Notes are grouped under verse headings, and their article links carry names.
• Faster Check. The first Check screen on a big book, and each check list, open faster (#914, #899, #896). Printing a story is faster (#900).
• History keeps an outside restore. When another program held a save file, a backup tool putting back an older book file could be written over without a word. The app now compares the file in full and tells you (#847). The "rare loss after crashes" in the first preview's notes turned out to be a mistake in the test that reported it; the investigation found this separate defect and fixed it. What remains is listed under Known limitations.
• Smaller fixes. Dialogs keep their buttons inside and close only on a press that starts and ends on the backdrop (#855, #852). The section and story editors are as tall as their source (#915). About shows the third-party licenses offline (#606). The app shows its own icon (#871), and Linux gets the app's own title bar (#642).
• A newer shell. The app runs on Electronite 44.9.3 (#937).

The issues closed since the first preview are listed here.

What to test

Everything from the first preview: drafting, checking and alignment for Bible and Open Bible Stories projects; opening a project from Door43, sync, and exchange by file or USB drive; import of a translationCore 3 project, and Update a book; export; the interface in each of its languages.

New in this build: start a new Bible project from USFM files and from a Scripture Burrito. Clear alignments on a verse. Two teammates changing the same story frame. Hindi. The Mac app, from a clean install.

Open your projects from the first preview in this build and check that nothing changed.

To report a defect, use Report a problem in the app, or open an issue. Include the version from About, your operating system, the steps, what you expected and what happened.

Known limitations

• No Open Bible Stories project from Markdown files (#967, planned for 4.2.0).
• A Scripture Burrito starts a new project only. Adding its books to a project you already have is not in this preview (#952), and its abbreviation, copyright and license cannot be edited at import (#951).
• Zoom keys. On Windows, Ctrl and "+" does not zoom in on a Spanish keyboard or with the numeric keypad; Ctrl and 0 resets (#976). On Windows and Linux, after zooming out the window buttons stand taller than the header (#977).
• A large push on a poor connection can fail and have to start again (#842).
• Save work for a teammate checks the exchange file through the computer's cache, not from the stick itself, so a failing stick can pass the check (#867). Your project is untouched; keep the stick until your teammate has received the file.
• macOS: two files whose names differ only by letter case, such as Intro.mp3 and intro.mp3, can come out of a sync with two extra renamed copies, and the original name is missing until the app next looks at the folder (#964). Nothing is lost.
• A rare loss after a crash. When another program has cut the file that holds a save and the app is then killed within about two minutes, that save can be lost (#847, accepted for the previews). It needs both events together.
• A crash right after a save can lose the notice that the save sent an alignment link back to the word bank. The link stays in History (#866).
• The app does not check for updates. Get a new version from this page.
• Signing. macOS is unsigned and not notarized. Linux is an unsigned zip.

Build evidence

• Commit: 90f8221638a4eeade2bc74e4ef40e7d56c9d96b2 on main, tag v4.1.0-preview2. About shows the same commit. This is the commit the format freeze marks (tag format-v1.0).
• Build: release run 42723069834. Every job passed: the translations check, the three builds, an install-and-start smoke test of each installer on a fresh machine of its own system, and publish. On a preview tag the translations check skips its full-translation test; that every string is translated rest...

translationCore 4.1.0-preview

This is translationCore 4.1.0-preview, the first build of the new translationCore 4. It is for named testers only. Do not use it for production translation work. Test with copies of projects and keep your own backups.

The project format is not final yet. Projects you make in this preview will keep opening in 4.1.0 and later (ruling H9), so you will not have to import your work again.

Download

File	For	Signed
translationCore4-4.1.0-preview-windows-x64.exe	Windows 10 and later, x64. Installs for you only, no administrator needed	Yes
translationCore4-4.1.0-preview-macos-arm64-unsigned.pkg	macOS 13 and later, Apple silicon	No, not notarized
translationCore4-4.1.0-preview-linux-x64.zip	Ubuntu 22.04 and later, x64. Unzip and run tc4 in the translationCore 4 folder	No

macOS can block the unsigned installer. Open System Settings, then Privacy & Security, and choose Open Anyway.

It installs as translationCore 4, beside any tC4 4.0 beta you already have. Your projects are in the translationCore4/projects folder in your home folder. Removing or updating the app leaves your projects and settings where they are.

What is new since 4.0.0-rc.2

The screens, words and keys are the same as tC4 4.0. On top of that:

• Team work goes further. Several people can work on one project offline and exchange work later, by Door43 or by USB drive or file. You can keep saving while a sync runs. Nothing anyone wrote is lost.
• Door43 sync works with private repositories (after you sign in), with any default branch, and with Open Bible Stories projects.
• Conflicts. When two people change the same verse or story frame, both versions are kept and shown. For checks, alignments, comments and settings, the newest wins, and the older one stays in History where you can restore it. The Received sheet says what was replaced.
• Files such as audio travel with the project.
• Translation helps can come from Door43 or from Aquifer.
• Every project is a valid Scripture Burrito, on disk and whenever it leaves the app.
• Fixes. 45 open tC4 issues are fixed in this build. They carry the fixed-in-4.1 label and close when 4.1.0 ships.

What to test

Drafting, checking and alignment for Bible and Open Bible Stories projects. Opening a project from Door43, sync, and exchange by file or USB drive. Import of a translationCore 3 project, and Update a book. Export. The interface in each of its languages.

To report a defect, use Report a problem in the app, or open an issue. Include the version from About, your operating system, the steps, what you expected and what happened.

Known limitations

• tC4 4.0 projects do not open. Home lists them as "Cannot be opened". Bringing a 4.0 project into this app is not in this preview.
• No import from USFM files or a Scripture Burrito (#844, #845).
• Five sentences are in English in every language (#848). Four are the versification messages on the import review, and one is "… is already on this computer" in Get source texts.
• A large push on a poor connection can fail and have to start again (#842).
• Rare loss after crashes (#847). A storage stress test finds a case where a save can go missing from History. It needs another program to lock the book file, several crashes and a damaged save file together. We are investigating it.
• The app does not check for updates. Get a new version from this page.
• Signing. macOS is unsigned and not notarized. Linux is an unsigned zip.

Build evidence

• Commit: 9249a60ddaf0464c32f88145569d41539f81ee19 on main. About shows the same commit.
• Build: release run 40611554814. Every job passed: the translations check, the three builds, and an install-and-start smoke test of each installer on a fresh machine of its own system.
• Windows signing: Azure Trusted Signing. The installer and every shipped program file are signed.
• Each BUILD-MANIFEST-<platform>.json lists the sha256 and size of every file the app ships.

SHA-256 of each file:

f72bcc52119e9cedc15109ebc7e1ddf9dbb363d7bb5776b1d263d1dcfed9f174  translationCore4-4.1.0-preview-windows-x64.exe
d0cc4591d9dbb167c32086eda32ea5bbd731769f79f76f3f7532ecbd745baa86  translationCore4-4.1.0-preview-macos-arm64-unsigned.pkg
b301f63df840d6e465dfe44b3686777d48f056bbab0d1781b9a4aa180421c901  translationCore4-4.1.0-preview-linux-x64.zip

Before 4.1.0

We fix what testers find, translate the last strings, and freeze the project format. Later previews keep the -preview name. The final release is 4.1.0.

translationCore 4 — Public Beta

This public beta is version 4.0.0-rc.2. We invite broader testing before stable 4.0.0. Do not use it for production translation work. Test with copies of projects and keep independent backups. The beta uses tC4's normal project store. It does not provide a separate beta store or an automatic rollback.

Download

File	For	Signed
tC4-4.0.0-rc.2-windows-x64.exe	Windows x64 installer	Yes
tC4-4.0.0-rc.2-windows-x64.zip	Windows x64, unzip and run	Yes
tC4-4.0.0-rc.2-macos-arm64-unsigned.pkg	macOS Apple silicon installer	No, not notarized
tC4-4.0.0-rc.2-macos-arm64-unsigned.zip	macOS Apple silicon, unzip and run	No, not notarized
tC4-4.0.0-rc.2-linux-x64-unsigned.zip	Linux x64, unzip and run	No

macOS can ask you to approve the unsigned app in System Settings, under Privacy & Security ("Open Anyway"). On Linux, unzip once and run start-tc4.sh.

What to test

The planned 4.0.0 workflows: Bible and Open Bible Stories drafting, checking and alignment where supported; export and import; Door43 first share and team sync round 1; and the English, Spanish, French and Arabic interfaces. The workflows and their proof are in JOURNEYS.md.

Use Report a problem in the app to report a defect. Include the app version, operating system, steps, expected result and actual result.

Known limitations

• Character styles in the aligned USFM export (#420). An aligned word loses the style that wraps it: \add Jesucristo\add* exports as an empty \add \add* beside the aligned word. No text is lost.
• Projects imported before the fix (#821). A Scripture Burrito with no vrs.json that was imported before this build cannot save a checkpoint. The save indicator shows "Checkpoint not saved", and export and share run the same checkpoint. New imports are not affected (#813).
• Imported alignment (#553). An aligned USFM file that you import or add as a book keeps its alignment markup as it is. Align shows a notice for these verses and does not edit them. The aligned USFM export keeps them as they are.
• Keyboard (#568). A keyboard user cannot place a word on a card, merge two cards or confirm one suggestion.
• A link without a review flag (#825). After a Translate save, a rare tie in the move rule can drop one alignment link without a review flag. The word returns to the bank. No wrong link is kept.
• Signing. macOS is unsigned and not notarized. Linux is an unsigned zip.

Build evidence

• Release commit: a5ce0307df90b558f5dc584d6591b3dc57f62fce on release/4.0. Its tree is the tree of main at b1d1f37.
• Build: package-desktop run 39481303903. All 10 jobs passed, including the post-install smoke tests for Windows x64, Linux x64 and macOS arm64.
• Windows signing: Azure Artifact Signing (D99). The smoke job requires a valid, timestamped signature on the installer and on every .exe, .dll and .node file.
• The evidence and the release checklist are in pull request #828.

SHA-256 of each file:

219eea24efc32362d2f5efc94bf3bf237b0f5af52f61e851db9b03f4a80637e3  tC4-4.0.0-rc.2-windows-x64.exe
0dc5c45aec65980b01d0306b85fa6ed7d9c3182edbb70a20caf1d0418ac54e14  tC4-4.0.0-rc.2-windows-x64.zip
65972ef66f3b63ed74c2b982ea3c5b333e0b71ee262d2cdf1bab99456fb1bef7  tC4-4.0.0-rc.2-macos-arm64-unsigned.pkg
19ee52fd30390defb0268e131d1307b9c18f95d7caac82500ec1a12b613c8601  tC4-4.0.0-rc.2-macos-arm64-unsigned.zip
06fc7e309f58e3ea86e9887ae0a14e6e51ba128193069d08086c6697a7fa9666  tC4-4.0.0-rc.2-linux-x64-unsigned.zip

Before stable 4.0.0

We review beta feedback, resolve release blockers and prove the release gates on the final build. Further beta fixes keep increasing rc.N versions. Stable uses version 4.0.0. Its date depends on those results.

v4.0.0-rc.1 — Increments 8 and 8.5: publish, import, and first share

Increments 8 and 8.5 close together in one tag (decision D79). A facilitator can now get work out of tC4 and bring existing work in. Export makes aligned USFM, plain USFM, a Scripture Burrito zip and a print-ready PDF of a book, and Markdown and a PDF of an Open Bible Stories project. Import makes a new project from a translationCore 3 zip, USFM files or a Scripture Burrito. Share puts a project on Door43 for the first time. Six journeys ship: J7, J23, J9a, J9c, J9d and J11. The format locks the re-key rules for renumbered verses before the release contract.

• Export a book (#375, J7): one export menu on the project. Aligned USFM and plain USFM (#19); the stored file is never overwritten. A Scripture Burrito zip of the project (#359). A print-ready PDF by the print-styled route, with page setup: spacing and paper size (#20, #381, #142). The app shows "Saved " only after the download completes (#382). On Windows, exports that read the project zip work (#425).
• Export an Open Bible Stories project (#360, J23): story Markdown and a dated PDF, on the same PDF path as J7 (D74). A second layout puts a quarter-page picture beside the text (#11). Runs of undrafted frames show as one line with no pictures (#454). The PDF prints on the Linux packaged app (#451).
• Import existing work (#361): + Add a project on Home (#431) opens one dialog. Choose a file, review what was found, and create a new project. Three sources: a translationCore 3 project zip (#21, J9a), raw USFM files (#195, J9c), and a Scripture Burrito (#196, J9d). A damaged or partial import is refused with a clear message and writes nothing (#41). Import never chooses a license: if the files carry none, the review says so and applies none (#392). The review warns when the Bible name matches a project already on this computer (#436), and the Details check is not green when the language code is missing (#437).
• Share to Door43 (#362, J11, Increment 8.5): Share on Door43 on the project card. Sign in with your Door43 username and password (#203). "Stay signed in on this computer" keeps the token in the operating-system keychain (#366). The app creates the repository in your account or in an organization, pushes the main branch, and shows the URL. The card then shows "On Door43". No name, email or login is stored (D85).
• Internet and consent (#486, #514; D88): a Door43 account menu shows at the top right, on Home and in a project. It has sign-in, sign-out and the switch "Ask before using the internet", which is on by default. While the switch is on, each internet task opens one "Use the internet?" dialog first. Cancel sends nothing. The app's fonts ship with the app, so nothing loads from a font CDN (#3).
• The format (#370): BURRITO-SPEC holds the re-key rules for renumbered verses, and the conformance harness proves them (#209, #219). An upgrade of the original-language text or a gateway Bible marks the affected alignments invalid (#258). Every store operation returns one Report shape with one refusal-code table (#156), and keeps an ops record that recovery reads on open (#374).
• Resources (#504, #528): the installer bundles the English suite at v91. An app upgrade installs each bundled release in its own folder beside the old one. Each project chooses its gateway-language package in its settings (#412).
• Fixes from end-user QA of build 9215071 (#439): Check shows the open project's own resources after a switch between a Bible and a stories project (#434). If the project view fails, the app shows a message and Back to Home, not a blank window (#435; the cause of the blank window after a translationCore 3 import is not found). Scripture updates offer only the original-language text that covers the project's books (#438). A carried-over check can be decided again after a change of checking language (#448). A new project opens in Understand (#507). Project settings left the top bar (#505).
• Also in this build: Community Checking opens faster on a drafted OBS project (#460). An OBS card on Home no longer stays empty when many projects load at the same time (#475). The Check picker follows a change of checking language (#481). Resume into Translation Notes does not stall (#513). Align does not hang when you click the verse that is already selected (#296).

Evidence

All on main at 6f878aa, 2026-10-02.

npm run prove on CI: ci run 37079690007: vitest 1258 passed, 42 skipped; conformance:validate 50; conformance:journal 356; conformance:normative 97. rig run 37079690011: transport 10, round-trip 12, vitest:rig 46.

Journeys: the full suite (npm run journeys) on a local rig, fresh seed: 153 passed, 8 skipped, 0 failed (15.0 min). The skips are J1 FR-3/4/5 (fixme), J10 ×3 (retired), J11 case 3 (the live qa.door43.org leg, no QA credentials) and J14 (pending). The journeys do not run in CI.

Tag rule (epic #59):

Check	Result
Built by CI for every covered platform	package-desktop run 37079689983 on main 6f878aa: macOS arm64 (pkg 11258805109, zip 11258785186), Linux x64 (zip 11257559838), Windows x64 (installer 11258084378, zip 11257824909)
Post-install smoke test on a clean machine	SMOKE OK on the Linux CI runner (job 111078761094, artifact 11258193980), the macOS CI runner (production pkg job 111079322427, artifact 11258640610; zip fallback job 111079322418, artifact 11258109689; debug job 111079322448, artifact 11257974754) and the Windows CI runner (job 111079585735, artifact 11259330374, install and reinstall). Each job runs an upgrade install and a fresh install. Every host: ok export: … 3 ingredient files; metadata matches raw route (Scripture Burrito export, #383)
One offline run	Debian 13 x86_64, the Linux artifact (11257559838, sha256 e957b91a…bcdcf, matches the CI digest), network off by unshare -rn with loopback only; ping 1.1.1.1 from the namespace: "Network is unreachable". PASS: steps 1 to 10 passed, with 9, 9a and 9b. Step 9: "Saved Offline371-Titus.pdf" and "Saved Offline371-2026-10-02.zip" (Scripture Burrito); the PDF holds the drafted verse and embeds PT Serif. Step 9a: the account menu shows on Home with no Internet or Local; Share on Door43 opens Use the internet?; Cancel sends nothing (D88). Step 9b: the OBS story 1 gateway text and the frame-1 picture showed from the bundled resources with the network off; one frame drafted; one Translation Notes item decided (1 of 91 resolved). Local smoke-installed.zsh before the run: SMOKE OK (upgrade and fresh pass). Run by Tessa, 2026-10-02 ET. docs/evidence/offline-run-2026-10-02.md

Pilots: read before you start

Pilot window Oct 10 to Oct 15 (#58). Focus on five things and report what you find as an issue:

1. The full loop, end to end: create or import a project, draft, check, export, share.
2. Export a PDF and a Scripture Burrito of a book. Does the PDF print? Does the zip open in another tool?
3. Import a USFM file as a new project. Does the review show the right book and language?
4. Share your project once and open the URL it shows. Is the project on Door43, with your books?
5. Install on all three systems: the macOS .pkg, the Windows .exe, the Linux zip.

Share writes to the real Door43. This build shares to git.door43.org, not to a test server. Share creates a real repository in the account or organization you choose. Use a test project, and use your own account.

The download carries the English suite and the OBS set. You can create a project, draft, check and export with the network off. Share needs the internet. It asks "Use the internet?" first, unless you turn off "Ask before using the internet" in the account menu.

Windows pilots, read this first (#284). On a Windows machine that has never had a Visual C++ runtime, the app does not start. It reports "The backend could not be started" because VCRUNTIME140.dll is missing. Install the Microsoft Visual C++ Redistributable (x64) from https://aka.ms/vs/17/release/vc_redist.x64.exe first, then start tC4. This applies to the installer and the zip. Many machines already have the runtime from other software.

macOS: download the .pkg. The installer is unsigned. If macOS blocks it, use System Settings › Privacy & Security › Open Anyway. It asks for an administrator password. Without administrator access, use the zip and follow its README. Windows: download the .exe. SmartScreen warns on an unsigned app; choose More info › Run anyway. The portable zip is the fallback. Linux: unpack the zip and run start-tc4.sh.

Pre-release. Not for production use.

v4.0.0-alpha.7 — Increment 7: Open Bible Stories

Increment 7 closes on Open Bible Stories. A facilitator creates an Open Bible Stories project; a translator drafts a story frame by frame beside the gateway-language story and its pictures, reads a story with its notes and word links, and checks a drafted story against the OBS notes and words. Four journeys ship: J20, J21, J25 and J22 (decision D74). Open Bible Stories is a second kind of Scripture Burrito (gloss/textStories: fifty stories of frames in Markdown), with its own format section, store path, journal vocabulary and screens. No journey moved to Increment 8.

• Create an Open Bible Stories project (#287, J20): on Home, + New Open Bible Stories: name, language, direction, Create stories →. The project card shows one tile per story, collapsed to the three most recently edited (#328); a tile returns to where you last worked in that story (#329).
• Translate a story frame by frame (#289, J21): the story opens in Translate with the gateway story and the picture of each frame on the left, in the same chrome as Bible Translate, so the process trains for Bible work (#307, #330). Draft frame N, type, click outside the card: the frame marker turns drafted. Each frame is one paragraph; the pictures come from the bundled picture pack, with the network off (#288).
• Understand a story (#290, J25): Understand shows the gateway story with the frame picture floating at the start of the text (#327), source only (#332), and the OBS notes, word links and questions of the selected frame in the Bible helps panel's tab strip (#331). A user comment on a frame is recorded and survives quit and resume.
• Check a story (#291, J22): Check › Translation Notes or Translation Words for the story, by story:frame; ✓ Mark valid decides an item and the progress line counts it. Community Checking previews the drafted story. A check reference is one model in two forms, story and verse, that cannot be confused (#310).
• The format (#147, #286): BURRITO-SPEC 1.15 section 10 defines the OBS project kind; the conformance harness proves the OBS sample burrito (conformance/sample-burrito-obs/). Story files, frame writes and journal vocabulary version 2 are in the store.
• Packaged OBS resources (#288, #306, #326, #344, #347, #348): the installer bundles en_obs, en_obs-tn, en_obs-twl, en_obs-tq and the picture pack uW/obs_images_360. The packaged app binds its resources to the installed package at every start, on all three platforms; a story keeps LF bytes through setup and on Windows; the build fails when /api/version disagrees with product.json.
• Also in this build: file names that escape an archive root are rejected in downloaded resources (#2, #309); a gateway frame-count mismatch is stated as a mismatch (#313); the picture pack is read once per open project (#312); a failed save retries once at a time and the desktop close gate waits for it, so failed alignment retries no longer make the app unresponsive (#356).

Evidence

Clean-clone CI (docs/evidence/manifest.json, run on main): vitest all passed (counts in the prove-manifest artifact of ci run 35671067435, D77/D78); format conformance 48/48; journal suite 350/350; normative rules 91/91. J20, J21, J22 and J25 run green on a local rig (PRs #320, #322, #323, #345); they do not run in CI.

Tag rule (epic #59) (docs/evidence/offline-run-2026-09-22.md):

Check	Result
Built by CI for every covered platform	run 35671067386 on main 95238c3: macOS arm64 (pkg 10671910574, zip 10671291064), Linux x64 (zip 10671230886), Windows x64 (installer 10671671208, zip 10671376348)
Post-install smoke test on a clean machine	SMOKE OK on the Linux CI runner (artifact 10670966445), the macOS CI runner (production pkg 10672060046, zip fallback 10672025081), and the Windows CI runner (10671740842, install and reinstall). Every host: ok OBS image: story 1/frame 1 decoded 640x360 from local bundled resource with net disabled; no CDN request
One offline run	Debian 13 x86_64, the Linux artifact (10671230886), network off by unshare -rn with loopback only: PASS; steps 1 to 8, 9b and 10 passed, step 9 skipped for #19. Step 9b: the story 1 gateway text and the frame-1 picture showed from the bundled en_obs and picture pack with the network off; one frame drafted; Understand listed the frame notes and word links; one Translation Notes item decided (1 of 91 resolved). Run by Tessa, 2026-09-21 PT. docs/evidence/offline-run-2026-09-22.md

Pilots: read before you start

Pilot window Sep 29 to Oct 3 (#58). Focus on four things and report what you find on the issue each names:

1. Create an OBS project (#287): + New Open Bible Stories on Home. Does the project appear with its story tiles?
2. Draft two stories (#289): draft every frame of stories 1 and 2 with the network off. Did every picture and every gateway frame show? Did a draft ever go missing after quit and resume?
3. Read a story with notes (#290): in Understand, select a frame. Are the notes and word links the ones for that frame? Write a comment; quit; resume. Is it still there?
4. Check one story (#291): in Check, decide the notes of story 1. Does the progress line count each decision after resume?

The download carries the English suite and the OBS set: create a project and draft with the network off. Export is not built (#19). The Windows machine needs the Visual C++ runtime (#284, below).

Windows pilots, read this first (#284). On a Windows machine that has never had a Visual C++ runtime, the app does not start: it reports "The backend could not be started" because VCRUNTIME140.dll is missing. Install the Microsoft Visual C++ Redistributable (x64) from https://aka.ms/vs/17/release/vc_redist.x64.exe first, then start tC4. This applies to the installer and the zip alike. Many machines already carry the runtime from other software.

macOS: download the .pkg. The installer is unsigned; if blocked, use System Settings › Privacy & Security › Open Anyway. It asks for an administrator password. Without administrator access, use the zip and follow its README. Windows: download the .exe. SmartScreen warns on an unsigned app; choose More info › Run anyway. The portable zip is the fallback. Linux: unpack the zip and run start-tc4.sh.

Pre-release. Not for production use.

v4.0.0-alpha.6 — Increment 6: suggestions and resources

Increment 6 closes on suggestions and resources: a translator aligning a verse gets suggested links learned from the project's own alignments and accepts or rejects each one; a translator checking a book leaves a check comment and a bookmark on a check item; a facilitator upgrades the project's help resources to a newer release without losing a decision. Three journeys ship: J12, J5 in its revised end state, and J4 in its revised end state (decision D72).

• Alignment suggestions, propose-only, off by default (#1, #255, #134, #213): turn on Suggest links in the Align tool and the engine proposes links for the words still in the bank, learned from the alignments already confirmed in this project (one model per testament). A suggestion is a dashed chip on its card; confirm one, Accept all, Reject all, or Reset. Nothing is written until confirmed; a confirmed link is the same edit a manual placement makes. One tokenizer splits a verse for the editor and the engine. After a verse edit, the links the edit did not touch stay; only the changed words come loose.
• Alignment done (#271, D73): a verse's alignment is done when every word is placed, or when the translator marks it valid in the Align tool.
• Check comments and bookmarks (#50): bookmark a check and write a check comment on it, in the translationNotes and translationWords tools. Neither is a decision: the progress meter does not move.
• Resource upgrade (#256, #257): in the sources modal, Check for updates (online only) asks Door43 for the newest release of every pinned repo and shows one offer per language set. Upgrade installs every offered release (sha-verified, all or nothing), shows the decision carry-over per book and tool, and moves the pins only when you confirm. Cancel leaves the project untouched; the other set's pins and every text ingredient stay byte-identical.
• Guided fix for a missing resource (#9): when a tool's pinned resource is missing on this computer, the tool card offers Fix this… and a guided screen gives three ways out: download the pinned version, re-pin to an installed version, or sideload from a file. Writes to checking/settings.json use compare-and-swap; a stale write is refused.
• A save never freezes the UI (#94): the fold runs in a Web Worker.
• Resume returns to the mode last used (#268): Understand, Translate, or Check, with the Check tool that was open.
• Installers (#243, #253): macOS ships a .pkg that installs a branded self-contained app; Windows ships an .exe installer with Start menu and desktop shortcuts and an uninstaller. The portable zips remain for both.
• Also in this build: the Draft Section/Verse switch is one control like Understand's and is disabled while an editor is open (#238, #250); the helps panel filters to the verses in focus (#239); the Academy tab and the Understand Comments tab leave the helps panel (#240, #252); the source pane shows bridged verses in both directions (#246); a held verse marker in Place mode no longer selects the text it passes (#241).

Evidence

Clean-clone CI (docs/evidence/manifest.json, run on main): vitest 1056 passed / 38 skipped; format conformance 41/41; journal suite 344/344; normative rules 72/72. Rig suites green in the rig CI job.

Tag rule (epic #59) (docs/evidence/offline-run-2026-09-14.md), met with one qualification on Windows, recorded below the table:

Check	Result
Built by CI for every covered platform	run 34858629549 on main 7227cb8: macOS arm64 (zip 10354905272, pkg 10354720508), Linux x64 (zip 10354730245), Windows x64 (zip 10354970673, installer 10354591238)
Post-install smoke test on a clean machine	SMOKE OK on the macOS CI runner (artifact 10354495935), the Linux CI runner (artifact 10354775261), and the Windows CI runner (artifact 10354567020, install and reinstall)
One offline run	Debian 13 x86_64, the Linux artifact, network off by unshare -rn with loopback only: PASS; steps 1 to 8 and 10 passed with source text, helps, checking and aligning from the shipped suite; step 9 skipped for #19. docs/evidence/offline-run-2026-09-14.md

Two runs on real machines sit beside the CI results. On macOS 26.5.1 arm64 the shipped smoke ends in SMOKE OK. On a clean Windows 11 Home machine with no prior Visual C++ runtime the smoke does not pass until the redistributable is installed; see the Windows note below and #284. The CI Windows runner carries that runtime already, so its green result says nothing about a machine without it.

Pilots: read before you start

Pilot window Oct 5 to 9 (#58). Focus on three things and report what you find on the issue each names:

1. Alignment suggestions: turn on Suggest links in Align. Are the proposals useful? Did an accepted or rejected suggestion ever change a link you did not touch? (#1)
2. Check comments and bookmarks: bookmark a check item and write a comment on it, quit, resume. Are both still there? (#50)
3. Resource upgrade: in the sources modal, Check for updates, then Upgrade a set. Did any decision go missing? (#256)

The download carries the English suite: create a project and draft with the network off. Export is not built (#19). The window keeps the system frame (#214).

Windows pilots, read this first (#284). On a Windows machine that has never had a Visual C++ runtime, the app does not start: it reports "The backend could not be started" because VCRUNTIME140.dll is missing. Install the Microsoft Visual C++ Redistributable (x64) from https://aka.ms/vs/17/release/vc_redist.x64.exe first, then start tC4. This applies to the installer and the zip alike. Many machines already carry the runtime from other software. Found on a clean Windows 11 Home machine, 2026-09-15; the fix is #284.

macOS: download the .pkg. The installer is unsigned; if blocked, use System Settings › Privacy & Security › Open Anyway. It asks for an administrator password. Without administrator access, use the zip and follow its README. Windows: download the .exe. SmartScreen warns on an unsigned app; choose More info › Run anyway. The portable zip is the fallback. Linux: unpack the zip and run start-tc4.sh.

Pre-release. Not for production use.

v4.0.0-alpha.5 — Increment 5: drafting for real

Increment 5 closes on drafting for real: a translator drafts a whole section at a time, places the verse numbers, joins verses into spans, formats paragraphs and poetry, and reads a passage with helps. Two journeys ship: J2 in its revised end state (D70) and J16.

• Section drafting (#141, #53): Translate drafts a section as one text on the design's Type / Place verse numbers flow.
• Verse spans (#63): create and break a span such as 9-10 while drafting. One structural change per save; records keyed to the member verses are invalidated and kept (#219 holds the open question on their disposition).
• Formatting (#54): paragraph and poetry marks in the drafting editor.
• Original-language source pane (#207): the Greek or Hebrew text shows beside ULT and UST in Translate.
• Understand with helps and user comments (#197, #111, #117): read a passage with translation notes and questions, write a user comment, and see the translator's own comments as a tab in Translate's helps panel (journey J16). The round trip is proven for projects framed in a versification other than eng.
• Aligning and checking never wait on a save (#100, #93): both surfaces save through their own queues, like drafting; the next action returns at once, and a refused write surfaces on the affected item after the fact.
• The English suite ships in the artifact (#163, #218): ULT, UST, UGNT, UHB, translation notes, words, academy, questions, and the two lexicons are in the download. A pilot drafts offline from the first start; "Get resources" is no longer a first step.
• Windows x64 build (#181, #228): CI builds an unsigned Windows artifact beside macOS and Linux. A Windows-only absence bug found by the clean-machine witness is fixed.
• Also in this build: fonts ship locally, so offline use keeps Mulish, Charis SIL, Noto Serif and Amiri (#3); the docs gate checks every journey row against its proof file (#199); the desktop build runs on a pull request only when the recipe changes (#227).

Evidence

Clean-clone CI (docs/evidence/manifest.json, run on main): vitest 969 passed / 37 skipped; format conformance 40/40; journal suite 344/344; normative rules 72/72. Rig suites green in the rig CI job.

Tag rule (epic #59), all met (docs/evidence/offline-run-2026-09-09.md):

Check	Result
Built by CI for every covered platform	run 34293254911 on main 1c8b376: macOS arm64 (artifact 10082301082), Linux x64 (artifact 10082201368), Windows x64 (artifact 10082254332)
Post-install smoke test on a clean machine	SMOKE OK on the macOS CI runner (artifact 10082326436) and the Linux CI runner (artifact 10082234806). Windows: the clean-machine witness on the owner's Windows 10 Pro laptop, docs/evidence/desktop-windows-witness-2026-09-08.md (alpha.4 artifact with the #228 fix; CI has no Windows smoke job yet)
One offline run	Debian 13 x86_64, the Linux artifact, network off by unshare -rn: PASS; steps 1 to 8 and 10 passed with source text, helps, checking and aligning from the shipped suite; step 9 skipped for #19. docs/evidence/offline-run-2026-09-09.md

Pilots: read before you start

The download carries the English suite: create a project and draft with the network off. Fonts load locally (#3). Export is not built (#19). On macOS a quit may leave the bundled server running (#206): seen once on the alpha.4 CI runner, not in this build's run. The window keeps the system frame (#214).

macOS: the app is unsigned. On first launch use System Settings › Privacy & Security › Open Anyway. Windows: SmartScreen warns on an unsigned app; choose More info › Run anyway.

Housekeeping

The two lexicons are pinned by commit to the uW org's burritos (D71) until the December 2026 Greek New Testament release brings its own lexicon.

Pre-release. Not for production use.

v4.0.0-alpha.4 — Increment 4: open and resume

Increment 4 closes on open and resume. The share leg moves to Increment 7 (#120, #156, #185, #203).

• Checkpoints commit (#183): a git commit happens when the translator switches mode or leaves the project, never on a save. A failed commit shows "Checkpoint not saved" with Retry and never blocks navigation.
• Resume across a restart (#184): close the app, start it again, and Home's Resume card returns the translator to the remembered book and chapter with the text (journey J8).
• Open, resume, share journey (#185): one spec runs open and resume end to end; the share leg is marked pending on #120.
• Also in this build: the Understand, Translate, Check workflow on the new design system (epic #104, D63); one project-open journal scan with a progress bar (#95); npm run prove and the evidence manifest (#154, #155); the post-install smoke test shipped in the artifact (#45); the offline-run procedure (#43).

Evidence

Clean-clone CI (docs/evidence/manifest.json, run on main): vitest 871 passed / 37 skipped; format conformance 40/40; journal suite 344/344; normative rules 72/72. Rig suites green in the rig CI job.

Tag rule (epic #59), all met (docs/evidence/offline-run-2026-09-06.md):

Check	Result
Built by CI for every covered platform	run 34058863316 on main 736fdd0: macOS arm64 (artifact 9996877373), Linux x64 (artifact 9996833809)
Post-install smoke test on a clean machine	SMOKE OK on the macOS CI runner, the Linux CI runner, and a clean Debian 13 machine
One offline run	Debian 13, network off: PASS; steps that could not run name #163, #3, #19

Pilots: read before you start

The artifact ships no English scripture yet (#163). Go online once, open your project, run Get resources, then draft. Without that step the source panes read "This source text is not on this computer" and the checking tools are unavailable offline. Fonts fall back to system fonts offline (#3). Export is not built (#19). Windows has no build yet (#181).

macOS: the app is unsigned. On first launch use System Settings › Privacy & Security › Open Anyway.

Housekeeping

Increment 3 closed on 2026-08-26 with a version bump to 4.0.0-alpha.3 and no release. This is the next pre-release after alpha.2.

Pre-release. Not for production use.

v4.0.0-alpha.2 — Increment 2: check and align

Increment 2 is closed after an independent adversarial review (a second model, independent of the implementer; all review blockers fixed).

• Check: a checker works a whole book — translationNotes and translationWords checks against resources pinned at exact versions (journey J4).
• Align: an aligner links each word of a verse to the original language; an edit to the verse invalidates its alignment honestly (journey J5).
• Evidence: clean-clone tests 283 passed / 32 skipped; format conformance 34/34; journal suite 59/59.

Pre-release. Not for production use.

v4.0.0-alpha.1 — First public build

The first public snapshot of the translationCore 4 client — a ground-up rewrite. translationCore 3.x is a separate codebase; projects will migrate, versions do not.

• Draft: create a project, choose source texts, and draft beside them (Increment 1; journeys J1–J2, proven by end-to-end tests).
• Check + Align: the feature work for checking a book and aligning verses, at this date entering independent review.
• Format: every project is a Scripture Burrito git repository. The format specification ships in docs/BURRITO-SPEC.md.

Pre-release. Not for production use.