In His Name, the Most High
Changelog — 2.440–2.446
Releases 440.0 through 446.19. Current releases are on the main changelog, and every band is listed in the release archive.
Loading audio...
Version 2.446.19
November 12, 2026Written down, so it can be done again
- We have written the instructions for bringing everything back if the worst happened, and our own checks now refuse any new machine that is not in them. Backups are only half of recovery; the other half is knowing what to rebuild, in what order, and how to tell it worked. The instructions are a first draft that we will test by following them. Nothing to do at your end.
Version 2.446.18
November 12, 2026Every database, brought back from its backup
- We restored every one of our databases from the backup we would rely on after a disaster, and checked each one, table by table. Each backup was unlocked with its key, rebuilt on a spare copy that could reach nothing, and compared with a record taken at the moment the backup was made. All of them matched. One check first refused to pass because it had nothing to test against, which is what a check should do; we gave it a second way to prove itself, and it passed. Nothing to do at your end.
- Our backups no longer keep a record of which of our own machines looked up which address. Testing a restore showed that one backup was carrying that record along with the settings it was meant to keep. Nobody needs it to rebuild anything, and we keep no record like it anywhere else, so it is now left out, and the older copies that hold it are being cleared. Nothing to do at your end.
Version 2.446.17
November 12, 2026Two backups in one drawer
- One of our new backups was being filed in the same place as an older one, which could have hidden a problem with the older one. Our morning check looks at the newest copy in each place, so a new copy arriving every night would have made a stopped one look fine. We found it the same evening, while writing down what we have; nothing was missed in the meantime. Each backup now has a place of its own, and our checks refuse two that share one. Nothing to do at your end.
Version 2.446.16
November 12, 2026Backed up, and then restored
- The private settings our services run with are now in our nightly, encrypted backups, and we have restored every one of them. A backup is only a promise until it has been read back, so the same evening we unlocked each copy and compared it, file by file, with what is running. Every file matched. Nothing to do at your end.
- Our backup alarm is on. We sent it one test message to be sure it reaches the right people, and it did. From now on it speaks only when something is late. Nothing to do at your end.
Version 2.446.15
November 12, 2026The settings that hold everything together
- We are adding the private settings each of our services runs with to our nightly, encrypted backups. They are small files, but without them a rebuilt service would have to be introduced to every other one again by hand. We listed them carefully first, and a backup that finds one missing refuses rather than quietly keeping less. Nothing to do at your end.
- When a backup stops arriving, our team will now hear about it the same morning. Every day a small check looks at what actually reached our backup store, not at what each machine says about itself, and messages the core team only when something is late. Nothing to do at your end.
Version 2.446.14
November 12, 2026Why we test a restore
- We restored our new code backup the same day, and the test caught something the backup itself could not see. Empty folders were being left out, and a few of the things we keep need them to be there. The backup now keeps every folder, and the test that found it now runs every time. Nothing was lost, and there is nothing to do at your end.
Version 2.446.13
November 12, 2026Refused, as it should be
- The first backup of our code stopped itself rather than keep something it was not sure of. It met two things it had not been told about, refused, and told us why. We taught it about both, and it now checks for each of them every time. Nothing to do at your end.
Version 2.446.12
November 12, 2026The small files that matter most
- The keys that let our email be trusted, the key that signs people in to our hawza tools, and all of our code will now be backed up every night, encrypted. The keys are tiny files, but without them we would have to start trust over from nothing; the code is everything we have built. Each backup takes exactly the files it should and refuses if one is missing, rather than quietly keeping less. Nothing to do at your end.
Version 2.446.11
November 12, 2026A backup is only as good as its restore
- The backup we described last time is now running, and we have opened it and checked it. We unlocked a copy with its own key, without ever writing the contents to disk, and compared every file with the original: all of them matched. Nothing to do at your end.
- Our research tools gained a new way to work together, with a key made for that one job. The key was moved rather than copied, so exactly one exists, and we checked that a wrong key or no key is turned away. Nothing to do at your end.
Version 2.446.10
November 12, 2026The keys to the keys
- The service that vouches for every one of our machines now has its own nightly, encrypted backup. It holds the keys our machines use to trust each other, so losing it would mean introducing every machine again from scratch. Only a few people can open its backup, with a key of its own, and we checked that a backup missing anything important is refused rather than kept. Nothing to do at your end.
Version 2.446.9
November 12, 2026One key, one place
- The tools we use to hand one of our services a key of its own are now kept with the rest of our tools, tested, where anyone on the team can find them. We first wrote them for a single job. Each one moves a key without it ever being shown, makes sure only one copy is left behind, and refuses if anything is not exactly as expected. Nothing to do at your end.
- Our nightly check on database backups now asks every machine what databases it holds, rather than trusting our own list. It found one important database with no nightly backup of its own, and we have a tested way to add one that also proves the backup can be restored before we call it done. Nothing to do at your end.
Version 2.446.8
November 12, 2026Reading the whole list
- The tool that issues our internal certificates now reads everyone's turn on the machines, not just the first one listed. Before any change we take a turn, so two people never change the same machine at once. Now that several unrelated turns can be held together, this tool could wrongly refuse because it read only the top of the list. It now reads every turn, and we checked that it refuses when it should and accepts when it should. Nothing to do at your end.
Version 2.446.7
November 12, 2026Certificate issued, and watched
- The coming translation service now has its certificate, in development and in production, and our certificate monitor watches both. We checked each one afterwards: it names the right machine, it comes from our own authority, only the service can read its key, and it will renew itself well before it runs out. In development the service is now running with it, and the monitor checks that the certificate it serves is the current one. Nothing to do at your end.
Version 2.446.6
November 12, 2026A certificate, ready to issue
- The coming translation service is ready to be given its own certificate, so the tools that talk to it can be sure it is the real one. The certificate will renew itself, and only the service will be able to read its key. Before writing any of it, we read the renewal steps the machine will run, and we checked that our test can catch the mistake it is there to catch. Nothing to do at your end.
Version 2.446.5
November 11, 2026One key per door
- Every one of our tools now gets its own key when it needs access to another, never a copy of someone else's. We found two of our tools quietly sharing one key. Nothing was wrong yet, but it meant we could not shut one out without shutting out the other, and if the key ever leaked we could not tell which of them it came from. We have written it down as a standing rule, and the two will get keys of their own. Nothing to do at your end.
Version 2.446.4
November 11, 2026Both doors open
- The coming translation service can now reach our scripture search, in development and in production, and only through its own door. We opened each door, then checked from the translation service's side that it opens, and that everything it should not reach stays closed. Nothing to do at your end.
- Our newest machines now set their clocks from a wider set of public time servers. The default ones often did not answer us, so a machine could take minutes to set its clock after a restart. Clocks matter more than they seem: sign-ins and certificates are only accepted within a window of time. Nothing to do at your end.
Version 2.446.3
November 11, 2026Asking before we test our own locks
- Before we try to break in to our own services from outside, we asked the companies we rely on what they allow, and wrote the answers down. Testing your own defences is good practice, but it can look like an attack to the companies whose networks carry it, and they have rules about it. So we asked, got the answers in writing, and kept the exact terms we will test under, including what we must tell them if we find something. The test itself comes later. Nothing to do at your end.
- The machines that will run sign-in for all our tools now stay on the software versions we chose. Until now, a routine update could have moved them without anyone deciding to. Now a change waits for a planned upgrade. Nothing to do at your end.
Version 2.446.2
November 11, 2026One door per visitor
- The coming translation service gets its own way into our scripture search, rather than sharing one. Each tool that may ask our search for scripture comes through a door that admits only that tool, so that each can be opened, watched and closed on its own. The translation service now has a door of its own instead of sharing the one another tool uses today. Its home is also now fully set up and checked. Nothing to do at your end.
Version 2.446.1
November 11, 2026Making room for translation
- The home for our coming translation service is ready, and watched from day one. Our research tools already translate on request; that work is moving into one shared service, so every tool translates the same way and checks it the same way. Its home now exists, walled off so that it can only talk to the tools that use it, and it shows on our own status page before anything runs there. Nothing to do at your end.
Version 2.446.0
November 11, 2026Backing up what matters, not what we can remake
- Our nightly database backups can now leave out data we can rebuild. One of our research tools now keeps its record of work in a database, so that database needs the same nightly, checked backup as the rest. Most of its size is a search index we can rebuild from the books at any time, and copying it every night would buy nothing. The backup can now be told to leave such parts out, says each night what it left out, and still proves that everything else restores exactly. Nothing to do at your end.
Version 2.445.2
November 10, 2026Tidying up without tripping anyone
- The regular tidy-up of the machines that build our projects no longer gets in the way of a build. It already checked that nothing was building before it began, but a build that started a moment later could be slowed to a halt behind it, and one of our projects had a build fail that way today. Now those machines take no new work until the tidy-up has finished, and then they start again by themselves. Nothing to do at your end.
Version 2.445.1
November 10, 2026Proving an update worked, properly
- Each update to our services now proves it changed what it set out to change. Before an update goes out, a small check is run against the live service and must show the old behaviour; after the update, the same check must show the new one. A check that already passes beforehand proves nothing, and we found exactly that kind of check in one of our own proofs today. Nothing to do at your end.
Version 2.445.0
November 10, 2026Following our own advice
- This site now fixes the exact foundations it is built on, as we ask of our other projects. Until today, each build of this site took whatever its starting ingredients happened to be that day, so two builds of the same code could differ. Another of our projects pointed out that we had asked everyone else to fix theirs and had not fixed our own. Now every build starts from the same known version, and changing it is a decision we make on purpose. Nothing to do at your end.
Version 2.444.2
November 10, 2026The tidy-up that could not see the mess
- One of the machines that builds our projects ran out of space, and stopped building. Its regular tidy-up was working as written, but it was written to clear only one kind of leftover, and the leftovers piling up were a different kind. We cleared them by hand, and the tidy-up now clears that kind too, carefully, keeping anything still in use. Nothing to do at your end.
Version 2.444.1
November 10, 2026Writing down what we learned today
- Our internal guides now record two lessons from today's work. One: a tool should ask another tool what state it is in, not peek at its files, because the files can change shape. That is how a change here this morning briefly stopped one of our projects from updating. Two: the way our projects share their own code, which we had planned but not yet tried in practice, now works, and the guide shows exactly how. Nothing to do at your end.
Version 2.444.0
November 10, 2026Our checks test on what the live sites actually run
- Our services now share one version of a core building block, and our checks test on that same version. One of our own projects noticed that its checks ran on a slightly older version than the live site did, so a check could pass on code the live site would treat differently. We have settled on one current version, which also includes recent security fixes, and the checks now use it. Nothing to do at your end.
Version 2.443.1
November 10, 2026Our checks stop picking up outside changes on their own
- The building blocks our checks borrow from outside are now kept, not fetched every time. Until today, each check downloaded them again, so a change someone else made to one could alter our checks without our knowing. Now a kept copy is used, and we refresh it on purpose: at each regular upgrade, and at once if a fix is published. Nothing to do at your end.
Version 2.443.0
November 10, 2026More of our checks bring their own tools
- The copy of their tools our checks keep now covers two more languages. Earlier this week our checks stopped downloading one programming language each time they ran. Two others were still being fetched from outside on every run, so an outside service having a bad day could still fail them. They are now kept with the checks as well, each one fixed and checked before use. Nothing to do at your end.
Version 2.442.1
November 10, 2026This site's updates stop holding up anyone else's
- An update to this site now waits only for work on the same part of our systems. Earlier today, a change let updates say what they touch. This site's own update now does, so it no longer waits for, or holds up, an update to one of our research tools. Nothing to do at your end.
Version 2.442.0
November 10, 2026Changes that cannot touch each other no longer wait for each other
- Our updates now take turns only when they need to. Until today, any change to our systems made every other change wait, even when the two had nothing to do with each other. Now each change says what it will touch, and waits only for a change touching the same thing. An update to this site and an update to one of our research tools can go out side by side. The team will also see each change start and finish in our own chat, as it happens. Nothing to do at your end.
Version 2.441.0
November 10, 2026Our checks start using their own tools, one at a time
- The copy of their tools we built yesterday is now in place where our checks run. We expected that putting it there would be enough, and it was not: every one of our projects names exactly what its checks start from, so nothing changes until each project says so. That is a good habit, and it means each project now moves over with a one-line change of its own. The first already has, and its checks no longer wait on an outside download. We also found two of our own notes describing how this works the wrong way round, and corrected them. Nothing to do at your end.
Version 2.440.1
November 10, 2026A new shared piece, written down where everyone looks
- Our list of the code our tools share now includes the first part of our translation work. When one of our tools shares a piece of code with others, it is published in one place, checked, and every tool that uses it names the exact copy it expects. The first piece of the translation layer our research tools will share was published this morning, and we checked it ourselves before adding it to the list. No tool uses it yet. Nothing to do at your end.
Version 2.440.0
November 9, 2026Our checks stop depending on someone else's download
- The automatic checks that run on every change now bring their own tools with them. Each time we changed one of our tools, our checks fetched a programming language from an outside service before they could start. This morning that service had a bad few minutes, and a check failed for a reason that had nothing to do with our work. We have now built a fixed, checked copy of it for our checks to keep with them, and they will move onto it shortly, after which they no longer wait on anyone else. Each check will still start from a clean copy, so nothing one check does can carry over into the next. Nothing to do at your end.