Development milestones · 8 and 16 October 2026
A dated snapshot of the code behind this site and its four free tools. It is linked from the site footer; it is not in the menu or in search.
Behind the pages you can see sits the code that measures audio, signs members in, builds the books and refuses to publish a page that breaks the rules.
Brad Huett designs and specifies the work, and a change ships only when he signs it. The AI team writes the code. Six weeks of signed work, from the first saved change on 4 September 2026 to 16 October. Counted twice along the way, on 8 and 16 October; each count keeps its own section, so the earlier figures stay as measured.
The six weeks as sprints · two plus two plus two
Read back from the record of changes, as if each two-week stretch had ended in a sprint review. The sprint lines are the history regrouped, not plans written at the time.
Sprint 1 · 4–17 September
Goal: a finished-mix check anyone can run in the browser.
The demo: AudioVibes measuring a master in the browser, embedded on the old site; the security statements written and numbered; the first rulings.
At the end: 8,853 lines of code. Most of this sprint was saved as one batch on 20 September.
Sprint 2 · 18 September–1 October
Goal: our own site, members signed in, the first book on sale.
The demo: release 3.0; this site, about 20 pages; ABA sign-in with each member’s history; Produce the Record as PDF and EPUB; the public ledger; the Repair Book on sale.
At the end: 24,182 lines of code; 49 signed changes in the sprint.
Sprint 3 · 2–16 October
Goal: the full toolbox, the production clock, the book line, and outside proof.
The demo: ABA Compare, ABA Phaze Check and ABA Pocket Check; the one-command ship; ABA TruSync’s clock and rooms through Milestones 0 to 8, rehearsed end to end; the EBU test set, 29 of 29; the Repair Book’s fourth edition and two new books.
At the end: 47,807 lines of code; 210 signed changes in the sprint.
The second count · 16 October 2026
47,807
In 227 files, not counting the web pages themselves. Up from 34,786 eight days earlier.
270
Each one a saved, described change (a commit), since the first on 4 September 2026. 107 of them since the first count.
6,993
In 44 test files: code whose only job is to check the other code.
29 of 29
ABA AudioVibes, build 2026-10-15.1, computed to and passes the EBU Tech 3341/3342 minimum-requirements test set (v05), 29 of 29.
What it is written in · 16 October
| Kind | Files | Lines | What it does here |
|---|---|---|---|
| Python | 139 | 30,543 | Runs on the studio computer. The ABA TruSync clock that drives the production record (kept in Excel), the site build and its checks, the one-command ship, the book builders, and the AudioVibes reference code. |
| JavaScript | 77 | 16,667 | Runs in the visitor’s browser and on Cloudflare’s servers. The engines and screens of the four tools, the sign-in service, and the browser tests. |
| VBA | 3 | 379 | The macros inside Excel, in the ABA TruSync production record that tracks production cost against each milestone. |
| SQL | 5 | 101 | The member list’s database tables, including a record of actions that is only ever added to. |
| Settings | 3 | 117 | Deploy settings: which server runs the site, under which address. |
| All code | 227 | 47,807 |
Where it lives · 16 October
| Area | Files | Lines | What it is | Share |
|---|---|---|---|---|
| AudioVibes | 57 | 15,062 | The finished-mix check: loudness and delivery measurement, scoring, the Repair Book and book builders | |
| The shared scripts | 27 | 8,536 | The one-command ship, the build checks, the page builders | |
| ABA TruSync | 27 | 4,665 | The production clock and its rooms, and the production record of cost and milestones | |
| This site | 27 | 4,405 | The site build, the publishing gate, search tags, and the sign-in service | |
| Tests | 26 | 3,802 | Checks against known answers, run before a change is trusted | |
| ABA Pocket Check | 10 | 3,789 | Where parts share frequency and time | |
| ABA Compare | 8 | 2,501 | Mix versions at matched loudness | |
| Studio tools | 14 | 1,828 | Helpers for the studio’s own production work | |
| ABA Phaze Check | 15 | 1,362 | Phase and timing alignment between mics | |
| Everything else | 16 | 1,857 | Housekeeping, outreach, graphics and small helpers |
As on 8 October, each tool keeps tests in its own folder, so the tests row is only the shared set; the 6,993 figure includes them. Not counted here: 244 web page files (much of ABA TruSync’s room code is written inside them), 266 written documents (the rulings, the specifications and the books’ sources), and 30 Excel workbooks.
How it fits together
ABA Pocket Check, ABA Phaze Check, ABA Compare and ABA AudioVibes run in the visitor’s browser. Your audio never leaves your machine. It is decoded and analyzed in your browser, and it is never transmitted.
A site built from its source pages and published on Cloudflare. A small sign-in service keeps members’ readings. “Remove from my list” hides the reading from you and from everyone. Its record is kept, with its number and its time, and the removal is logged.
A program on the studio computer runs the clock and writes task times into the production’s own record, kept in Excel, rounded up to the quarter hour. The rooms the session moves through are web pages that read from it.
Built from source into PDFs. The Repair Book is generated from the tools’ own scoring code, so a page can’t say something the tool doesn’t.
One command builds, checks, publishes and records a change, and waits for Brad to type yes. If a check fails, the command stops before it publishes.
The largest single programs: the AudioVibes screens (2,488 lines), the ABA TruSync clock (886), the AudioVibes engine (656), the site’s publishing gate (679) and its build (555), the sign-in service (527), and the one-command ship (161).
How the work is organized
The work runs in parallel by area: ABA TruSync, AudioVibes, the books, this site, outreach. Each desk opens from a written state, so a settled question is read, not asked again.
Architecture, testing, claims about what listeners hear, marketing and AI strategy each have their own member of the AI team. Each job goes to the model that suits it.
Rulings are written down with their dates, and the public ledger shows them. A question is settled against the canon before it is asked.
Claims are checked against known answers and independent references. A fix is not called fixed until a test has failed on the old code.
How it is checked
A change goes live through a single command that builds the site, checks it, publishes it and records it. It waits for Brad to type yes before it does anything.
Before anything is published, a program reads the site’s pages against the rulebook: forbidden wordings, US spelling, dead links, missing search tags, anything loaded from another company’s server. One failure stops the publish.
The measuring code is tested against signals whose answers are known in advance: a planted delay, a flipped polarity, a set loudness. The tests check that each tool finds them.
Not counted here
Left out on purpose, in both counts: the web page files (179 on 8 October, 244 on 16 October) and the code written inside them, the built copies of each tool, the books’ text, the audio and images the tests use, and the packages downloaded from elsewhere. Lines are counted as written, blank lines and notes included. Both counts use the same method: the files the repository tracks, with built copies and downloaded packages left out.
The first count · 8 October 2026
The figures below are the 8 October count, kept as they were measured.
The headline figures · 8 October
34,786
In 169 files, not counting the web pages themselves.
156
Each one a saved, described change (a commit), since the first on 4 September 2026.
4,637
In 32 test files: code whose only job is to check the other code.
4
ABA Phaze Check, ABA Pocket Check, ABA Compare and AudioVibes. Each runs in the visitor’s browser.
What it is written in · 8 October
| Kind | Files | Lines | What it does here |
|---|---|---|---|
| Python | 106 | 21,862 | Runs on the studio computer. Builds the site and checks it before it goes live, ships it, builds the books, and holds the AudioVibes measuring and scoring code. |
| JavaScript | 54 | 12,351 | Runs in the visitor’s browser and on Cloudflare’s servers. The engines and screens of the four tools, the sign-in service, and most of the tests. |
| VBA | 3 | 379 | The macros inside Excel. They drive ABA TruSync, the production record (kept in Excel) that tracks production cost against each milestone. |
| SQL | 3 | 77 | The layout of the member list: the database tables the sign-in service reads and writes. |
| Settings | 3 | 117 | Deploy settings: which server runs the site, under which address. |
| All code | 169 | 34,786 |
Where it lives · 8 October
| Area | Files | Lines | What it is |
|---|---|---|---|
| AudioVibes | 41 | 9,863 | The finished-mix check: loudness and delivery measurement, scoring, the Repair Book and book builders |
| The shared scripts | 26 | 8,156 | The one-command ship, the build checks, the page builders |
| This site | 19 | 3,702 | The site build, the publishing gate, search tags, and the sign-in service |
| Tests | 18 | 2,569 | Checks against known answers, run before a change is trusted |
| ABA TruSync | 15 | 2,539 | The production record of cost and milestones |
| ABA Compare | 8 | 2,372 | Mix versions at matched loudness |
| ABA Pocket Check | 7 | 1,893 | Where parts share frequency and time |
| Studio tools | 14 | 1,828 | Helpers for the studio’s own production work |
| ABA Phaze Check | 15 | 1,330 | Phase and timing alignment between mics |
| Everything else | 6 | 534 | Graphics, outreach and small helpers |
Each tool also keeps tests in its own folder, so the tests row above is only the shared set. The 4,637 figure includes them.