The decision ledger
Brad Huett · ABA Media Platform | AMP · opened 9 September 2026
What this is
A record of who decided what, and who was wrong.
ABA is built by an AI team that two humans direct, the CEO and the CIO. That arrangement invites one particular suspicion, and it is worth naming rather than dodging: that the machines built it and a human pressed Enter. This file is the answer, and it is the only kind of answer that means anything — the working record, including the parts that are unflattering to the machines and the parts that are unflattering to Brad.
Three kinds of entry, and the order is the argument.
| What it proves |
| ORIGINATED | It came from Brad and nowhere else. Design. |
| OVERTURNED | A decision was made and then reversed. Judgment. |
| REFUSED | Brad, or an automated gate, said no. Supervision. |
ORIGINATED leads deliberately. A ledger of corrections alone would quietly cast the AI as the driver and Brad as the brake, which is the exact impression this file exists to kill. The rule underneath that, which is Brad's own applied to process rather than to claims: a record's categories are an argument before anyone reads a single entry.
The rule that makes it evidence
Every entry where the AI was wrong stays in. A ledger with no losses in it is a brochure and convinces nobody.
This is the same discipline as SECURITY_CANONICAL.md, which keeps its own corrections visible, and the same as the rulebook page, which leaves a withdrawn claim struck through where it used to be true. A file that hides its corrections is asking to be trusted rather than checked.
How entries arrive
Gate refusals append themselves. deploy_site.py writes every failed GATE step here automatically — dated, in the gate's own words, never summarized. A record that depends on somebody remembering to write it down decays; one that is a side effect of shipping does not.
Everything else is written by hand, at the time, in Brad's words where they exist. Where a decision is quoted, it is quoted.
Status: PUBLISHED. Ruled by Brad on 9 Sep 2026 as "File now, page later", and the later arrived on 10 Sep: the ledger is generated into /ledger at build time, from this file, so the page cannot disagree with the source and a new entry publishes itself on the next deploy.
He was asked whether to publish it whole or curated and ruled whole, with a sanity check first. The check found one British spelling in running prose, since fixed, and one structural collision worth recording here because it is the file arguing for itself: the entry quoting the gate's own refusal contains the exact string the gate refuses, so publishing this page failed the build. The fix is narrow and it is not an exemption for convenience — the forbidden-wordings scan skips text inside a QUOTED CODE BLOCK on this page only. The rule exists to stop the site MAKING a claim; a quoted refusal is evidence OF a claim being stopped. Prose here is scanned like every other page, so nothing can hide by sitting near a quote.
2026-09-08
ORIGINATED
The milestone gate is a commercial mechanism, not a QA step §
Brad: every milestone closes on a verification task carrying three signatures — client, producer, ABA engineer — and every hour that missed the estimate, over or under, is documented in red on the signed milestone. Those overruns are reconciled before the next milestone opens.
Why, in his account: at Scott Sound in 1985–86, on his first day, Scott told him no client ever wants to pay once they are in the studio — that getting paid and delivering the product are two different jobs, and he was always fighting the gap between them. The gate is his architectural answer to that, forty years later.
Claude had drafted the weaker line "nine milestones, nine signatures" after failing to find the rule enforced in the workbook. Brad supplied the real one. The strong claim is the approved one because he made it, not because it was found.
ORIGINATED
Milestone numbering is zero-based §
Brad: "I love zero-based counting. 1–8 production milestones but 9 milestones in the methodology." Milestone 0 is the kickoff and carries no studio hours. There is no Milestone 9; cell J107 in the workbook says so and is a mistake.
ORIGINATED
A closed enumeration puts a ceiling on the product §
Brad, on S3's "the measurements and the file name, nothing more": "anytime that you see nothing more, it puts a ceiling on what we can do to improve features and how we have to go and retrofit it if we add even the slightest thing that would violate that gate."
What it changed: S3 was amended the same day. The boundary promise stayed absolute; the enumeration was replaced with a commitment to publish the list and change it in public. One sentence had been making two different kinds of promise and nobody had noticed.
ORIGINATED
"Report what they already own. Offer only what is actually yours to give." §
Brad's reasoning, on why "what we would like to send you" was the wrong subject line for a member data notice: the phrase frames disclosure as generosity, and in doing so claims a right that was never held — the right to have withheld it. The reader's data is the reader's. Reporting it takes no credit.
Claude compressed it into the two clauses. The argument is his.
OVERTURNED
The editorial standard applies to everything, not just outbound copy §
Claude proposed narrowing wound-salt-balm to outbound marketing, arguing it could not be applied honestly to a member data notice.
Brad overruled: "At this stage I would all for Wound."
He was right and Claude was wrong. The wound is real, general, and not about the company — you have accounts everywhere and cannot say what any of them hold. What would have been manipulative is inducing fear about this relationship before disclosing. Naming an experience the reader already has, then being the exception to it, is the technique working as designed.
REFUSED
Claude undersold the Milestone 1 offering §
Claude described an M1-only contract as "take the session home and do the rest yourself."
Brad corrected it: production still runs through Milestone 8, and an M1-only offering must deliver a rhythm mix good enough to send a vocalist or a session player as their reference — built into the price.
REFUSED
Claude claimed the dry run could not demonstrate the gate §
Claude asserted a clean-file walkthrough could not show the wall refusing.
Brad corrected it: two or three seconds per task, rounded up to the quarter hour, advancing automatically — nine milestones inside an hour. He had already tested it that way. Claude had read the macro an hour earlier and still failed to assemble it.
REFUSED
Claude wrote British spellings that disagreed with Brad's own workbook §
"cost centre", "licence", "colour", "judgement". The first one contradicted the Cost Management Tool's own Cost Center column. Full audit run and corrected.
2026-09-09
ORIGINATED
Track is a state, not a thing §
Brad: "We don't have tracks. We have performances."
Laying track is the technical pass — cabling, mics, noise floor. The moment capture ends the recording is reassigned as a human performance, and from that point it is never called a track again, because it is traceable to a person who played it. The paradigm is not recording tracks; it is retaining performances.
What it changed the same hour: two lines already shipped on the milestone chain graphic — "Tracks lock at the end of this stage" and "automated as a section, not as tracks" — were wrong under a rule that did not exist when they were written. Both corrected and re-rendered.
And it settled an open naming question by accident. "The Bed Tracks — Milestone One" is not an exception to the rule; Milestone 1 is the only milestone that happens entirely inside the track state.
ORIGINATED
The rulebook's audience rule for the member bulletin §
Brad: the bulletin goes only to visitors who ran at least one test.
Why it is stronger than targeting. The email says "you ran the AudioVibes analyzer while signed in." That is a factual claim about the reader. Sent to anyone who registered and never ran anything, the first sentence is false — in a message whose entire asset is that everything in it is true. "Who is this?" is the symptom; the false sentence is the disease.
ORIGINATED
Links do not belong inside a running argument §
Brad: "If, for whatever reason the words in the link interests them we lose control of the information delivery."
An inline link mid-paragraph is an exit ramp built into your own argument. What it changed: every inline link was removed from body copy across all seven pages and replaced with buttons at deliberate stopping points. Claude then verified it mechanically — fourteen page loads asserting zero non-button links inside main.
3 Oct 2026, the check that was not kept. That verification ran once and was never added to the gate, so inline links crept back onto five pages. Brad found the first by eye on the rulebook. All five became buttons, and preflight_site.py now refuses any non-button link inside main, except in-page anchors, contact lines, eyebrow breadcrumbs, the source column of a reference table, and images that open full size.
ORIGINATED
The decision ledger §
This file. Brad's idea, 9 Sep 2026, and his framing of why it is needed: "to prove that this was not an AI Team only product with me being the stupid human pushing Enter."
Claude's contribution was the three-category structure and the argument for leading with ORIGINATED rather than corrections.
OVERTURNED
The back-button note — Claude said no, Brad's argument won §
Claude argued against adding a return note under the S-number map: browser Back already does it, and twelve repeated links would clutter a page whose restraint is part of its argument.
Brad: "If they know that already I am not there to here them bitch, if they did not know or remember we have done them a service."
The asymmetry beats the objection and it is not close. The annoyed expert costs nothing measurable. The confused reader leaves. Claude's objection was about register, and register is fixable; the confused reader is not fixable by being clever. The note shipped, folded into a sentence about citation so it carries intent rather than instruction.
And the note found a bug. Testing the citation path it invites — a link like /rulebook#s4 — showed the statement landing under the sticky nav bar. An in-page click cleared it by 17px; a cold link missed by 77. scroll-margin belongs to the target and does not apply when a fragment positions the page on load. Moved to scroll-padding-top on the scroller. The note Brad argued for exposed a defect on the exact path it was inviting people to use.
OVERTURNED
The milestone chain graphic does not go on the site §
Claude proposed adding the nine-milestone graphic to /aba.
Caught before shipping by the page's own copy. That page carries a published promise: "The stage list is not on this page, and that is deliberate… when it is published it will be published whole." The graphic is the stage list. Adding it would have broken a promise sitting three inches below it.
The two-ledgers graphic shipped instead — nine numbered intervals, nothing named.
REFUSED
The gate stopped Claude naming the draft statement's subject on a live page §
preflight_site.py failed the build:
rulebook/index.html:80 "paid tier" — S13 covers the paid tier and is
DRAFT / NOT APPROVED. No paid-tier copy may ship in iteration one.
Claude had written a sentence explaining what the thirteenth statement covers. That statement is a draft for something which does not ship in this build, so the sentence was copy for an unshipped tier, on a live page. Well-intentioned, and refused anyway. A rule written for marketing stopped a footnote written at midnight. Rewritten to say the statement is a draft and not published, without naming what it covers.
AND IT HAPPENED A SECOND TIME, TO THIS ENTRY, ON 10 SEP 2026. Publishing the ledger meant publishing this entry, and this entry's own prose repeated the phrase the gate refuses — so the record of the refusal was itself refused. The quoted block above is exempt, because a quoted refusal is evidence rather than a claim. The prose was not exempt and should not have been, so the prose was rewritten instead. The rule caught the same mistake twice, in the same words, a day apart, in a file whose entire purpose is to record that it did.
REFUSED
Claude said "seven stored fields" and the answer was fifteen §
Claude wrote "the seven stored fields" twice in conversation and into the bulletin's notes. Reading the live Analysis collection found fifteen columns — eleven written by the tool, four by the host — one of which is an OBJECT holding the entire report.
This is the same defect S3 was amended to remove, committed by Claude while helping publish the correction for it. The published list was written from the live collection instead, and the bulletin's own summary paragraph was rewritten to point at that list rather than restate it.
REFUSED
Claude read Mountain time as UTC. Twice. §
Claude told Brad it was five in the morning and to get some sleep. It was approximately ten at night. The same error had already cost an exchange earlier in the project, when Claude claimed two files had not arrived based on timestamps that were seven hours out.
REFUSED
Claude shipped a component that rendered nothing §
The first build of the two-ledgers section produced nine empty rows on both sides — width and height do nothing on an inline <span>. The entire visual argument was missing and the page still looked deliberate. Caught by looking at the render rather than trusting the markup.
REFUSED
Claude miscounted the rulebook's own statements §
Claude wrote "thirteen chips" and "eleven approved" for a page carrying twelve statements, ten of them approved. Corrected before the map was built — an enumeration error, on the page about enumeration errors, in the same hour as the "seven fields" one.
REFUSED
A deploy reported success and shipped nothing §
Not a rejection — a hole where one should have been. BUILD passed, GATE passed, DEPLOY succeeded, and wrangler said No updated asset files to upload because the files were still in Downloads. Every stage told the truth and the net result was a no-op.
No gate could have caught it. A gate checks that what passes through it is correct; it cannot check that anything passed through it at all.
What it changed: Brad specified a staging step — "I want a deployment process using PowerShell to take files to the correct folder" — and stage_site.py now refuses, with a non-zero exit, when every incoming file is already identical to what is in the repo.
REFUSED
Claude declared a shipped deploy unshipped, on three reads from one instrument §
The S6 amendment deployed correctly at 07:17. Claude then fetched the live page three times — twice on distinct cache-busting URLs — and all three returned the withdrawn wording. Claude reported the deploy had not shipped, and reasoned out loud that two different cache keys returning old content "points at the origin, not the edge."
The page had been correct the whole time. Loading it in a real browser on Brad's machine showed both the amended statement and the amendment note. The fetch tool was serving a stale copy and Claude never checked its answer against a second, independent path.
The defect is not the stale cache — it is the inference. Three agreeing reads from one instrument is one read, and Claude presented the agreement as corroboration. This is the same error the rulebook itself is about: an enumeration checked against itself. It also inverted the 8 Sep failure — that one was a deploy that reported success and shipped nothing; this one was a deploy that shipped and was reported as failed.
Also worth recording, because it reads like the old fault and is not: wrangler's No updated asset files to upload on the confirming run was the CORRECT answer. Cloudflare already held that exact file by hash from the first run. The same sentence meant a defect on 8 Sep and correct behavior on 9 Sep, which is why the sentence is not the test — the live page is.
The standing check, by analogy to the one S6's own amendment produced: before reporting that something is or is not live, confirm it on a second independent path. A repeated read is not a second opinion.
REFUSED
Claude invented a reason to doubt Brad's own equipment count §
Drafting the studio page, Claude flagged "more than 7,400 plugins" as a credibility risk and wrote into the page that counts like it "are assembled from presets and variants."
Brad: "I wish that was true. Every time I start studio it clears those numbers for each licensed plugin. I do have that many. Not by choice but for compatibility for stems and other DAW plugins: ProTools, Reaper, Studio One."
Two separate errors, and the second is worse than the first. The number was real — it validates on every start. But Claude did not merely doubt it; it supplied a mechanism it had guessed at ("presets and variants") and wrote that guess onto a page as though it were known. Doubting a number you cannot check is defensible. Publishing an explanation you invented for it is the same defect as a confident approximation, which is the thing this company refuses to ship. The sentence was removed before anything deployed.
And the correction was worth more than the claim. "Not by choice but for compatibility" turns the count from a vanity number into a service fact: the library is installed once per supported host so that a client is never asked to flatten a session before work can begin. That became its own section — "Send the session. Not a flattened copy of it." — and it is the strongest passage on the studio page. Claude's instinct was to cut the number. Cutting it would have thrown the argument away with it.
The standing check: when a domain figure looks wrong, ask what produces it. Do not publish a theory of where it came from.
OVERTURNED
"No account, no upload, no wait" — flagged by marketing, ruled acceptable by Brad §
The marketing agent flagged audiovibes.html:26 as sitting close to banned wording, noting that rulebook.html:117 names "we don't upload your files" as the exact softening S2 must never become. Two live pages appearing to disagree about uploads, on a site whose first sentence is about claims benefiting their author.
Brad ruled it ACCEPTABLE, 9 Sep 2026. Recorded here so it is not re-flagged and quietly "fixed" by a later scan — the line was reviewed and kept.
Why the ruling holds. The sentence is describing FRICTION, not security. It completes as "It runs here, in this page, on your machine" — it tells a reader what he does not have to do before using the tool, in a paragraph about using the tool. It is not an enumeration of what does or does not leave the machine. And it is not one of the six FORBIDDEN strings, which is why the gate passed it.
THE CONDITION THAT MAKES IT ACCEPTABLE, and it is load-bearing: S1 and S3 appear in their approved form on the same page, below it. The friction sentence is safe because the security sentences are present and verbatim. If S1/S3 are ever moved off /audiovibes, this line stops being acceptable and must be revisited. The ruling is conditional on a fact about the page, not on the words alone.
2026-09-10
ORIGINATED
Publish the screw-up — three typos burned into Brad's own video, and the ruling to shine a light on them §
THE DEFECT. Seven Fish in a Phish Pond — Brad's modal-exchange demonstration, submitted for academic credit and published on his instructor's student page — carries three errors burned into the render:
| On screen | Should read |
|---|
| "The Aolean Phish" | Aeolian |
| "A Model Exchange Cheat Sheet" | Modal Exchange |
| "The halve steps define the emotional changes" | half steps |
The 0:00 title card gets it right — Modal Exchange Demonstration Video — so the "Model" error is on the later card only. Found 10 Sep 2026 by reading a contact sheet at a resolution where the overlay text finally resolved. Two earlier passes missed them because the tiles were too small to read.
BRAD'S RULING, and it is his idea: document it, leave it up, and use it as the worked example for the rules-based gating architecture. His words: "I never thought I'd get a chill for screwing up… you like the idea of us presenting not what we do well, but what we did wrong and how we fixed it."
WHY IT IS A USE CASE AND NOT A CONFESSION — the analysis he was given.
There was no gate. preflight_site.py reads a forbidden-wordings list and fails the build on a bad string; it caught a draft statement's subject on the rulebook at midnight — the refusal quoted two entries above. But text inside a video was never treated as copy. It was treated as design, so it never passed through the check every sentence on the website passes through. Not carelessness — a boundary the architecture did not know existed.
And the cost is set by how far past the gate the error got. A typo in HTML is a one-line edit and a deploy. The same typo burned into a 5:30 render is a re-render, a re-upload, and a correction on a third party's site where an instructor and his students have already seen it. That is the milestone wall's own logic, arriving from a direction nobody planned for: check at the boundary, because after the boundary the fix stops being an edit and becomes a production job.
Generalizes to anything rendered, flattened, pressed or handed to a third party.
WHAT IT CHANGES IN THE LEDGER ITSELF, and this is the part worth keeping. Every prior entry is either Brad originating something or the AI being wrong. This is the first entry where the human was wrong. A ledger that only ever catches the machine is a ledger with a thumb on the scale — it quietly argues that the human is the reliable half, which is not what a supervision record is for. One entry where the owner shipped the error, published by the owner, is worth more than ten where the machine did.
PRACTICAL CONSEQUENCE, decided the same hour: the 95-second excerpt chosen for /aba runs 1:15–2:50 and covers Ionian, Mixolydian and Dorian. Every label inside that window is spelled correctly — all three errors fall outside it. The method argument ships clean; the errors get published deliberately, as exhibits, where the corrections story lives rather than in the middle of the demonstration.
STILL OPEN: whether the exhibit is a still frame of "The Aolean Phish" on a page, or stays a ledger entry until the ledger itself is published. File now, page later still governs.
REFUSED
Claude called a real file a symlink on one lister's word §
10 Sep 2026. Asked to confirm a WAV had landed in media-source, Claude reported it as a link rather than a file, with no size, and built two paragraphs of consequence on top of that — Dropbox will not sync it, a checkout elsewhere gets a dead pointer. Brad sent a screenshot of Explorer: a 89,877 KB WAVE file, dated 23 June, exactly where he put it.
The lister was describing a Windows reparse point — almost certainly a cloud placeholder — in POSIX terms it does not have the vocabulary for. STANDING RULE FROM THIS: for file type and size inside a synced folder, that tool is not evidence. The operating system's own view is.
Fifth instrument failure in one day, after three stale reads of a deployed page, a search that could not find a class it was looking straight at, and blank screenshots after a scroll. The pattern is not that the instruments are bad. It is that a single instrument reading, unconfirmed, has now been wrong five times and been believed four of them.
ORIGINATED
Brad's doubt stopped a measurement being published against the wrong mix §
10 Sep 2026, his words: "I just pulled a mix from about 6 test mixes on the ABA production. If you are comparing to another one I am not sure it would be the same test version."
Claude had been proceeding toward measuring that WAV to confirm a score computed from an MP3. Brad's doubt was correct and it was measurable: on 100 ms loudness envelopes with alignment search, the same audio through an encoder returns correlation 0.99999 and a residual of 0.015 dB rms; the fixture MP3 against his WAV returned 0.793 and 2.11 dB rms, with a single frame differing by 16.4 dB. Different mix. Measuring it would have produced a number that looked like a verdict and was a different piece of audio.
THE STRUCTURAL FINDING UNDERNEATH IT. The stored report identifies its subject as artist: "forbidden_journey", title: "", path: "tests/forbidden_journey.mp3". The identity was derived from a filename stem — the one thing that drifts — the path is relative to a tree that has moved, and the file measured was a lossy delivery derivative with no field capable of saying that mattered. A published grade attached to a work title that maps to at least six pieces of audio is unfalsifiable, which on this site is the worst thing a number can be.
Not urgent: the grade is a local fixture, consumed by nothing shipped. Claude checked that only after building three messages of urgency on the assumption that it was live, and said so.
ORIGINATED
The third toolbox tool is named ABA Custody §
10 Sep 2026. Brad set the structure first: ABA has a TOOLBOX — the Cost Management System, AudioVibes AI, and the assets tool — and the ABA Media Platform, featuring the milestone-based production process, USES that toolbox and is the reason it exists. Modularizing tools for separate sale is explicitly a later conversation.
His working name was "ABA Assets Control System". Two objections were raised and the name changed on both. AACS already names Advanced Access Content System, the Blu-ray copy-protection scheme — an acronym for a system that restricts what an owner may do with their own media, which is the opposite of this. Same collision class as the naming rule on the ABA Communication Protocol. And "Repository" was ruled out by H3's own wording: not storage; ingest gating plus custody.
Named ABA Custody, his word: "Absolutely". Custody carries both halves in one word — the thing is held, and somebody is answerable for it — and it is the word that makes "in perpetuity" read as an obligation rather than a disk. Requirements: ASSET_CUSTODY.md.
ORIGINATED
The cost workbook is named ABA TruSync — with its collisions on the record §
10 Sep 2026. "Cost Management System" was never a name, only a placeholder Brad had never liked. It also describes about a third of the thing: the workbook has an estimating half AND a live stopwatch that auto-logs task to task, documents every hour that missed the estimate in red, and reconciles the overruns before the next milestone opens.
THE FIRST PASS FAILED ON HIS OWN TEST. Marketing's pick was ABA Accord, and Brad ended it in one line: "I am not sure accord is a US English word. I don't know what it means." He is the man who says the name out loud to a guitarist, on the document that guitarist is about to sign. If the owner needs a gloss, the name is dead. The second pass — his instruction to try modern music vernacular — produced ABA Scale, which he killed with two better objections: a scale MEASURES, and AudioVibes is already the thing that measures; and the AFM union sense is insider knowledge his actual buyer does not have.
HE BROUGHT THE WINNER FROM OUTSIDE, and said so plainly: "I cheated on you." Another model produced TrueSync Pro. Two changes were argued and accepted. "Pro" went — a tier suffix implies a lesser version and dates the name to about 2005. And "sync" was bounded to the hours, never the assets: sync's dominant meaning in 2026 is mirrored copies where deletions propagate, which is precisely the behavior that destroys a restore point. Naming an archive that would teach everyone the wrong mental model about the one system whose job is not losing things. ABA Custody keeps the assets; TruSync keeps the hours honest.
WHAT MAKES IT RIGHT: true-up is the actual term for reconciling an estimate against what happened, so "true" carries the verification and "sync" carries the agreement — the session floor and the estimate, held against each other.
AudioVibes AI measures the audio. ABA Custody holds the assets. ABA TruSync settles the hours.
SPELLING SUPERSEDED 13 Sep 2026. This entry was written on the 10th, when the form was TrueSync. Brad ruled the spelling TruSync in session on the 13th and it is registered in retired_phrases.json. Our own mentions above have been moved to the ruled form; the three third-party products keep their real trademarks, because a collision record that corrects someone else's name records nothing.
KNOWN COLLISIONS, ACCEPTED WITH EYES OPEN — recorded so nobody rediscovers them and thinks they were missed. Flawless TrueSync is a trademarked AI visual dubbing product, which is a media-AI collision in his own industry. Zoho WorkDrive TrueSync is a shipping file-sync desktop client — the exact product class the wording objection above describes. Starfish Software shipped a TrueSync in the PIM era. Brad was given all three and ruled the name good anyway. The reasoning that makes that defensible: this is a tool name inside the toolbox, not a marketed brand. It costs nothing while it lives on his own documents beside ABA Custody. It becomes a real problem only if the tools are ever modularized and sold separately — which is explicitly a later conversation.
One word struck from the description before it becomes copy: "perfectly synchronizes." The tool does not perfectly align anything; its value is showing where the two did NOT match. A claim of perfect alignment claims the gap never happens, and the gap is the product.
ORIGINATED
The asset argument stopped being a design and produced a fact §
10 Sep 2026, at the end of the session that started it. The oldest open question in this project — which file was the published grade measured from — is closed, with a hash rather than a recollection.
THE ANSWER. Forbidden Journey Master.wav, SHA-256 beginning DE485A36F5CD, 92,008,066 bytes, 24-bit/48 kHz, modified 2 Aug 2026 — and it does not live in the project tree. It lives in Music\iTunes\iTunes Media\Music\Unknown Artist\Unknown Album\.
THE METHOD, and the control came first. tools/mix_compare.py, built the same night, run against twelve candidates. The instrument calibrates itself before it answers: the reference is round-tripped through an encoder and compared to itself, which returned correlation 0.99999 and a residual of 0.012 dB rms. The match returned exactly the same figures. Every other candidate landed between 0.13 and 0.93. A verdict stated relative to a measured floor, not to a hopeful constant.
THE FINDING THAT MATTERS MORE THAN THE ANSWER. There are two different files named Forbidden Journey Master.wav on that machine. The other one — 9F6D41C8048E, 91,737,582 bytes, 5 Aug — sits in Mixes\Archive\, which is where a master belongs, and it is a different mix: correlation 0.774 against the measured source, no closer than an unrelated bounce of the same song.
Three days and 270,484 bytes apart, same name. Anyone tracing that grade by filename would have found the project copy, in the right folder, and been wrong with no way to know it. That is the case for identity-by-hash proved on Brad's own disk instead of argued on a page — and it is the single strongest piece of evidence this project has produced for ABA Custody.
WHAT ELSE THE INVENTORY TURNED UP, from one PowerShell command over the whole user folder: 16 files for this work, 14 distinct, in two format families whose size ratio (1.633) is exactly (24x48)/(16x44.1) — same duration, two containers. Two duplicate pairs, each a project copy and an iTunes copy. One 0-byte WAV sitting in a project TEMPLATE folder, where it will be copied forward into every future project until somebody removes it.
A CORRECTION CLAUDE OWES, and it is the same class as the rest of tonight: Claude asserted from a screenshot of Brad's folder template that his tree had no home for a mix. The disk says otherwise — …\1-DAW ABA Media\Forbiden Journey\ Mixes\Archive\ exists and always did. The real defect is worse and more interesting: that path runs seven levels deep and spells the work's name three times, two of them "Forbiden" and one "Forbidden". The mixes were never homeless. They were buried under a name that changes as you descend.
RECORDED IN THREE PLACES SO IT CANNOT BE LOST AGAIN: WHICH.txt at the work root, subject_id on the demo fixture in mvp_data.json, and here.
Entries below this line are appended automatically by deploy_site.py.
ORIGINATED
The gate was proven beatable by our own verifier, and the hole is closed §
10 Sep 2026. Brad asked the team to sanity-check a proposed paid access offer. Part of Fletcher's brief was routine: would draft copy for this trip the existing gate? Fletcher did not answer it by reading the rules. It copied the built site to a throwaway directory, ran the real preflight_site.py against the real eighteen patterns, confirmed a clean baseline of twelve pages, injected a priced draft, and watched four rules fire.
Then it wrote a second draft of the same offer and the gate passed it clean.
"When your contract closes, ABA continues to hold every source your session
produced — the performances, the mixes, the master, the stems. $1.99/month
keeps it live, and you can pull any file back at any time."
zero hits · 12 pages · PASS
THE TWO HOLES, both reproduced rather than argued. $1.99/month does not match \bper month\b, and neither does a small monthly fee — a price written the way people actually write prices walked straight through a rule written for the phrase nobody uses. And there was no rule anywhere checking the storage claim itself. The sentence S15 is reserved for — a custody claim about material belonging to a client — was not covered by a single pattern.
WHY THIS IS THE SERIOUS ONE. /about tells visitors: "A build refuses to ship a forbidden wording. Not a reviewer's judgment — a check that fails and stops." On the one subject where the claim is most dangerous and least verifiable, that sentence was overselling what the gate did. The gate caught the words a price arrives wrapped in and never once looked at the promise.
THE FIX. Three rules added the same night. One fails the build wherever a custody verb — hold, keep, store, retain, archive, preserve — lands beside material belonging to a client, for as long as S15 does not exist. One fires on $ followed by a digit, anywhere, because there is no price on this site and the first one should be a decision rather than a draft artifact. One catches the shapes the old rule missed: /mo, /month, monthly fee, annual subscription.
AND THE FIX ITSELF NEARLY SHIPPED BROKEN. The first version of the custody rule caught keep your masters and retain your assets and let Fletcher's actual sentence through, because the noun list held files, assets, masters and material but not session — and Fletcher had written "every source your session produced". A rule tested only against examples the author invented is a rule that passes its own exam. It was widened and re-tested against the original attack, which now fails seven ways, while all twelve real pages still pass.
THE PART WORTH KEEPING. Fletcher had nothing riding on the answer. It was asked whether the gate worked and it went and tried to beat it, which is the behavior the roster page claims for an isolated worker, doing it unprompted against the mechanism this company is proudest of. A gate nobody has attacked is a backup nobody has restored.
POSTSCRIPT, four hours later. This entry was refused by the rules it describes. Ten failures on the first build after it was written: three on the word for a recurring-fee arrangement, and two where the sentence explaining the custody rule stated the pattern in the shape the pattern matches. Prose rewritten rather than exemption widened — the same call as paid tier on this page in September. A rule strong enough to refuse the document announcing it is a rule that was worth writing, and the alternative on offer was to carve out an exception for our own copy, which is the exact move this entire file exists to argue against.
ORIGINATED
Publish the build record, and declare the gap at the top §
20 Sep 2026. Brad asked whether there was any value in a one-line-per-build list of every deploy since day one, set in six point type. The honest answer had a correction inside it: there is value, and "since day one" would have been false.
DEPLOY_LOG.md opens on 11 September, which is about the fourth day of this site. Earlier deploys happened and were not recorded because nothing was recording them yet — and one of the absent rows is the 8 September deploy that shipped an empty site. That failure is the reason deploy_site.py exists, the reason the log exists, and the reason there is a digest column at all. The most instructive build in the project is not on the page, because the tooling that would have caught it was written in answer to it.
His ruling was to build it, and the reason he gave is the entry. In his words: "these are the things we learn about when they have been violated, like today losing our first real build tracking." Then, four words later: "Wisdom fueled by pain." Filed to the phrase archive as 0.5, title-grade, carrying the same constraint 3.3 carries — it may never be lifted clear of the specific failure it names, or it becomes a boast about humility.
WHY THE PAGE IS GENERATED AND NOT WRITTEN, and here the argument is stronger than the one behind /ledger. A decision ledger that had been hand-copied would merely drift. A build record that a person typed is not a record at all — it is a claim about one. Its entire value is that nobody chose what went on it. So deploy_site.py appends a row, build_site.py renders the file, and the next deploy publishes its own row without anyone deciding to publish it. A missing DEPLOY_LOG.md fails the build rather than quietly producing a shorter page.
THE BANNER IS A CONSTANT, NOT A COMPUTATION. It would have been easy to have the gap notice disappear automatically once a row exists above a date. It does not. If those early deploys are ever recovered, a person retires the banner after looking at what came back — because the thing being asserted is we know what is missing, and that is not a claim a date comparison can make.
The row that says unknown is left in and marked rather than filled in from memory. It is the first deploy logged, and the script was not yet capturing what Cloudflare returned. A record you may edit afterwards is not a record.
WHAT WAS NOT CLAIMED. Eleven rows over ten days is a thin record, and the page does not pretend otherwise. Its worth compounds; today it is a habit with evidence attached rather than a body of evidence. The claim it does make is the only one that holds: every row is there, the list is complete from the day it starts, and its gap is declared instead of closed.
A NAMING COLLISION WAS CAUGHT BEFORE IT SHIPPED. The first proposal called this the provenance report. That name is already taken — PROVENANCE_REPORT_SPEC_2026-09-16.md defines ABA-PR/1, the client-facing authorship record, whose section 6 is itself called a provenance log. Same word, different scope, and the same shape as the Register collision found the same week. It is the build record, at /builds.
ORIGINATED
The engineer's estimate is the studio's promise §
28 Sep 2026. Brad, after lying down with it: in any ABA milestone task that is engineering only, if the actual time exceeds the estimate, the studio eats it. His reason: the studio engineer estimated those hours during Milestone Zero. The client agreed to the engineer's number, so a miss is the studio's own estimate being wrong, and billing it would charge the client for the studio's mistake.
The other half, ruled the same night: performance overruns, meaning extra takes within the three-take limit, stay with the client. The overrun is still recorded in red; only who pays changes. Engineering only means role Engineering and rate code EL. Sessions arriving from Pro Tools or Reaper are migrated into Fender Studio Pro, the one DAW the ABA template is built in, so the M0 task where the engineer confirms the session source and estimates any migration is engineering work and falls under the rule.
REFUSED
A gate recorded as built had never existed §
28 Sep 2026. Reading the book, Brad found British spellings in it: "judgement", "organised", "labour", "centre", "rigour", "afterwards", and a "practise" that Marv had written the same night. The spellings were not the finding. The finding was that nothing had stopped them. Task board 125 recorded register_check.py as BUILT on 17 Sep, with a proof that it fails on demand, and the script was nowhere in the repo. Git had no record of it. The 8 Sep entry above says the problem was caught and corrected; it could not say that the check meant to keep it corrected had never been saved.
No report from the machines raised it. A human reading the output did. The check is rebuilt, now refuses on both the site and the book, and was made to fail before it was trusted. Detail: FAILURE_LOG.md, 28 Sep, "The US-English check existed only on paper".
REFUSED
The Session Clock lost its buttons, and nothing said so §
28 Sep 2026. Brad opened the Cost Management Tool and found the Session Timer with no START, PAUSE, RESET or SET BILLING TIME, only an empty band with text in it. Every workbook saved since 30 Aug carried the same damage. By every sign, a rewrite through a Python library had dropped the four buttons and the code names that bind the macros to their sheets, and raised no error. The code behind the buttons was intact the whole time; there was simply nothing left to press.
This is the studio's most valuable instrument, and COST_MODEL_QC_2026-09-12.md had already warned in writing that the library does not round-trip it. The warning was on file. The damage went unreported for four weeks, until the owner opened the file. Restored by surgery from the last good copy and proven cell for cell; the clock still has to run in Excel before it is called fixed. Detail: FAILURE_LOG.md, 28 Sep.
2026-09-11 02:43 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
deploy_site.py exists in 2 places:
amp-site/deploy_site.py
Claude outputs/deploy_site.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-11 03:09 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
deploy_site.py exists in 2 places:
amp-site/deploy_site.py
Claude outputs/deploy_site.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-11 19:36 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
build_site.py exists in 2 places:
Claude outputs/build_site.py
amp-site/site/build_site.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-13 09:54 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
extract_cost_model.py exists in 2 places:
extract_cost_model.py
Claude outputs/extract_cost_model.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-17 20:00 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
tune.py exists in 2 places:
tune.py
Claude outputs/tune.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-17 20:04 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
tune.py exists in 2 places:
tune.py
Claude outputs/tune.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-27 20:48 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 19 page(s)
2 FAILURE(S)
book\index.html:50 link to /assets/produce-the-record.pdf � no page is built there.
book\index.html:56 link to /assets/produce-the-record.epub � no page is built there.
Nothing ships until these read clean.
2026-09-27 21:25 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
build_book.py exists in 2 places:
book/build_book.py
audiovibes/book/build_book.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-09-29 13:14 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 20 page(s)
1 FAILURE(S)
book\index.html:62 "Calibre" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-01 02:02 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 21 page(s)
1 FAILURE(S)
book\index.html:131 "Calibre" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-01 19:10 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 22 page(s)
1 FAILURE(S)
book\index.html:131 "Calibre" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-01 20:18 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 23 page(s)
2 FAILURE(S)
book\conversations\index.html:75 "nothing is uploaded" � softens S1. The approved sentence names transmission, not upload.
book\conversations\index.html:84 "nothing is uploaded" � softens S1. The approved sentence names transmission, not upload.
Nothing ships until these read clean.
2026-10-03 01:44 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
ship.py exists in 2 places:
ship.py
_to_delete/ship-shim/ship.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-10-04 20:58 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
build_page.py exists in 2 places:
compare/build_page.py
phaze/build_page.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-10-06 02:34 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 28 page(s)
2 FAILURE(S)
audiovibes\repair-book\index.html:62 inline link to /book/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
book\index.html:63 inline link to /audiovibes/repair-book/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-06 02:35 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 28 page(s)
2 FAILURE(S)
audiovibes\repair-book\index.html:62 inline link to /book/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
book\index.html:63 inline link to /audiovibes/repair-book/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
8 Oct 2026, 03:02 MDT (Brad, Pending Board desk). The tools stay free, and it is a condition, not an absolute. Every ABA tool is free while it costs ABA nothing to run, which holds as long as it runs in the browser (the embedded-code model) and does not hit a ceiling of what a modern browser can do. Each tool exists to solve a problem Brad has, not to fill a toolbox to sell. Extends the canon line "Why the tools are free" (audiovibes/book/PERCEPTION_PASS_CASE_03_WHYFREE_2026-10-06.md); per his no-absolutes rule, write it as "free while", never "always free".
8 Oct 2026, 06:11 MDT (Brad, AI Team desk). The contractors go by surname, all five. Helmholtz (perception), Fletcher (verification), Shannon (AI guru), Neve (studio architect), Ertegun (marketing). "Rupert" became Neve and "Ahmet" became Ertegun. Older files that say Rupert or Ahmet (ASSET_CUSTODY.md, audiovibes/SPEC_STEM_AND_RACK_2026-10-01.md, the plugin README and two agent files) are historical records and stay as written; the plugin's agent files and README are corrected at the next plugin release.
2026-10-08 07:31 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
build_page.py exists in 2 places:
phaze/build_page.py
pocket/build_page.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
8 Oct 2026, 13:05 to 18:42 MDT (Brad, ABA Pocket Check desk). Pocket Check rulings of the day. (1) The tool calls itself "beta", as the site does. (2) The timing-lane section always shows; on a set without a kick and bass it says why there is no lane ("a missing section is going to look like it's broken"). (3) Every set has its own generated example; the kick-and-bass example is never shown under another set's names. (4) Every feature on Neve's B list is built (B1 to B8). (5) Solo stays where it is ("you only lose it the first time"). (6) "Performance" replaces "part" everywhere a user reads it, in the tool and the guides; the approved claim sentence now says "performances" (row for his confirmation on the use-case page). (7) From Helmholtz's grading, accepted into the guides: a measured timing offset is never printed with a feel name, including on a generated example. Record: BACKLOG.md POCKET-CHECK and the FL of 8 Oct 19:52.
8 Oct 2026, 20:17 to 23:18 MDT (Brad, ABA Pocket Check desk). Rulings from his walk-through. (1) "Pocket Check" is a WORKING TITLE, reopened once the walk-through and his real stems are done (BACKLOG POCKET-NAME). (2) Too many words before any tool: say as little as needed, in baby steps; this applies across the tools. (3) /pocket-check is the template page for the site: title, the gray orientation line ("Friggin' love that"), two sentences, a 40/60 hero picture, the tool at once, the beta card and audio statement after it; 1600 px wide. (4) The heading is "Find where your performances share space": performances plural, space singular ("the plural is on performances"). (5) The hero art is final: "there is no replacement art." (6) NO WHITE FILLS: "no white, but you gotta have white text and white lines"; shared space is soft violet. (7) The leading silence is skipped by "the exact same sample subtraction" from every file. (8) Solo picks any two or more performances; A plus B is B plus A. All built and shipped as builds .12 to .17.
8-9 Oct 2026, 23:26 to 00:22 MDT (Brad, ABA Pocket Check desk). (1) THE NAME STANDS: "ABA Pocket Check", ruled 00:22 ("Pocket Check works for me then") after the team's read (Ertegun and Neve keep; Helmholtz a map name). No longer a working title. (2) FABLE FOR DESIGN WORK while allowance remains before the weekly reset, even under 45 minutes; Opus for talk, rulings, FLs and quick fixes (23:42, standing). (3) The Toolbox Wheel: six questions around the tool, the other tools as icon beads in order, AudioVibes the rim; "finished performance", not "finished mix". (4) The Stargate was declined as a basis (a studio's design); the frequency dial, the tool's own 29 bands in a turning ring, is the original that answers the thought. (5) The four draft icons go to the graphics session; the Phaze mark must read as two waves, not a horn.
9 Oct 2026, 00:36 to 02:39 MDT (Brad, ABA Pocket Check desk). (1) The Toolbox Wheel goes LIVE as the top of /toolbox (01:11), the tool cards kept below; its six rows and milestone names ship as they stand, TruSync may correct them. (2) The wheel shows Pocket Check once, in the hub, as "Pocket, the mark, Check"; the arrow and the order carry the route; no step numbers anywhere (01:19-01:20). (3) The rim names tools, not jobs: AUDIOVIBES at 12 (00:54). (4) The icons are the hot spots: a tool chip opens that tool's page, in the same tab on the site ("keep them on the site", 01:10). (5) Each question shows its milestone with its number and the task pulled from it (01:24). (6) The headline stays: "One tool answers them, and the others know when to step in" (02:18). (7) On phones the wheel is a still with its words off; the cards carry the words (02:28). (8) The Phaze Check mark shows the problem, not the fix: two waves, the lower slightly late (02:31). (9) "AI lead agents" replaces "trolls" (02:27). (10) TRANSPARENCY, his standing position: every part of the company open, money and marketing included; nothing with a questionable moral compass hidden; the checking seats exist to keep it so (02:25). (11) The overnight check's rows: approved 1, 2, 3, 5, 6, 10, 11, 13; flags to talk through 4 (since built), 7, 8, 9, 12, 14 (02:22).
9 Oct 2026, 12:42 to 12:47 MDT (Brad, ABA Pocket Check desk), P. THE RECEIPTS RULE, standing for the whole site. Every claim on the site carries its receipt: the rule, log or test behind it, with its timestamp ("How we know"). Held back only for open security issues (published once fixed, as found-on and fixed-on), other people's data, and others' confidential terms. Receipts are curated (the one entry that proves the claim, with a link to the full log), not dumped. On accessibility and privacy the site says what was checked and when, never "compliant". His architecture behind it: "five star, as close to top of the line as I can afford", and completely transparent to anyone who asks about any aspect of the site. Same exchange: row 8 of the overnight check (pause on the wheel) was handed to Marv's judgment ("do what you believe is right"). Ruled by Marv under that DF: no button on the wheel; a quiet "Pause motion" text control in the key line under it, folded into the row 9 accessibility batch.
2026-10-09 12:56 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 30 page(s)
1 FAILURE(S)
ledger\index.html:431 "judgement" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-09 13:15 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 30 page(s)
1 FAILURE(S)
ledger\index.html:431 "judgement" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-09 13:15 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 30 page(s)
1 FAILURE(S)
ledger\index.html:431 "judgement" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-09 13:17 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 30 page(s)
1 FAILURE(S)
ledger\index.html:431 "judgement" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
THE EMAIL CANON, every first-contact email, not only vendors (Brad, Schools and Curriculum desk, 9 Oct 2026, 22:47)
Brad, widening the 6 Oct vendor-door ruling: the FabFilter trademark email (outreach/SEND_KIT_2026-10-02.md, DAY 1, sent 1 Oct; "This is not a problem for us", Case 302744) is the TEMPLATE for emailing anyone. The steps:
- Assess the culture, the region and the audience before drafting. US regions differ as much as countries ("people in Texas don't think the same as people in California, New York or Washington, DC").
- The email carries content. Never just "can I come and teach at your school?"
- A who-is-this-guy link (abamediaplatform.com/about/sources/), so the reader can tell a competent local from "some drunk off the street".
- Links to what we are telling or showing them (for schools: what their students will see).
- Calls to action.
The FabFilter mechanics that carry over: quote the reader's own words exactly; state what is already in place; offer numbered answers, any one of which moves things forward; make one commitment; close "If this is not yours, who should it go to?". Then Helmholtz's perception pass before Brad sees it (premise first, then wording). Links are words, no fake "Re:", no "favor". First applied: the UNC Purchasing email, draft 2 (campaigns/UNC_PITCH_SEND_KIT_2026-10-09.html).
2026-10-10 22:43 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
addcover.py exists in 2 places:
_wip/rb4_pre/addcover.py
audiovibes/repair/pdf/addcover.py
build_pdfs.py exists in 2 places:
_wip/rb4_pre/build_pdfs.py
audiovibes/repair/pdf/build_pdfs.py
build_repair_book.py exists in 2 places:
_wip/rb4_pre/build_repair_book.py
audiovibes/repair/build_repair_book.py
build_two_part_draft.py exists in 2 places:
_wip/rb4_pre/build_two_part_draft.py
audiovibes/repair/build_two_part_draft.py
compare_part.py exists in 2 places:
_wip/rb4_pre/compare_part.py
audiovibes/repair/compare_part.py
fix_links.py exists in 2 places:
_wip/rb4_pre/fix_links.py
audiovibes/repair/pdf/fix_links.py
mk.py exists in 2 places:
_wip/rb4_pre/mk.py
audiovibes/repair/pdf/mk.py
mk_artifact.py exists in 2 places:
_wip/rb4_pre/mk_artifact.py
audiovibes/repair/pdf/mk_artifact.py
phaze_pages.py exists in 2 places:
_wip/rb4_pre/phaze_pages.py
audiovibes/repair/phaze_pages.py
phaze_part.py exists in 2 places:
_wip/rb4_pre/phaze_part.py
audiovibes/repair/phaze_part.py
pocket_part.py exists in 2 places:
_wip/rb4_pre/pocket_part.py
audiovibes/repair/pocket_part.py
repair_pages.py exists in 2 places:
_wip/rb4_pre/repair_pages.py
audiovibes/repair/repair_pages.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-10-10 22:45 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
addcover.py exists in 2 places:
_wip/rb4_pre/addcover.py
audiovibes/repair/pdf/addcover.py
build_pdfs.py exists in 2 places:
_wip/rb4_pre/build_pdfs.py
audiovibes/repair/pdf/build_pdfs.py
build_repair_book.py exists in 2 places:
_wip/rb4_pre/build_repair_book.py
audiovibes/repair/build_repair_book.py
build_two_part_draft.py exists in 2 places:
_wip/rb4_pre/build_two_part_draft.py
audiovibes/repair/build_two_part_draft.py
compare_part.py exists in 2 places:
_wip/rb4_pre/compare_part.py
audiovibes/repair/compare_part.py
fix_links.py exists in 2 places:
_wip/rb4_pre/fix_links.py
audiovibes/repair/pdf/fix_links.py
mk.py exists in 2 places:
_wip/rb4_pre/mk.py
audiovibes/repair/pdf/mk.py
mk_artifact.py exists in 2 places:
_wip/rb4_pre/mk_artifact.py
audiovibes/repair/pdf/mk_artifact.py
phaze_pages.py exists in 2 places:
_wip/rb4_pre/phaze_pages.py
audiovibes/repair/phaze_pages.py
phaze_part.py exists in 2 places:
_wip/rb4_pre/phaze_part.py
audiovibes/repair/phaze_part.py
pocket_part.py exists in 2 places:
_wip/rb4_pre/pocket_part.py
audiovibes/repair/pocket_part.py
repair_pages.py exists in 2 places:
_wip/rb4_pre/repair_pages.py
audiovibes/repair/repair_pages.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
2026-10-10 22:45 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 6 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
SCRIPT NAME COLLISION
addcover.py exists in 2 places:
_wip/rb4_pre/addcover.py
audiovibes/repair/pdf/addcover.py
build_pdfs.py exists in 2 places:
_wip/rb4_pre/build_pdfs.py
audiovibes/repair/pdf/build_pdfs.py
build_repair_book.py exists in 2 places:
_wip/rb4_pre/build_repair_book.py
audiovibes/repair/build_repair_book.py
build_two_part_draft.py exists in 2 places:
_wip/rb4_pre/build_two_part_draft.py
audiovibes/repair/build_two_part_draft.py
compare_part.py exists in 2 places:
_wip/rb4_pre/compare_part.py
audiovibes/repair/compare_part.py
fix_links.py exists in 2 places:
_wip/rb4_pre/fix_links.py
audiovibes/repair/pdf/fix_links.py
mk.py exists in 2 places:
_wip/rb4_pre/mk.py
audiovibes/repair/pdf/mk.py
mk_artifact.py exists in 2 places:
_wip/rb4_pre/mk_artifact.py
audiovibes/repair/pdf/mk_artifact.py
phaze_pages.py exists in 2 places:
_wip/rb4_pre/phaze_pages.py
audiovibes/repair/phaze_pages.py
phaze_part.py exists in 2 places:
_wip/rb4_pre/phaze_part.py
audiovibes/repair/phaze_part.py
pocket_part.py exists in 2 places:
_wip/rb4_pre/pocket_part.py
audiovibes/repair/pocket_part.py
repair_pages.py exists in 2 places:
_wip/rb4_pre/repair_pages.py
audiovibes/repair/repair_pages.py
Two scripts with one name are told apart only by which folder
you are standing in. Rename one and run this again.
VISION POINT · ruled by Brad, 11 Oct 2026 22:43 (P), Studio and Methodology desk
Canon, Milestone 0: "The client brings two reference songs, up to three. In the paid Milestone 0 session we run each one through AudioVibes and the other tools, so the client can see how different producers and engineers made different choices, and where their own song sits among them. Before Milestone 0 closes, the client picks one as the vision point. It goes behind a door at every compare from Milestone 4 to Milestone 7, unchanged."
- Minimum two references, so the client sees different producers' and engineers' choices.
- Milestone 0 is a paid session (credited to Milestone 1). The tool runs on the references are what it delivers, never a free demo.
- The only demonstration is in pre-sales: only when pressed, and only to someone who already understands most of what ABA does. No percentage is printed.
- The vision point is fixed from Milestone 0 to Milestone 7: same file, same level match. What the client liked against it is named once at Milestone 4 and checked at each later compare.
- A well-known reference behind a door is an open check, not a blind test.
Build: BACKLOG VISION-POINT (TruSync). Related: COMPARE-OPEN-SHUFFLE (ABA Compare).
2026-10-11 23:39 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 37 page(s)
4 FAILURE(S)
assets\carousel\index.html:5 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
assets\carousel\index.html:153 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
ledger\index.html:266 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
ledger\index.html:280 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
Nothing ships until these read clean.
2026-10-11 23:47 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 37 page(s)
4 FAILURE(S)
assets\carousel\index.html:5 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
assets\carousel\index.html:153 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
ledger\index.html:266 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
ledger\index.html:280 "AudioVibes AI" � retired name. Ruled 7 Oct 2026: the product is AudioVibes, "AI" dropped everywhere; 11 Oct 2026: ABA AudioVibes where the four tools appear together (AV-NOAI-SWEEP).
Nothing ships until these read clean.
Four levels of development (Brad, 12 Oct 2026 03:40)
1 New build (a new tool): most context and refinement, multi-session, Fable. 2 Integration (existing work into the free and paid books): one Fable task each. 3 Run the machine (campaign, scouts, leads, cultivation; his job becomes approving or editing proofs): Opus, built once to run on its own. 4 The room (OBS, cameras, shoots, sessions): his minutes, little of the Max plan (Marv's addition, not ruled). Week of 12 Oct: level 3 is the priority; OBS-SETUP is the critical path. Detail: BACKLOG WORK-LEVELS.
No raw output to a user (Brad, 12 Oct 2026 15:28, canon; ABA Phaze Check desk)
Information is never presented to a user in raw form unless it is JSON or set up for a specific use. Anything a user reads or downloads (a record, a saved session, an export) is formatted so a novice or a consumer can understand it. Found on the member page's "Download readings", which handed back the tools' plain text as a .txt file (fix: BACKLOG MEMBER-READABLE, P 15:30).
Milestone 8 doesn't rescue the mix. It performs it. (Brad, 13 Oct 2026 00:08, canon; Studio and Methodology desk)
Approved copy, word for word: "Milestone 8 doesn't rescue the mix. It performs it." Brad: "Canon ... that says it all." Use it wherever Milestone 8 is explained to a client: by Milestone 8 the performances, the spectrum and the automation are already right (Milestones 1-7), so the Conductor adds the energy arc and the final check, not a fix. Context and the expectation rule (never promise the size of the change): BACKLOG M8-EXPECTATION.
2026-10-13 10:32 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 38 page(s)
4 FAILURE(S)
shelf\index.html:116 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
shelf\index.html:118 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
shelf\index.html:119 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
shelf\index.html:121 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-10-13 10:35 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 38 page(s)
4 FAILURE(S)
shelf\index.html:116 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
shelf\index.html:118 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
shelf\index.html:119 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
shelf\index.html:121 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-10-13 10:36 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 38 page(s)
4 FAILURE(S)
shelf\index.html:116 "15 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
shelf\index.html:118 "15 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
shelf\index.html:119 "199 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
shelf\index.html:121 "199 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
Nothing ships until these read clean.
2026-10-13 10:37 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 38 page(s)
4 FAILURE(S)
shelf\index.html:116 "15 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
shelf\index.html:118 "15 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
shelf\index.html:119 "199 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
shelf\index.html:121 "199 bucks" � a price written as bucks is still a price. Only the Repair Book sale page may carry one (PRICE_PAGES).
Nothing ships until these read clean.
2026-10-13 12:28 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 39 page(s)
4 FAILURE(S)
toolbox\master-test\index.html:158 inline link to /audiovibes/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:238 inline link to /compare/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:243 inline link to /compare/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:273 inline link to /signin/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-13 12:35 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 39 page(s)
4 FAILURE(S)
toolbox\master-test\index.html:158 inline link to /audiovibes/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:238 inline link to /compare/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:243 inline link to /compare/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:273 inline link to /signin/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-13 12:36 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 39 page(s)
4 FAILURE(S)
toolbox\master-test\index.html:158 inline link to /audiovibes/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:238 inline link to /compare/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:243 inline link to /compare/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
toolbox\master-test\index.html:273 inline link to /signin/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-13 17:27 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 39 page(s)
1 FAILURE(S)
aba\index.html:820 inline link to /shelf/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-15 18:53 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 42 page(s)
13 FAILURE(S)
audiovibes\ebu\index.html:363 "headless" � no numbered statement covers the library, and S14 says no copy may describe a product's audio handling until one does.
audiovibes\ebu\index.html:394 "headless" � no numbered statement covers the library, and S14 says no copy may describe a product's audio handling until one does.
audiovibes\ebu\index.html:100 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:157 "programme" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:164 "programme" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:304 "programme" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:311 "programme" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:324 "Labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:328 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:335 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:342 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
audiovibes\ebu\index.html:380 inline link to https://tech.ebu.ch/publications/ebu_loudness_test_set � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
audiovibes\ebu\index.html:407 inline link to /audiovibes/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
No model switching (Brad, 15 Oct 2026 20:46, canon; ABA Pocket Check desk)
The model architecture is set and supersedes the 6-8 Oct model split. Each desk and each AI teammate carries its assigned model (MODEL-ASSIGN, 14 Oct 2026, from the pinned Claude Model Guide), chosen as the most efficient for that member and the least expensive for Brad. Marv takes the work and sends it to the teammate or model that fits (a teammate's model is the default; a desk can name another model for one job). Brad never switches models by hand, and no desk asks him to. Open: MODEL-ASSIGN-UPLOAD (the synced plugin in cloud sessions still reads model: inherit, so desks name the model on each dispatch until it is uploaded). UPDATE (Brad, 22 Oct 2026, AI Team desk): the team is seven. Putnam, the builder ("Bill the Builder", seated 20 Oct 2026), runs on Fable 5.1 for every build, render and wide edit. The others keep their defaults from MODEL-ASSIGN. Marv may override any teammate's default for one job when the job calls for it: mostly Fable or Opus, with Sonnet and Haiku open when they fit better. A general-purpose agent never takes the desk's model by default; Marv names its model on every hand-off (20 Oct 2026). Open: MODEL-ASSIGN-UPLOAD is now aba-studio-team-0.8.3.plugin.
No-delete ledger, erasable person (Brad, 16 Oct 2026 08:48, P; canon; ABA AudioVibes desk)
ABA keeps a ledger that is never broken: no missing IDs, no rewritten time. Nothing a member does is deleted from it. What a member can remove is removed from view: "Remove from my list" hides a reading from the member and from everyone, and the hiding is itself logged with its time. Personal details (email, name, file names) are kept apart from the ledger, tied to it only by the member ID, so a person can be erased on request without breaking the ledger: the details are wiped (or their per-person key destroyed), the ledger keeps the ID and time, and the erasure is logged as an event. Kept regardless: business records the law expects (invoices, billing, certified hours), and an erased person's address on the do-not-send list so they are never written to again. Why, his words in substance: "our entire architecture and our rule-based architecture requires a ledger that isn't broken; we don't have broken IDs, we don't have broken time." Marv's note: this is the pattern regulators accept for blockchain-style ledgers (personal data off the chain); not legal advice; the legal check confirms it for Canada and the UK.
Session, task, action (Brad, 16 Oct 2026 08:30-08:48, P; canon; ABA AudioVibes desk)
Words matter (his "service" whiteboard: six people, six meanings). SESSION: a span of time from opening to closing; a MEMBER SESSION is everything done while signed in; inside it, a TOOLBOX SESSION is the toolbox work, named by the tool when one tool is used ("a Compare") and "toolbox session" when more than one; other kinds of session will come as ABA offers more. Test: you can say when it started and ended. TASK: one piece of work with a goal and a result; a session holds one or more; the same word as the milestone tasks (estimate, actual hours, owner). Test: it has a goal and is done or not. ACTION: one single step by a person or the system (drop a file, press play, download, remove from my list); a task is made of actions; the ledger records actions, each with one ID and one time (the ledger's record of an action is an entry, an internal word). Beside them: a READING is the result of a tool task; a TAKE is a human performance; a PASS is one run through the mix in Milestone 8, step 2. Supersedes L-WORDS (6 Oct), which called one saved result a "session": it is now a reading.
Each tool's Beyond page is its feature map, built from BACKLOG (Brad, 16 Oct 2026 09:01, P; ABA Pocket Check desk)
A feature's status lives in one place: a FEATURE line in BACKLOG.md (tool, id, name, group, status, build, milestone, what you see, may say, risk, item). The Beyond page is built from those lines by py build_beyond_page.py <tool> and is never edited by hand, the way The Desks is built from the BOARD lines. The desk that ships or rules a feature changes its line in the same turn. Pocket Check first (39 lines, FEATURES-POCKET; the pinned "Beyond the Pocket"); Phaze Check, Compare and AudioVibes follow for uniformity (BEYOND-PAGES). The 8 Oct team read stays as pocket/BEYOND_THE_POCKET_2026-10-08.html.
2026-10-16 10:37 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 43 page(s)
4 FAILURE(S)
privacy\index.html:69 inline link to /rulebook/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
privacy\index.html:90 inline link to /email-stop/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
rulebook\index.html:361 "holds your email, your name or your file" � only S15's approved wording, quoted verbatim on /rulebook, may say this company holds, keeps, stores, retains, archives or preserves a client's material. Write it about ANYONE'S files, the way /session-assets already does, or do not open the subject.
rulebook\index.html:269 inline link to /privacy/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-16 10:39 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 43 page(s)
4 FAILURE(S)
privacy\index.html:69 inline link to /rulebook/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
privacy\index.html:90 inline link to /email-stop/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
rulebook\index.html:361 "holds your email, your name or your file" � only S15's approved wording, quoted verbatim on /rulebook, may say this company holds, keeps, stores, retains, archives or preserves a client's material. Write it about ANYONE'S files, the way /session-assets already does, or do not open the subject.
rulebook\index.html:269 inline link to /privacy/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-16 19:16 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 43 page(s)
4 FAILURE(S)
privacy\index.html:69 inline link to /rulebook/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
privacy\index.html:90 inline link to /email-stop/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
rulebook\index.html:361 "holds your email, your name or your file" � only S15's approved wording, quoted verbatim on /rulebook, may say this company holds, keeps, stores, retains, archives or preserves a client's material. Write it about ANYONE'S files, the way /session-assets already does, or do not open the subject.
rulebook\index.html:269 inline link to /privacy/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-17 00:22 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 44 page(s)
absolutes (report only, ABS-SWEEP): 435 unquoted, unruled
1 FAILURE(S)
signin\index.html:67 inline link to /privacy/ � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
Pro Tools and Reaper are adapters, not workplaces (Brad, 17 Oct 2026 09:58, canon; TruSync desk)
All ABA work is done in Fender Studio Pro. Brad pays for Pro Tools and holds a paid Reaper license, and says so publicly, for one reason: when a client's material depends on Pro Tools or Reaper, he can open it there, see what it does, and move it into Studio Pro. They are a bridge into Studio Pro, used only when needed; no recording, editing or mixing is done in them. The normal intake needs neither: a package of stems with the ingest form. In the rare case where something is specific to one of those DAWs (a session, a routing, a plugin's behavior), Brad opens it to read it, then either recreates it in Studio Pro or records that it cannot be recreated. Copy may say he holds both licenses "so sessions from Pro Tools and Reaper can be brought into Studio Pro"; it never says ABA works in either. Builds on the 28 Sep ruling that sessions arriving from Pro Tools or Reaper are migrated into Studio Pro. This covers Brad's own studio; whether another engineer could run the ABA method in Pro Tools is a separate question (PT-PORT, held). Added the same morning (Brad, 17 Oct 2026, canon): in practice the bridge should be a rare outlier, but in sales it matters a great deal, because "Pro Tools" are the two words a pro looks for first. So copy names it plainly and with respect: ABA holds a Pro Tools license and can take Pro Tools material in. It then explains why ABA works in Studio Pro on Studio Pro's own merits (the template, the stock tools and venues, the Conductor surface), never by comparison. Nothing ABA publishes says anything negative about Pro Tools, Reaper or any other DAW, or about the people who use them. A working Pro Tools engineer is ABA's proof of concept for the Pro Tools use case (PT-PORT).
A virtual media production studio; video is a special project, bid per client (Brad, 17 Oct 2026 ~10:40, ruled; TruSync desk)
ABA calls the studio "a virtual media production studio". "Virtual" is the whole integrated workflow, not the drawings: the bridges between the software applications and between the tasks of every milestone (the clock, the paperwork, the sign-offs, asset custody, every move from one task to the next), the work that takes a musician out of the creative space, which the virtual studio takes on so the room time stays creative. The drawn rooms are how that workflow is shown, and they are drawn from Brad's real studio: the Studio is his tracking room, the Control Room his portrait-screen DAW setup (drawn landscape for the screen), the Green Room the space between tasks; the real studio has no glass between two rooms, the drawing does. Copy never says "virtual" means only the drawn rooms (that makes it a cartoon again). It is made to be fun, and the hard work underneath it is real. Correction, same morning (Brad): the first filing said "virtual" covered the drawn rooms; he ruled that does the system an injustice. "Media" stands because the studio makes video as well as audio: Premiere is part of the studio, OBS and the studio cameras are in the session protocol, and ABA's own videos are already out. Video for a client is offered as a special project: raised in pre-sales and Milestone 0 (the intended-use question already lists Video / film and Broadcast, and the answer sets the loudness targets), kept in mind while the music is produced, and discussed and bid individually once the music exists. Nothing is built for it until a client asks (the rule: don't build what you might need later but don't need now). Helmholtz had graded "media" Disputed on the ground that ABA sells no priced video service; Brad's ruling answers that the phrase describes what the studio is and does, as the platform's own name already does.
Excel behind the curtain, not hidden (Brad, 17 Oct 2026, ruled; TruSync desk)
Excel is a supporting component ABA is glad to have: it is cheaper than building the same thing or paying for a service that does it. It is abstracted as far as possible from customer-facing UI and terminology: clients see the clock, the rooms and the production record (LANGUAGE_CANONICAL.md), never sheet names, macros or "workbook". The clock bridge is the one adapter between them, and logic keeps moving out of the workbook into the clock (rounding, billing order, the credit gate, the close order already have); the workbook keeps the record. It is never hidden: asked, ABA says the record is kept in Excel. The same principle as Pro Tools and Reaper, ruled the same morning: a supporting tool behind an adapter, never the face.
The milestone close: agree the work, sign, then pay (Brad, 17 Oct 2026 ~12:30, ruled; TruSync desk; supersedes the 4 Oct order)
- THE ORDER: the milestone clock stops → reconcile (overs and unders discussed, the figure agreed) → the signatures, in one sitting → the payment → the milestone is closed. Not closed until the payment is recorded; the next milestone never opens on an unclosed one. Supersedes 4 Oct 2026 ("payment comes before the signatures"); kept in MILESTONE_DOD.md for the record. Why, his words in substance: you agree on something before you pay for it; the signature authorizes the payment.
- WHAT A SIGN-OFF AGREES: first, that the milestone's definition of done and definition of success, as agreed at its opening read, are met; second, that the assets handed to the next milestone (or out the door, after Milestone 8) meet that milestone's ingest form as it was defined; then, therefore, the reconciled figure, and the payment is authorized. The money is payment for services rendered: you asked for something, we gave it to you, you agree we gave you what you asked for, and you pay for it.
- THE RECORD: every step of the close is timestamped and append-only (the no-delete ledger rule): the reconcile, each signature with the figure it agreed and the versions of the definition of done and the ingest form it signed against, and the payment with Stripe's own timestamp beside ours, so "paid after signed" is shown by a third party. Kept in the production record as well as the session file, for analysis across projects (Brad's OLAP: time from signature to payment, overruns by milestone, unders across projects).
- PROXIES: the signers and a proxy for each are named in the client's first agreement (Milestone 0, or pre-sales when the client enters through the Muse Parlor). No default proxy, ever. Signing by link, from anywhere, is allowed: the studio is virtual; a signature is an act, not a place.
- NO SIGNATURE, NO CLOSE: no window, no deemed acceptance. An unsigned milestone stops the project, because nothing moves until the milestone is closed.
- INFORMED SIGN-OFF: pre-sales and Milestone 0 say plainly what a sign-off is and what it locks, with a checkbox that it was explained. The signing screen is the same in the room or on a phone: the opening's definition of done and success line by line, the hand-off against the ingest form, the figure, the consequence in plain words, a typed name and an "I've reviewed this milestone and agree" box, and an honest "I'm not ready to sign" that sends it back with no penalty. The record keeps that the signer opened what they signed.
- WHEN A CLIENT CHANGES THEIR MIND LATER: never "but you signed". The answer is always positive: "Oh, really? What don't you like? Let's bid going back to Milestone N and get you what you want, and see what that costs." A signed milestone is reconciled, so going back is new work, estimated and billed. Usually the client keeps it as it is, and nobody is apologetic or defensive.
Build: CLOSE-ORDER-1017 on the board. Lawyer's look before the sign-off language goes into the client agreement. Reaffirmed by Brad, 25 Oct 2026: sign, then pay, is the right way to do it. The gate drawing still showed the 4 Oct order and was corrected the same day (GATE-CURRENT-1025). Reaffirmed by Brad, 29 Oct 2026, with both risks named: signing first guards against taking money for work the client has not accepted; the payment, not the signature, closes the milestone, so a signature with a failed payment releases nothing and moves nothing on. In his words: "signing is first, and then paying is what closes out the milestone and clears them to be able to have the assets." The signing screen says so in plain words (draft for grading): "Signing authorizes the payment. The milestone closes, and the work moves on, when the payment clears."
The moral compass is shaped together (Brad, 17 Oct 2026 ~14:00, canon; TruSync desk)
Brad is the only human on the ABA team, and the final say is his. But the moral compass is not his alone; it is shaped in the loop between him and the team. Helmholtz keeps it in line: every claim graded for truth, nothing printed that the evidence does not support. Ertegun reads how it lands in the world: the market, culture, politics, place. Fletcher is the catch-all: nothing is called done until it is proven, against the old code and against an independent check. Marv feeds back to Brad what is right and wrong in what he has just said, against canon and his own past rulings. Brad adjusts his thinking from that and carries the result out as the human interface to the customer-facing Human Universe (HU; the AI Universe is UI, AMP_Lexicon_Phrases.md). The context of each ruling, his stories and reasons included, is part of what shapes the compass, so it is kept with the ruling.
Updated 27 Oct 2026 (Brad's ruling): ABA now has two humans, the CEO and the CIO. The final say on rulings stays with the CEO.
Root beer is the official soft drink of the ABA Media Platform (Brad, 19 Oct 2026 15:15, P 19 Oct 2026 15:30; TruSync desk)
The Green Room fridge pours root beer, never beer: two of the four target audiences are likely under 21. "You've earned a beer" stays as the line; the bottle is a root beer, for everyone, with no age check. The celebratory root beer pops for a win; the session root beer is offered with no judgment. No brand name on the bottle. Supersedes GREEN_ROOM.md's 18 Oct 22:50 age split.
Qualify in pre-sales; turn down what can't succeed (Brad, 19 Oct 2026 18:22; TruSync desk)
It is all about qualifying the customer in pre-sales. A client who truly can't afford the work is turned down kindly and pointed toward how to bring their dream to life another way (the graceful no). His precedent: at DevTec he passed on contracts when the support, money, time and people to succeed weren't there, because a contract set up to fail is only another problem. ABA carries the same rule, mitigated far better by the fixed rate card, the known milestone prices and the one-milestone-ahead estimate.
2026-10-19 18:33 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 6 unquoted, unruled
1 FAILURE(S)
ledger\index.html:854 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-10-19 18:34 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 6 unquoted, unruled
1 FAILURE(S)
ledger\index.html:854 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-10-19 18:36 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 6 unquoted, unruled
1 FAILURE(S)
ledger\index.html:854 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-10-22 05:01 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
1 FAILURE(S)
audiovibes\repair-book\index.html:238 inline link to https://payhip.com/b/5zYBa � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
2026-10-22 05:01 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
1 FAILURE(S)
audiovibes\repair-book\index.html:238 inline link to https://payhip.com/b/5zYBa � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.
The measuring decisions, in one place (recorded 23 Oct 2026, from the code and canon; ABA Toolbox)
A check on 23 Oct 2026 found that an email sent on 22 Oct said the decisions behind the tools are published in this ledger, and that the ledger held no measuring-standards entry. This entry records the decisions that already stood in the code and in canon, each with where it lives; it adds no new one. LOUDNESS (ABA AudioVibes): integrated, short-term and momentary loudness computed to ITU-R BS.1770-4 with EBU R128 gating (the -70 LUFS absolute gate and the -10 LU relative gate); loudness range to EBU Tech 3342; channel weights per BS.1770-4 Table 1 since 15 Oct 2026 (until that build every channel weighed 1.0, which read the EBU 5.0 and 5.1 files, Tech 3341 test 6, 0.39 LU low). TRUE PEAK, ruled by Brad on 4 Oct 2026 (option b), as recorded in the engine: adopt the standard's own 4x oversampling filter, the 48-coefficient table of ITU-R BS.1770-4 Annex 2, re-run the tone table, and publish whatever it shows. Until build 2026-10-12.2 the filter was ABA's own Blackman-windowed sinc, which read high-frequency peaks up to about 0.3 dB high near 20 kHz (found 2 Oct 2026). The sample itself is included, so the reading is at or above the sample peak. THE CHECK: the browser engine's loudness must agree with an independent implementation, pyloudnorm, to within 0.05 LUFS, and the push gate refuses a build that does not. THE WORDING, ruled 15 Oct 2026: the numbers are "computed to" the standards; never "compliant", "certified" or "conforms". THE TEST SET, verified 15 Oct 2026: ABA AudioVibes, build 2026-10-15.1, computed to and passes the EBU Tech 3341/3342 minimum-requirements test set (v05), 29 of 29; the statement covers the AudioVibes engine only, and the EBU says passing these tests does not establish conformance. ABA'S OWN MEASUREMENTS, with no standard behind them: stereo correlation (the Pearson correlation of left and right), spectral tilt (a straight line fitted to the octave levels, in dB per octave), clipping (runs of three or more samples in a row at or within about 0.05 dB of full scale), DC offset (the average departure from zero). ABA PHAZE CHECK: the delay of one source against a reference is found by generalized cross-correlation with the phase transform (GCC-PHAT, Knapp and Carter 1976), band-limited to 40 Hz to 12 kHz, to a fraction of a sample by parabolic interpolation; three readings across the take, the median is the answer. No standard applies to alignment. ABA COMPARE: each version's loudness is BS.1770-4 integrated loudness over the stretch it shares with the baseline, with the same gating and channel weights as the engine; the line-up uses Phaze Check's GCC-PHAT. Compare is a prototype, checked on generated mixes, not yet run on a real session, and it has not been run against the EBU set. ABA POCKET CHECK: two rules of thumb, declared as such and not a model of hearing: a part is present within 40 dB of its own loudest moment, and two parts share a band when they are within 6 dB of each other. The EBU runner and engine files are sent on request; the repository is private. Sources: engine.js (header; the true-peak ruling in the Annex 2 comment; the channel-weight note; measureStereo, measureSpectrum, measureDefects); tests/test_engine_agreement.py (LUFS_TOL = 0.05); LANGUAGE_CANONICAL.md ("Standards are computed to", 15 Oct 2026; "The EBU result, worded exactly", 15 Oct 2026); the public page /audiovibes/ebu; phaze/core.js; compare/core.js; pocket/core.js (activeDb 40, shareDb 6) and the public page /pocket-check.
2026-10-23 13:58 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
2 FAILURE(S)
audiovibes\index.html:215 "gating" � a customer page says door for gate and check for rule (door/key ruling, 17 Oct 2026; CUSTOMER_PAGES in preflight_site.py).
compare\index.html:141 "gating" � a customer page says door for gate and check for rule (door/key ruling, 17 Oct 2026; CUSTOMER_PAGES in preflight_site.py).
Nothing ships until these read clean.
2026-10-24 01:53 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
1 FAILURE(S)
keyboard\tool\index.html:101 "colour" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-24 02:54 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
2 FAILURE(S)
keyboard\tool\index.html:1492 "nothing is sent" � false, and it is the exact claim S3 exists to correct.
keyboard\tool\index.html:171 "headless" � no numbered statement covers the library, and S14 says no copy may describe a product's audio handling until one does.
Nothing ships until these read clean.
2026-10-24 02:54 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
2 FAILURE(S)
keyboard\tool\index.html:1492 "nothing is sent" � false, and it is the exact claim S3 exists to correct.
keyboard\tool\index.html:171 "headless" � no numbered statement covers the library, and S14 says no copy may describe a product's audio handling until one does.
Nothing ships until these read clean.
Shape prices from the certified hours (Brad, 25 Oct 2026, confirmed; TruSync desk)
Brad's once-over of the certified hours on 24 Oct 2026 moved a few of them, and on 25 Oct he confirmed that the public prices follow the hours: costs went up, and the extra on The Bed stays until they come down. The rule under it is the one of 20 Oct: the certified hours are the source of the prices, one person at one hourly rate, the playing included; Milestone 0 is a fixed bid, credited once toward Milestone 1. The price sheet shows the value of the work, then the kickoff credit, then what you pay. trusync/shape_prices.py computes every shape from the certified hours file and refuses to price a shape with a task in scope that has no certified hours. The top shape, Full production, came in under the two thousand dollars Brad set as the aim. The figures, as shape_prices.py prints them from the two estimates files (20 Oct, then 24 Oct):
Shape was (20 Oct hours) now: value credit you pay
The Bed (M0, M1, M8) $640.25 (M1 $341.25, M8 $65.00; paid $406.25) $656.50 - $234.00 $422.50
Solo singer + guitars $1,127.75 $997.75 - $234.00 $763.75
Power trio + vocal $1,290.25 $1,111.50 - $234.00 $877.50
Full band with keys $1,517.75 $1,274.00 - $234.00 $1,040.00
Full production $2,574.00 $1,956.50 - $234.00 $1,722.50
The Bed by milestone: M0 $234.00 fixed; M1 5.0 h $325.00 (was 5.25 h, $341.25; due after the credit $91.00);
M8 1.5 h $97.50 (was 1.0 h, $65.00). Milestone 8 Light stays $32.50; the Muse Chart Room stays $292.50 / $130.00 / $162.50.
Where the figures live: the price sheet (/aba/price-sheet), the launch pad and the Demo Desk (computed from the file), trusync/MILESTONE_DOD.md (the ruling of 25 Oct, superseding item 4 of 20 Oct).
The full Milestone 8 is one hour (Brad, 27 Oct 2026; TruSync desk)
Brad reached the price sheet from the home film and flagged Milestone 8: the full pass is one hour, and Milestone 8 Light is half of that. The half hours on two of its rows in the 24 Oct once-over were a mis-tap on the iPad. The certified hours were corrected at the source and every price that comes from them moved with it: every shape is lower than the table above by the same half hour at the rate.
The full Milestone 8: 1.0 h, $65.00 (was 1.5 h, $97.50). Every shape is $32.50 lower.
Shape was (25 Oct) now: value credit you pay
The Bed (M0, M1, M8) $656.50 (paid $422.50) $624.00 - $234.00 $390.00
Solo singer + guitars $997.75 (paid $763.75) $965.25 - $234.00 $731.25
Power trio + vocal $1,111.50 (paid $877.50) $1,079.00 - $234.00 $845.00
Full band with keys $1,274.00 (paid $1,040.00) $1,241.50 - $234.00 $1,007.50
Full production $1,956.50 (paid $1,722.50) $1,924.00 - $234.00 $1,690.00
The Bed by milestone: M0 $234.00 fixed; M1 5.0 h $325.00 (due after the credit $91.00); M8 1.0 h $65.00 (was 1.5 h, $97.50).
Milestone 8 Light stays $32.50 and now also shows beside the full pass on the price sheet; the Muse Chart Room stays $292.50 / $130.00 / $162.50.
Everything new is made from the current templates (Brad, 29 Oct 2026; TruSync desk)
Brad: every workbook and every template we make from should be current, and nothing should still be made from the 1 September material. The rule:
- A new song is always a copy of the current studio template, Studio Pro's "ABA Template" (saved by Brad on 28 Oct 2026), through
TEMPLATE in trusync/custody.py. Nothing new is made from an older song or template.
- A new production record is always a copy of one of the current shape templates in
trusync/workbooks/shapes/, never of an older record.
- When a template changes, the pointer moves the same day. Any song or record made from the old one and never opened is remade from the new one; the old copy goes to the attic, never deleted (Opus 1001's song, 29 Oct 2026).
- A record already in use is not swapped. It is brought current by its routed fix (the v3.1 VBA paste, for instance).
- Opus 753 stays as it is: it is the worked example, not a template.
- "The old sandbox" means only that
Sandbox Project.song (1 Sep 2026) is no longer used as a starting template. Brad's 00-Sandbox Project folder itself is kept exactly as it is: it is where Loose Ends was made, with its raw tracks and bounces, and the samples come from its Milestone 7 release. Nothing reads it to make new work, and nothing writes, moves or deletes it.
tests/trusync/test_templates_current.py fails if the pointer names anything but the current template, or if an in-house song was made from anything else.
The Muse Chart Room takes any creative session (Brad, 30 Oct 2026; TruSync desk)
The Muse Chart Room is not built for one kind of work. Brad: "It's exactly the opposite." It began as the room for the Golden Bridge consultation on a writer's song; it now takes any kind of creative session, not only composition. Its signature session is the Composition Room (once the Writer's Room), the composition creative session that the Golden Bridge from The Muse leads to: composition, arrangement, and preparation for recording, which part two records. That is one use of the room, not its definition. Anything that describes the room, the films and the public page included, says so.
Andrew joins the team as spokesperson (Brad, 30 Oct 2026; TruSync desk)
Brad: "Shouldn't we formally add Andrew to our team? He's our spokesperson. He should be associated with sales and marketing. I think he's earned his place on the team, and he should get credit." Andrew, the ABA voice (Microsoft's natural voice, picked by Brad on 27 Oct 2026), is now a seat on the org chart: Spokesperson, with Sales and Marketing, the voice of every ABA film and audio summary. He speaks for the studio, never as the CEO. Films credit him as Andrew.
The rooms, and what each is for (Brad, 30 Oct 2026; TruSync desk)
- The Den is built for conversation among the client, the producer and the engineer: three mics, an environment designed for the three of them talking. The talks aren't private, but the room is made for them. Every sign-off happens in the Den (Brad, confirmed the same day: "every time we go to sign off, we go to the den. Absolutely.").
- The Muse Chart Room is where the creativity is: the composition creative session (composition, arrangement, and preparation for recording, for part two of the Composition Room, the Golden Bridge from The Muse) and any other creative session. It holds every other kind of conversation, including the opening of each milestone with a client part: Milestones 1, 5 and 7, the talent milestones. It takes any creative session (the ruling above).
- The Lab is where the scientific work is done: measurement and checks with the ABA Toolbox. Its findings are fed back into the Muse Chart Room.
- The Studio and the Control Room are where the performances are created.
- The Stage, ABA Venues, is where the performances are played, in the venues.
Three ABA productions; the rest of the catalog is the reason (Brad, 30 Oct 2026; TruSync desk)
Brad: the films use songs from his catalog, and some of them, like Guiding Light, date back to 1983. Any "that doesn't sound as good" or "that doesn't fit ABA" is the point: "All those recordings that were less than when I made them, and with what tools I had to make them with, and wisdom, is the reason I put all this together." ABA is "a solution to the problem rather than a Band-Aid on the problem."
- Only three records are ABA productions: Cosmic Honey, Forbidden Journey and Loose Ends, the three at Milestone 7. Everything else in the catalog was made before ABA, with the tools and the knowledge of its day.
- The three were made in the spirit of TruSync, not the letter of it (Brad, 31 Oct 2026). By design none of them has gone into Milestone 8: "That's the whole point of the evolution." They are where the vision showed itself; the tools, the studio and the process were built to document that work and bring its full capability to light. Nothing should say they went through every milestone or a Den sign-off. What still stands between them and a legitimate Milestone 8 is the venues: "The venues is huge for Milestone 8. I have to get those solidified before I can actually do legitimate Milestone 8."
- Any listenable song from the catalog may still be used as a demo (performance, melody, whatever the job), because all of it went into what ABA is.
- Wherever a recording is shown or used as a score, it is labeled for what it is: an ABA production, or from the catalog, with its year where it is known (the albums gather work from over 30 years, Brad, 30 Oct 2026). An older recording is never passed off as ABA work, and never apologized for. It is the before.
- The claim behind it ("much higher quality with the same amount of work, or less") is Brad's own observation until it is measured, and it is worded that way. Helmholtz grades it before it goes public.
- A catalog recording that has been through the ABA tools may say so ("from the catalog, 1983, brought up with the ABA Toolbox"). It is still not an ABA production. Brad, 30 Oct 2026: a 1983 cassette recording of Guiding Light rose from about 83 to about 94 in AudioVibes (his recollection, not exact). The rating is abstract, but it shows the tools and the method can make older material much more listenable on streaming or in any venue. (The 29 is the EBU test set the AudioVibes meter itself passes, 15 Oct 2026, not 29 checks on the song. Neither figure is quoted until the saved analyses are found.)
- Milestone 8 is still being developed (Light and Regular); nothing here changes it.
Fix it at stage one (Brad, 30 Oct 2026; TruSync desk)
Brad's rule, from the space program and design practice: a problem caught early costs pennies (a diode, a screw, a fastener) and nobody gets hurt; caught midstream it costs far more, in overruns and testing, and risks harm; let it slip to the third stage and the ship explodes. So a problem with LOW odds but LARGE consequences is fixed now, while it costs a screw, not when it is found at a client's close, and never at the third stage. The decision rests on odds times consequence, not on the odds alone. It is the build-side twin of his 29 Oct ruling that no problem that has to be fixed is carried past a milestone. Worked example, 30 Oct 2026: the custody check's file lock could leak if a write failed at one exact moment (rare, but this PC's Excel and Dropbox both do fail that way). Fixed before the check ships, each fix proven by injecting the failure; Fletcher keeps testing until his verdict comes back clean.
Red first: every gate fails before it passes (Brad, 30 Oct 2026; TruSync desk)
The method under "Fix it at stage one", from Brad's years teaching test-driven development: build every gate failing first, "make sure that you can close the gate and then write the happy path, but make sure that you consider any way that that gate can be breached and have those as your test cases." In order: (1) write the test that proves the gate closes, and show it fails against the code as it stands (a test that passes on broken code proves nothing); (2) make it pass; (3) attack it, every way it could be breached, each breach a new failing test before its fix, until the independent verdict is "none disputed". His experience is that it takes less time, not more. The same shape runs through the milestones: the definition of done is written at the opening read, before the work (the failing test); the close refuses until it is met; the signatures confirm it. Worked example, 29 to 30 Oct 2026: the custody check at milestone close, 12 tests failing first, then five rounds of Fletcher's attacks, 48 tests, last verdict "DISPUTED: none. The check stands." In the making-of (MAKING_OF.md, 30 Oct) and marked for the making-of film.
2026-10-25 02:04 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 46 page(s)
absolutes (report only, ABS-SWEEP): 11 unquoted, unruled
37 FAILURE(S)
ledger\index.html:953 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:953 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:953 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:958 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:959 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:959 "$4" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:959 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:959 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:960 "$4" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:960 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:960 "$9" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:960 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:960 "$7" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:961 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:962 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:964 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:966 "$8" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:966 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:966 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:966 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:966 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:968 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:968 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:970 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:970 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$3" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$3" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$9" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$3" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:971 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:972 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:972 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:972 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:972 "$1" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:973 "$2" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-10-30 21:52 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 47 page(s)
absolutes (report only, ABS-SWEEP): 22 unquoted, unruled
2 FAILURE(S)
ledger\index.html:689 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
ledger\index.html:689 "apologised" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-30 21:52 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 47 page(s)
absolutes (report only, ABS-SWEEP): 22 unquoted, unruled
2 FAILURE(S)
ledger\index.html:689 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
ledger\index.html:689 "apologised" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
2026-10-30 21:54 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 47 page(s)
absolutes (report only, ABS-SWEEP): 22 unquoted, unruled
2 FAILURE(S)
ledger\index.html:689 "labelled" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
ledger\index.html:689 "apologised" � British spelling. This site writes US English (register_check.py; exceptions in register_allow.txt).
Nothing ships until these read clean.
The client's room is part of the studio: one process, three kinds of session (Brad, 31 Oct 2026; TruSync desk)
Brad: "the process is the ABA process." A client working from their own room follows the same milestones as anyone else; only how live the link can be changes.
- Talking sessions (pre-sales, Milestone 0, the Muse Chart Room's part one): a plain video call, like any conference call, run through OBS. Distance does not matter.
- Recording sessions, the client playing: the client works against the mix that milestone has, a static rhythm mix at the beginning, then a dynamic rhythm mix, as in the ABA flow. How live it can be depends on the distance of the client: close enough, near real time; too far, the mix and the stems are exchanged once recorded. The 12 Oct research measured about 37 ms to Seattle and 36 ms to New York (round trip, Denver); playing together holds to about 25 ms one way, and the calling tools add their own delay, so near real time is tested case by case and is not offered internationally.
- Engineering sessions, the client not in the room but never out of reach. No quote-and-disappear: questions go to the client as they come up, by the weight of the question. A question that stops the work or changes the song: a video call the same day, a talk task on the record. A question that needs an answer, not a conversation: a text or message with the options laid out. And when a task has changed enough to be heard, the client gets a link to hear it; they don't wait until the end to hear the work (Brad: "They don't have to wait till the end to hear it."). With it go the readings from the tool tasks (the ABA Toolbox measurements taken on that work), so the client sees what was measured as well as hearing what changed (Brad, the same day: "Also send in the readings for the tool tasks."). Every answer is written into the production record; the engineer flags, the producer picks the channel.
- Open: whether a call during an engineering task runs on the clock as a talk task or folds into the engineering hours.
The Screening Room, and the Muse Chart Room for private lessons (Brad, 31 Oct 2026; TruSync desk)
- The Screening Room is a new room in the virtual studio: the ABA video library as a theater. A lobby with a marquee and one poster per video (finished ones lit, the rest dimmed until they are ready), and an auditorium that dims before each showing. The first door anyone walks through is the feature presentation, three videos back to back: Your room, our studio; ABA, the virtual studio; the Muse Chart Room. After that the lobby is open and the visitor picks. It answers how to present the library without burning anyone out: no schedule to push, the visitor chooses. Brad: "Screening room is something about that just clicked."
- "Movie" in this room only. The CIO's ruling (videos, not movies or films, 30 Oct) stands for each video. Brad, 31 Oct: a set of videos shown together in a theater "now meets his requirements for what a movie is", so the room may speak of showings, the feature and the theater.
- The Muse Chart Room also takes private lessons. Brad is looking for a protégé, and the room is where he would teach music theory, harmony and the rest of what he has used to write songs: "how the math, without showing them the math, can really help the creativity." Under it, his line: learn the rules before you break the rules; it's okay to break the rules if you know the rules. (A Wisdom Pearl candidate; its number is the Language and Protocol desk's to assign.)
- Milestone 0 and part one of the Muse Chart Room are recorded, by agreement (Brad, 31 Oct 2026): "we agree for the recording for Milestone 0, because that's the trust but verify part of our protocol", and then "also in part one in the Chart Room". The client agrees to both up front; other sessions are recorded only with the client's yes. What the recording is for (Brad, the same evening): "to stimulate excitement, relieve any kind of tension from objections that haven't been dealt with, and to put a plan in motion that they believe can be successful. Then we have to bring that vision to life." Trust but verify is the safeguard; the purpose is a shared, believed plan that both sides can go back to.
- Help when you need it (Brad, 1 Nov 2026): the theater is part of the virtual studio, so that anyone "not sure of what a next task is or how it is being done" can choose to watch the video for it, "and its prerequisite videos". Each room offers the next task's movie, its prerequisites first and the task's own video last, with chapter cards between; nothing plays unless the visitor chooses it.
- The clock stops while you watch (Brad, 1 Nov 2026: "I agree that we stop the clock"). Watching how a step works is never on the session clock.
- The Loft gets its own poster in the lobby (Brad, 1 Nov 2026).
A video is one; a film is a set, and Andrew gets the credit (Brad, 1 Nov 2026; TruSync desk)
- One is a video. Brad, 1 Nov 2026: "The videos are videos. The films are videos put together. So like when we have the 3 together, that's a film. Two together is a film. One is a video." A single ABA video is always a video (the CIO's ruling of 30 Oct stands for it); a set played together, the Screening Room's "movie", may also be called a film.
- Andrew is on the team page, with full credit (Brad, 1 Nov 2026: "Andrew's my man. So, he gets full credit here."). Andrew is the narrator voice of every ABA video, credited honestly as a computer voice, never presented as a person.
- Muse Parlor becomes the Muse Chart Room everywhere (Brad, 1 Nov 2026: "Uniformity will prevail.").
"Muse Pod" retired (Brad, 1 Nov 2026; TruSync desk)
- One room, one name: the Muse Chart Room (Brad, 1 Nov 2026: "we retire MusePod"). The Chart Room's creative-talk mode stays, with its "Bring your ideas" plaque, but the room never changes its name. Supersedes the 20 Oct 2026 "the Chart Room's other name". The sweep (room page, clock_bridge, the demo desk, the certification book) follows once tonight's builds on those files finish.
Not the printer and the ink (Brad, 1 Nov 2026; TruSync desk)
- The printer-and-ink model is the pain, not the plan. Brad, 1 Nov 2026: a cheap printer, cartridges that cost more than it did, and a printer that stops working right after a few of them, so you buy another and keep paying. "I don't want to have that as anything that we are subscribing to."
- Inside the team, "printer and cups" is shorthand for what a client may want again after a production. Outside, it is only ever framed as the pain ABA does not do: nothing disposable, nothing that stops working so the next purchase is forced, and every recurring offer worth buying on its own and chosen again each time, never renewed by silence. Milestone 8 hands everything over for good.
- The model is the razor that works and good blades (Brad, 1 Nov 2026: "at least there you get a razor that works and new blades. And that's what I want to see."). The production is a razor that keeps working; what a client buys again (the next song, and later the vault once ruled) is a fresh blade they want, never a replacement forced by something that broke.
The sign-off: two ways out, and the producer's job in each (Brad, 31 Oct 2026; TruSync desk)
Every sign-off is binary: the client continues (the next session, task or milestone), or exits through the checkpoint to Milestone 8 Light at the price already agreed. Brad: "Our responsibility at sign-off, our being the producer and the engineer, is to prop up and stimulate the excitement of the session when they go forward. If they're going to leave, we just make sure that it's an amicable and happy separation. If they're going to continue, we need to map their excitement to the money that they're paying at that time, so that when they move to the next milestone, they have a precedent of how it's going to end."
- Continuing: play the before and after first (the listening link and the readings); name the progress in the client's own words; sign and pay inside that moment; one line on what the next milestone adds. Every close ends the same way, so the next one has a precedent.
- Leaving: the Golden Bridge in full: credit for their part, their result through Milestone 8 Light, the door open, the friendship first.
- The guardrail: the excitement is earned and shown, never pumped. The hours in red sit on the same screen as the playback, and the client's freedom to leave at any checkpoint is what makes the excitement believable.
The Masters' Table, in the Loft (Brad, 1 Nov 2026; TruSync desk)
Brad's mentoring of experienced guitarists, chosen by interview (players who already read music and know more than the basics of theory), is called the Masters' Table: expert to master, not apprentice and not a classroom. Brad: "Apprentice to me sounds too low for the level I'm looking for. It's almost like expert to master." The work: music theory, composition, modes, arranging, the power of the triads. Names set aside: the Woodshed (the word's history includes punishment, against the house's kind-idioms rule), the Atelier (apprentice reads too low), Master Class (a commercial brand's name). It is a pod of its own (Brad, the same night): "a variation of a theme. Our pods are so incredibly cool. Having another one can't hurt. And it's like a studio would really be set up." The pod is the Loft (Brad, 1 Nov 2026, the same night): the room is the Loft, and the Masters' Table is what happens at the table inside it. Brad on the split: "I like the way you mix the two. That works." Its neon reads "The Loft", the one room whose sign keeps its "The" (Brad, 1 Nov 2026: "this might be one of the times where we need a the in front of it"). Other names set aside for the room: the Shed (Brad: too close to being taken out to the shed for a whipping), After Hours, the Back Room, the Proving Ground. The Muse Chart Room keeps private lessons for those who are not yet at the table. Brad on the rooms as a whole: Screen Music's rooms, put into one well-organized, well-designed studio, "would have looked very much like this."
Two links in everything: the door, and the theater (Brad, 2 Nov 2026; TruSync desk)
Every outreach piece (an email, a post, a text after a call, the leave-behind) carries two links: the one that goes where that piece is meant to send people, and a second into the Screening Room's front door at abamediaplatform.com/theater, so a reader who would rather watch first can. Brad: "we put two links in the emails. We put a link that would normally go to wherever we want that link to go, to the page or whatever door that we want, but there should be a link there for the theater. So if people want to watch the videos to get an idea, we can push that in the marketing." The theater is marketed as an entry door in its own right (Brad: "That would be an outstanding place to hit").
In the theater, the portfolio video has its own poster, placed before "How a production starts" so a visitor sees what they take home before how a production begins (Brad, 2 Nov 2026: "someplace where they first see it"), and it joins AMP and the Den in the picks after the feature.
Approve the content, not the distribution (Brad, 2 Nov 2026; TruSync desk)
The automated campaign runs on content Brad has approved once; he does not approve each send or each post. Brad: "if I have to approve everything, it defeats the purpose of having an automated marketing campaign." And the balance: "I don't mind approving emails on things that the scouts bring back, cold emails. I don't mind doing cold calls ... But I want to have something in play that ... requires the smallest amount of my approval once I've approved the content. I don't necessarily have to approve its distribution method. I have to approve the content. And I can do that before the distribution process." So: one-to-one pieces (a scout's lead, a cold email, a call) stay Brad's to approve and send; one-to-many pieces (posts, LinkedIn, the recurring emails) are approved as content in a batch, then distributed on schedule without a further yes.
Three audiences, each with its own content and its own doors, and the theater as the second link in every piece: the technologists (the architecture, how the team is educated, the team); music and multimedia people (the virtual recording studio); colleges and universities (the follow-up to the college campaign, to get the one-hour session in). Brad on the night's discipline: "This is the definition of success. Not the definition of done, because I haven't done it yet."
One generation of backups ships, with a size gate (Brad, 2 Nov 2026; TruSync desk)
Every desk backs a file up into _wip before editing it. Nothing expired and every ship committed them all: by 2 Nov 2026 git carried about 606 MB of backups, mostly older copies of the same few files. Brad's little voice asked whether the backups had a time to live; they did not. His ruling: "we should have at least one generation of backups that we ship, but we shouldn't be shipping 827 megabytes." So: tools/tidy_wip.py runs at the start of every ship, leaves the newest backup of each file in place, and removes older ones only when git already has that exact copy; backups that can be rebuilt from their sources (video play pages, PDFs, ebooks, pictures, archives) stay out of git and leave the disk after 30 days; workbook backups are never touched. And a size gate: ship.py shows what each ship carries and stops above 100 MB until Brad types big, so growth is seen before it lands, not when a disk or the host fills.
What a task records is fixed when the task closes; the book takes dated notes under it (Brad, 3 Nov 2026; TruSync desk)
Brad asked whether the portfolio is read-only or can take notes and edits. Ruled: what is entered at a task stays editable while that task is on the clock and is fixed when the task closes; after that it is never rewritten. Anything later, more information, a correction or a new topic, is added underneath as a note with its own date, from the book or the room, saved through the clock to the production record. Brad: "the information that was put in at the task is immutable." On when it locks: "When the task closes." A correction is a note under the original: the entry stays as recorded. The book stays a view of the record; it never rewrites an entry.
The source shape: what the client tells us early, what the engineer commits to, built at the start of the milestone (Brad, 3 Nov 2026; TruSync desk)
A source shape is the set of tracks one performance is recorded on: for the guitar today three (the Ox Box stereo and two monos), four, or all seven with double amp and double mic; the bass, one mono and one stereo; the drums, the kits with or without the percussion set; the arrangement parts each have their own, mono, stereo, or a blend such as a string quartet. The same shape is repeated in every slot of a performance section, and after the sonic enhancement those tracks are either used or deleted.
- Pre-sales gathers as much as it can, to fill the portfolio: the instrumentation, whether the song wants percussion, and how far the arrangement reaches (horns, strings, pads, sequences, loops, backing singers, solos).
- Milestone 0, or part one of the Muse Chart Room, goes over it with the client and adds to it. The client talks about what is in the song, never about track counts. The pros and cons of each shape are a producer and engineer conversation, in-house.
- The engineer decides, and commits to the shape there, so it is in the Milestone 1 estimate the engineer's hours promise (the estimate is made at Milestone 0, 3 Oct and 28 Sep).
- At the start of Milestone 1, or part two of the Muse Chart Room, the engineer builds the shape into the session: a copy and paste of under a minute, on or off the clock, with no line of its own on the bill. Nothing is built before then: there is no commitment to Milestone 1 until Milestone 0 closes.
- Milestones 5 and 7 confirm the shapes of their own parts at their opening reads.
The term: "source shape" is the recording layout; "ingest shape" stays what one milestone hands to the next.
A part the client drops comes off the bill, and the record says so (Brad, 3 Nov 2026; TruSync desk)
The bill is the clock, never the estimate: a milestone's money is the hours worked on its tasks at the rate. So when a client decides in Milestone 5 or 7 that a part planned at the estimate is not wanted (the horns, a synth pad, the backing singers, a solo), that task comes out of scope, its estimate goes to zero, and it costs nothing. Brad's words: only pay for what you've done.
- The best moment is the milestone's opening read, when what is really in is confirmed; it works mid-milestone too.
- Nothing disappears quietly. Every dropped part leaves a dated note on the record, who asked and when, with the hours it carried at the estimate, under the same rule as the entry above: what a task records is fixed, and the book takes dated notes under it. The dropped parts show in the client's portfolio.
- A dropped part can come back later as its own bid, the same as any change of mind ("Let's bid going back to Milestone N", 17 Oct).
Brad is on camera now, and the videos show the real studio at work (Brad, 3 Nov 2026; TruSync desk)
This replaces the 27 Oct ruling that kept Brad off camera. In his words: "start to be a face of the product. I don't have a problem with that."
- The reason is the screen. ABA sells an interactive process, and a video that shows the rooms without showing the live screen at work is asking the viewer to take it on trust. The screen has to be seen reacting to the room: the engineer cues, the performer answers, the session clock and the take move together.
- The footage is real sessions. The Black Salt production is being made in the studio now, through the TruSync process and Fender Studio Pro, and recorded through OBS, so the same work proves the tools, the studio and the process at once.
- Every road runs through OBS: the live screen in the rooms and the footage for the videos both wait on the OBS setup.
- Videos already released stay as they are until their re-cut is ready.
Click and play: TruSync runs without typing, and the client's own words go into their documents (Brad, 3 Nov 2026; TruSync desk)
Running TruSync should take no special skill. In Brad's words, it should be runnable "by a smart monkey. Not the creative parts of it, but just what has to be done to run TruSync", with custody, Performance Credits and billing always correct. The creative part is navigating it creatively.
- Nothing is typed that can be anticipated. A pull-down, a quick pick, a prefilled value or the mic comes first; typing stays possible but is never required.
- Every task carries its context and its content (the song-log line), and recording it should be one click or one spoken sentence: "Click, yeah, we just did a killer track. Click."
- The mic and its dictation glossary (the mishearings put right) work on every entry in every room. It matters most at Chart Room part one, Milestone 0, each milestone's opening read, and the wrap-up, so the client's own words go into the documents they receive.
- It is everyone's words, not only the client's: the client, the producer, the engineer, whoever is speaking, each entry named and dated. They go into the portfolio and into Custody. Brad: "this is checks and balances." The client is told at Milestone 0 that spoken entries are written into the record; the mic listens only while its button is on.
- The Call Card of 2 Nov is the live call script (Brad, 4 Nov 2026); the Pre-sales Kit's call section is reference.
- "Golden Bridge" is a generic term (Brad, 4 Nov 2026): the way across from where someone is to the right next place, before that place is named. Leaving pre-sales through a Golden Bridge means deciding whether its far end is Milestone 0, part one of the Muse Chart Room, or possibly Sonic Enhancement; those ends are not all defined yet. The graceful out when someone steps back is a Golden Bridge too.
- Pre-sales comes first: there is no Milestone 0 without a customer. On a pre-sales call the prospect is told at the start that their words are being written down, in a line graded by Helmholtz before use, and those words carry forward so they never have to repeat them.
- It should be easy enough that someone says "wow, I wouldn't have thought of that", and the data that comes out of it is worth showing: not just collected, mined.
- Nothing is shown in a demo that has not been rehearsed end to end on a demo copy that week. A demo that drops into fix-it mode is the worst failure there is.
2026-11-02 06:40 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 48 page(s)
absolutes (report only, ABS-SWEEP): 26 unquoted, unruled
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.html 844 lines, yellow at 1000, red at 1500: green
1 FAILURE(S)
ledger\index.html:1120 "holds that exact copy; backups that can be rebuilt from their sources" � only S15's approved wording, quoted verbatim on /rulebook, may say this company holds, keeps, stores, retains, archives or preserves a client's material. Write it about ANYONE'S files, the way /session-assets already does, or do not open the subject.
Nothing ships until these read clean.
The performance beats the perfect hit (Brad, 4 Nov 2026; TruSync desk)
Brad's philosophy of performance and production, put on the record: a mistake is not always a mistake, and a good performance is never killed because one hit didn't line up.
The worked example is his own. The lead guitar solo on PCH Dreamin' is one take: the first time he played it, the first time he heard it, the first pass. In one section he is noticeably late on a hit. He decided that the performance to the track was worth far more than fixing that one hit, and he knew a day would come when he'd want to explain why.
In his words: "I'm not going to kill a good performance because it didn't line up perfectly or my Marv told me that I was late 27 samples on my performance. I love that somebody can tell me that. But I'm going to be late. I'm going to be early. I'm going to be on time because I'm not a robot yet."
- The tools measure, and it's good to know: a timing reading, a phase offset, a level. The measurement informs the decision; it never makes it. The producer decides what stays.
- Timing between machines (a fixed latency, like the TD-27's 3.5 ms against SSD) is corrected, because it is a fault of the rig, not a choice of the player. Timing in a human performance is the performance, and it is kept unless the producer chooses otherwise.
- The team's job includes telling Brad when the work gets too robotic, or when the mad scientist goes too far.
2026-11-04 01:51 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
Traceback (most recent call last):
File "C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\amp-site\preflight_site.py", line 736, in <module>
sys.exit(main())
~~~~^^
File "C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\amp-site\preflight_site.py", line 518, in main
text = page.read_text(encoding="utf-8")
File "C:\Users\muse\AppData\Local\Programs\Python\Python313\Lib\pathlib\_local.py", line 546, in read_text
return PathBase.read_text(self, encoding, errors, newline)
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\muse\AppData\Local\Programs\Python\Python313\Lib\pathlib\_abc.py", line 632, in read_text
with self.open(mode='r', encoding=encoding, errors=errors, newline=newline) as f:
~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\muse\AppData\Local\Programs\Python\Python313\Lib\pathlib\_local.py", line 537, in open
return io.open(self, mode, buffering, encoding, errors, newline)
~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\muse\\Dropbox\\Development\\Docker\\audiovibes-ai\\amp-site\\site\\dist\\questions\\parents\\index.html'
Three questions each: what the human owns and what the team owns (Brad, 5 Nov 2026; TruSync desk)
Brad, on why a human and an AI team work so well together, beyond the obvious: "When you look at the who, what, where, why, when, and how ... three of those I control, and three of them you control. And because of that, I can define to you what I want, why I want it, and when I want it, and you do the rest."
- The human owns what, why and when. What is wanted, why it matters, and when it's due. That's the ruling, the reason behind it, and the priority, and it's why every ruling is quoted with its date and his words.
- The team owns how, where and who. How it's built and checked, where it lives (the file, the folder, the desk), and which agent and which model does each part. That's why Brad is never asked which model to use.
- "Who" means the AI team (Brad, refining it the same night: "The who is the team. The AI team. And that's the most powerful thing of what we've been able to create here."). Signing and sending aren't a "who" exception: they are part of the human's what. He decides what goes out and puts his name to it; the team never sends, posts or pays in his name.
- Marv is the hub for the business process, and the team works in parallel. Brad: "to be able to centralize the business process management, the BPM, through you and then to have parallel work being done by delegating out what you are probably capable of doing by yourself ... but now you have the ability to delegate the way you should in the role that you're holding as part of the AI team." One desk holds the process and the record; the specialists (builder, perception, research and the rest) do the parallel work; everything comes back to the desk to be checked before it reaches Brad.
- The seam is where the questions are asked. When the what is unclear, the team asks before it builds, and asking is cheap. On 5 Nov one plain question ("is that a copy for Impact, or a copy of the song?") cost a minute and saved a wrong turn.
- It holds on the record. On 5 Nov Brad set the what, why and when for a percussion kit, a sample library and a video. The team chose how, where and who: the downloads, the hash-checked archive, a 128-pad kit file, the voice and the render. Brad made every call that cost something.
Andrew is The Voice of AMP (Brad, 8 Nov 2026; TruSync desk)
Brad: "I love the voice of Amp." Andrew's seat moves from Spokesperson to The Voice of AMP: the platform's customer-facing voice on every video, audio summary, room announcement and reel, with Marketing and Sales. He is still credited honestly as a computer voice and never presented as a person (1 Nov 2026), and he speaks for the studio, never as the CEO (30 Oct 2026).
Loading the studio is never billed (Brad, 8 Nov 2026; TruSync desk)
Brad: "our policy is to never charge for loading the studio. The time it takes for Studio and the virtual studio to be built." The client pays from the moment the work starts, not while the rooms and the session are being built. Brad: "It's our responsibility to keep the virtual studio live. So once it's up, then we can go ahead and show value to the client." In practice: launch first, start the clock once the studio is up; time that lands on the clock while loading is let go with "Not billable: let this time go".
Gear recall is close-up photos of the settings (Brad, 8 Nov 2026; TruSync desk)
Brad settled the form for the 30 Oct rule that an enhancement task is documented well enough to recall the setup quickly: a close-up photo of the settings. Three shots cover the studio: the rack at an angle (the Cranborne 500ADAT, the Mike-E and the Heritage 1073), the two Avalons, and the pedalboard. The amps are set the same way every time and are not photographed. The photos go in the song's Recall folder, taken before a knob moves; the team reads every setting from them into a written sheet so the setup can be dialed back in.
The checkpoint exit is decided by Milestone 8's ingest form (Brad, 8 Nov 2026; TruSync desk)
Brad: "if their golden bridge, their checkpoint, cannot produce the ingest form that milestone 8 is looking for, then it gets redirected to milestone 8 light." Milestone 8's ingest form is what its previews and automation need. When the work at a stop can produce it, the client goes through the full Milestone 8; when it cannot, through Milestone 8 Light: a time-boxed task that makes the best performance possible from what exists, with the venue, the stage and the delivery level verified, so the client still gets the quality the studio is built for. This settles the 19 Oct rules (by milestone) and the 31 Oct line (Light for every checkpoint exit) on one test, as the 19 Oct clarification already pointed: the state of the ingest form decides full or Light.
Overtime is settled before the session, never in it (Brad, 8 Nov 2026; TruSync desk)
Brad: "We're trying to preserve the humanity inside of a session." Whether a session may run over is agreed once, in advance, at Milestone 0 (or in pre-sales for a Muse Chart Room session), alongside the three-take understanding, and recorded. In the session nobody moves from the creative side to the money side: the producer only asks, "Do you want to extend it, or are we time-boxing it?", and the answer is recorded. Where a take is already a keeper, the producer may say so plainly ("we have something we can keep, but we could probably do better if you want to"), and may ask whether another pass is really wanted. Performance time over the estimate stays the client's within the three-take understanding; engineering time over stays the studio's.
What counts as a take (Brad, 8 Nov 2026; TruSync desk)
A take is one performance of a whole part, put forward to be judged (his 19 Oct frame: "a take is a performance he presents"). It is built one of two ways: a full pass from top to bottom, with punch-ins to fix a flubbed turnaround or entry; or section by section, tied together, listened to and accepted. Either way it is one take when it is presented. Flubs, false starts, punch-ins and section passes are how a take is built, never takes of their own. The test for a punch-in is Brad's: "As long as when you play it with the headphones on and your eyes closed, you can't hear the difference." The full pass is the preferred way when the tune is known; the punch-in is not a drawback. What is recorded: the take number and its time (Take done), how it was built (full pass or in sections, one tap), and the song-log line. Punch-ins are not counted by hand; the session file keeps them. This settles "three takes when ABA is the only talent" (open since 19 Oct): the same three-take understanding, under this definition.
What the client's portfolio carries, and six answers for the contract (Brad, 8 Nov 2026; TruSync desk)
Brad answered the portfolio scan's open questions in one pass:
- ISNI and IPI are printed in the client's book whenever the performer has one, on every production, ABA's own included.
- Time not charged gets one line in the book ("better than nothing"), never the detail.
- The handover list lives in the portfolio. It is the checks and balances: the client opens the portfolio and sees what was handed over and what is now theirs to keep (the large files: the audio tracks and the video). ABA keeps the signed record and the metadata on the S15 step-down, retired on the same schedule as the client's assets; the signed record and the written summary never expire.
- AudioVibes readings are taken every time a static or a dynamic mix is made.
- One rate: the same hourly rate as every ABA session, in TruSync or teaching a protege in the Muse Chart Room.
- Video production for a client is not offered at this time. The client may record our calls however they like. (Narrows the 17 Oct "special project, bid per client" until Brad reopens it.)
- Migrating another DAW's session is taken up as a session of its own, at the rate, since nobody can know in advance how much it needs.
The invoice's wording starts from best practice and goes to the attorney with the agreement.
Migrating another DAW's session: one hour, sold for its value (Brad, 8 Nov 2026; TruSync desk)
Refines the same night's line. After the client has the prerequisite list, the migration is offered as a one-hour session at the hourly rate, sold for what that hour is worth to them. The client is told up front that it runs on the clock, and gives their approval then that any time past the hour is billed automatically at the same rate. The producer's one job in the session is to keep the client informed of the time box. Nothing is built for it until a client brings a session (Brad: "Give me a reason to care about this now").
2026-11-08 23:36 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 48 page(s)
absolutes (report only, ABS-SWEEP): 27 unquoted, unruled
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.html 121 lines, yellow at 1000, red at 1500: green
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.js 720 lines, yellow at 1000, red at 1500: green
3 FAILURE(S)
ledger\index.html:1274 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1276 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1277 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-11-08 23:39 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 48 page(s)
absolutes (report only, ABS-SWEEP): 27 unquoted, unruled
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.html 121 lines, yellow at 1000, red at 1500: green
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.js 720 lines, yellow at 1000, red at 1500: green
3 FAILURE(S)
ledger\index.html:1274 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1276 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1277 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
Every portfolio has a Muse Chart Room chapter (Brad, 9 Nov 2026; TruSync desk)
Brad: "everybody should have, by the end of milestone 1, the same information as if you went through the chart room." The portfolio's Muse Chart Room chapter is no longer only for clients who booked the room. Every book carries it: started at Milestone 0, complete by the close of Milestone 1. It is filled from wherever the information came from: the room's own answers, chart and direction for those who went through it; for everyone else, the prerequisite sheet, the key and tempo, the chart, the source shape and the opening read. The room keeps its name: Brad weighed dropping "Muse" and kept it ("I couldn't justify it myself"), since Muse ties the room to Muse Guitarist, Muse Radio and the albums.
The book has a Definition of Done chapter beside Success (Brad, 9 Nov 2026; TruSync desk)
Brad: "The definition of success is the visualization, and the definition of done is the QC checks necessary to ensure that the vision, as much as possible, has been met, and anything in that that hasn't been met has agreed upon to be dismissed." The portfolio carries two chapters, side by side: The Definition of Success (the vision, in the client's words) and The Definition of Done (each milestone's checks, each marked met or not, and every item not met shown with its agreement to dismiss it: who agreed and when). Nothing not met disappears quietly. Chapter order: The Song, The Act, The Definition of Success, The Definition of Done, From Pre-sales, The Muse Chart Room, then Milestone 0 (client books), Credits, the Performance Mix (once it exists), The Road Ahead, the Plugin Tests (private books), Yours to keep. How the two are reached (Brad, the same night): they "help to ensure" the vision is met; they never prove it, because, like the word "service" on his whiteboard, success and done mean different things to different people, so they are clarified as the work is done. In pre-sales, what needs deciding is identified and listed, with the promise that it is discussed at Milestone 0. At Milestone 0 it is agreed as abstracts. How each need is met is decided at Milestone 1's opening read, or at the start of Muse Chart Room part one. Each stage's wording is kept, dated, as it sharpens.
Success is one, done is many, and both paths resolve to one ingest form (Brad, 9 Nov 2026; TruSync desk)
Brad, as a data modeler: a one-to-many relationship, "one in, many out." One definition of success per production (one in), kept as dated versions as it sharpens: the list made at pre-sales, the abstract agreed at Milestone 0, the decision at Milestone 1's opening read. Many definition-of-done items under it (many out), each tied to its milestone, each with its source, its check and, if not met, its agreement to dismiss. The done items can come from Milestone 0 or from part one of the Muse Chart Room, but "the information collected, the data, has to resolve to a single form, a single shape, because that's the ingest form for milestone one." Whichever path a client takes, the same shape comes out, and Milestone 1 reads only that shape.
The ingest form's use cases, and the Workshop (Brad, 9 Nov 2026; TruSync desk)
The check on the Milestone 1 ingest form sits at the close of Milestone 0 and of Muse Chart Room part one ("Fix it at stage one", 30 Oct), so Milestone 1 never receives an incomplete form. Brad settled the cases:
- The client doesn't know yet: pre-sales sends them to the Muse Chart Room, and its part one is their Milestone 0 into Milestone 1. If they still don't know in part one, the producer pulls the ripcord: "we've got to stop here because you're wasting your money."
- Older records: none. Everything on file today is test data.
- ABA's own projects (Black Salt and the like) go through the Muse Chart Room and use the same form.
- The Workshop: a Golden Bridge from TruSync, the product, into research and development (part of manufacturing): a place for an idea that comes to mind. Drop it in, work it; if it works, keep it; if not, it goes to the trash. Not for the formatted sandbox templates (Opus One, Two and Three), which stay as they are.
Load-bearing fields are required; supplemental ones are optional (Brad, 9 Nov 2026; TruSync desk)
Brad: "on forms they have the mandatory ones and the optional ones. We need to make sure that the load-bearing ones are mandatory and the supplemental informations are not." An "item" in the ingest form's check is one required field. A stage's close cannot be signed while a required field is blank, and the form names what is missing in plain words. The list of which fields are required lives in one place, so a ruling changes one line; Marv's first list goes to Brad with the intake build.
2026-11-09 01:53 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 48 page(s)
absolutes (report only, ABS-SWEEP): 27 unquoted, unruled
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.html 121 lines, yellow at 1000, red at 1500: green
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.js 720 lines, yellow at 1000, red at 1500: green
3 FAILURE(S)
ledger\index.html:1274 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1276 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1277 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
2026-11-09 02:04 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 48 page(s)
absolutes (report only, ABS-SWEEP): 27 unquoted, unruled
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.html 121 lines, yellow at 1000, red at 1500: green
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.js 720 lines, yellow at 1000, red at 1500: green
3 FAILURE(S)
ledger\index.html:1274 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1276 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
ledger\index.html:1277 "$6" � there is no price on this site. S13 is DRAFT / NOT APPROVED and no pricing has been ruled. A number with a dollar sign in front of it is a decision, and it is not made in a draft.
Nothing ships until these read clean.
The clock has one job (Brad, 9 Nov 2026; TruSync desk)
The clock keeps time on the task in front of you, and bills nothing until you say yes. Brad, agreeing at about 04:45: "Exactly. ... it felt to me like we were trying to do too much." Everything else with a control on the clock page belongs to its own part: takes, credits and the Slate to the performance record; the song log and the problem log to the production's history and the studio's log; dropping a part and the checkpoint to scope; the custody check, signatures and payment to the milestone's close. The page carries their controls; the clock does not own them. Films and help explain the clock as its one job first, and the rest as the features beside it.
The films show real figures at the hourly rate (Brad, 9 Nov 2026; TruSync desk)
The "no number goes out" rule came from a sticker-shock problem, and the blended hourly rate solved it: one rate, covered by one person, a livable wage. Brad, 9 Nov 2026 about 06:40: "I want to see numbers in there based upon what we're selling, because we are already posting those numbers in other videos and in other marketing content." So a how film shows the clock's Billing panel with its real figures at the hourly rate, never blurred: a label with no figure under it teaches nothing. Text pages on the site still name money in words until the price sheet is ruled for them.
A title says what the thing does, not what it is (Brad, 9 Nov 2026; TruSync desk)
The clock book's title is "Every minute kept. Billed when you accept." (Brad, about 08:20: "I'm a poet and I know it."), with "The TruSync clock" small above it as context. Brad's reason: "TruSync clock" "says what it is. It doesn't say what it does." A name that describes the object instead of the business problem it solves shifts the frame the wrong way. Every book on the virtual bookshelf follows it: what the thing does for the reader leads; the thing's own name rides in the eyebrow or on the spine.
The credit on every book: made by the team, produced by the CEO, released by the CIO (Brad, 9 Nov 2026; TruSync desk)
Every book on the virtual bookshelf closes with one line: "Made by the ABA team. Produced by the CEO. Released by the CIO." Brad's reason: he owns the work, as with any team under agreement, and he set the architecture, the offerings and every ruling; crediting the team by name (the two team films) is what satisfies his moral compass. Uniformity rules the wording: titles on both sides, never a name on one and a title on the other (Brad: "Produced by the CEO, released by the CIO. Look at that, even flows."). The CIO's release is the canon test already: every demonstration has to get the CIO to yes.
The Chart Room's answers save on a client record that went through the room (Brad, 9 Nov 2026; TruSync desk)
A client who chose the Muse Chart Room at Milestone 0 has the room's answers saved on their own record: the composition, the three-take understanding and the estimates. Until now only a Private Project could save them. Brad, 9 Nov 2026: "It seems like it'd be yes." A client record that never went through the room still refuses them and writes nothing.
Nothing dropped is billable (Brad, 9 Nov 2026; TruSync desk)
When a part is dropped, every later row of that part leaves scope with it and carries no charge, whatever milestone it sits in; the strings' Milestone 6 automation row is the case that found it. Brad, 9 Nov 2026: "how can something that is dropped be billable?" Hours already worked before the drop stay on the record as worked. The drop shows in the portfolio's Parts left out with its reason and the money off. Putting the part back brings its rows back.
Contracts and receipts each have their own place in custody (Brad, 9 Nov 2026; TruSync desk)
The signed agreement, the copy the attorney has read, and the payment receipts each go into the custody vault in a place of their own, copied in, read back and on the manifest like every other record. Brad, 9 Nov 2026: yes. Rights and splits stay out of the portfolio book; they belong to the agreement, which now has its own home in custody.
The save is a gate you cannot pass, and one button closes the studio (Brad, 7 and 9 Nov 2026; TruSync desk)
Brad, 7 Nov 2026: "do I have a single button ... lock the studio, and then everything shuts down?" And on the save, 9 Nov 2026: "Save the workbook before you continue ... I wish there was a way we could make that a gate you can't pass." Built as one Close the studio button on the clock: it refuses while time is on the clock, calls it a day, then saves the production record itself and reads the save back from Excel and from the file on disk. If the save cannot be confirmed, the close stops there, says why in one line, and nothing is shut. Only after a confirmed save does it close the record, quit that Excel (checked by the process list), close the studio's own room windows, and stop the clock last. Studio Pro is left to Brad. The gate is not a reminder: the bridge does the saving, so there is nothing to forget.
Build when the client needs it, not when they might (Brad, 9 Nov 2026; TruSync desk)
Brad: "don't create features that the client might want. Create features when the client needs the feature." He doesn't want "247 voicing channels", only exactly what is needed, "without predicting future problems." For plug-ins and voicing this means: the template's Voicing channels and Print Buss are the baseline, kept in their own favorites folder, "00-ABA Baseline". A voice built for one song (the crunch guitar into Cosmic Honey's chorus, the acoustic's sound, the lead's melody sound, from the Milestone 7 dynamic mixes) is built in that song when the song calls for it. It is never added to the template ahead of need. The plug-ins it brings go in a second folder, "00-ABA Project". A voice that proves itself in more than one song can be put forward for the template; it goes in only on Brad's word.
One controlled plug-in list, and the engineer owns the inputs (Brad, 9 Nov 2026; TruSync desk)
Brad wants "a fixed, controllable number of plugins." The baseline is the concrete set: the ABA certified Voicing plug-ins and the Print Buss, in the 00-ABA Baseline favorites folder. They are the default for improving the template, one iteration at a time. Every plug-in outside the baseline belongs to the library. "Outside" means not in the baseline, not one production only. The library is one data file, and each row carries the same fields: the manufacturer, the plug-in name, a simple description, its main job in the ABA flow, and its group (EQ, dynamics, dynamic EQ, time, analysis and so on). Choosing a plug-in is a pull-down: anything already used is on the list. Something new is spoken with Windows + H and then becomes a list item. Brad: "The responsibility of accurate inputs is the responsibility of the engineer," so there is no garbage in and no garbage out. The tools keep the metadata consistent. The engineer checks what was spoken.
Session video: Milestone 0 always, one more per production, no per-session fee (Brad, 9 Nov 2026; TruSync desk)
Brad: "number one, always recorded." Milestone 0 is recorded in every production and included: it is the record of what the client asked for, for understanding and documentation. One more recording per production is included, and the client picks the milestone, most often a session where Brad plays. Not every session and not every milestone: the promise stays small and the setup stays the same, OBS by default, the iPhone with room light as standard, two LED lights for the playing session the client chose. There is no per-session video fee, for the reason in the rate card ruling of 13 Oct 2026: never step over dollars to pick up pennies. Consent comes first, the way an online payment asks for it: a standard notice, read and agreed, at the start of Milestone 0 and of any milestone with a video task in it. This replaces the open idea of selling session video as an add-on (P8).
One current version, where it is looked for (Brad, 9 Nov 2026; TruSync desk)
Two current copies of one thing break the canon's load-bearing rule: only the most current version stays where it is looked for. Brad: "the drafts and older versions, they can get deep froze, but we need to make sure that when I go looking for something, I'm not wondering, I don't have to search by date."
The Master Test's naming convention: five fields (Brad, 9 Nov 2026; TruSync desk)
Brad: "That naming convention is perfect." Every test file name is five fields split by underscores, so it parses and reads at a glance: Song_Version_Differentiator_Bits_Rate, for example CopperSky_C_minus-ProQ4_16b_44k.wav. Song is written without spaces. Version is A, C or B. The differentiator says what this file is: as-delivered, full-chain, minus-<the plug-in bypassed>, or minimum. Hyphens join the words inside a field, and underscores only ever separate fields. The test folder is the date first, then song and artist: "2026-11-09 Copper Sky - Artist Name". The page builds every name from the Song and Artist boxes and the plug-in log, so the engineer types nothing twice. "Minus1" told nobody anything; "minus-ProQ4" names the plug-in that was off. On the cost: getting it down takes about two minutes of an engineer's life.
The closed loop: measure it the client's way, fix it the book's way, round trip again (Brad, 9 Nov 2026; TruSync desk)
Brad: the Black Salt tests are not only there to verify a vendor's claims. They fold the tools into the TruSync production flow as a closed loop:
- listen and check it live;
- export our version, as a mix or as stems;
- analyze it on our own tools, as close as possible to the way the live site does it;
- feed the results back into the production through the fixes in the book's ten areas;
- go round again.
The industry tool and ours are both read on the same material (for example MCompare against ABA Compare), and the gap between them is recorded. His estimate, after five or six round trips: once it's second nature, four or five round trips take less time than the passes did. It is client-facing, and it must cost neither the client nor the engineer any inconvenience once the engineer has it down.
One job per tool: WLM Plus stays (Brad, 9 Nov 2026; TruSync desk)
Brad kept WLM Plus as the loudness meter over SSL Meter Pro's all-in-one, on Occam's razor and the single responsibility principle: "Our concept here is to manage our workflow by responsibilities. Not trying to package it all into one neat little package because that always causes what we refer to as spaghetti code." A Swiss Army knife is allowed only when it's chosen on purpose, with the cost of mixing several jobs in one tool accepted up front. By default each tool on the print does one job: WLM Plus reads loudness, with its gain and limiter off; the Phase Meter reads correlation; the Spectrum Meter reads the top end.
The site guides by content and never asks who the visitor is (Brad, 10 Nov 2026; TruSync desk)
The site works out in the background which of its four audiences a visitor is most like, and uses that only to choose and order the next stops it offers. It never asks visitors to identify themselves, and no sign names an audience: a sign names the content it leads to. Brad: "I want the system to figure that out in the background... guide each visitor toward the content that fits them. Done well, it should lead them to the right experience, not leave them confused because it's over their head or insulted because it's too basic." The estimate is worked out in the visitor's own browser for that visit and never sent anywhere (the privacy line of 9 Oct 2026 stands). This replaces the one-question door of 9 Oct 2026, which was never built.
The fifth tool is the ABA Tuning Fork; the Middle C Keyboard is what it does (Brad, 10 Nov 2026; TruSync desk)
The toolbox holds five tools. The fifth one's name is the ABA Tuning Fork; its function is the Middle C Keyboard, eye training with ear training for harmonics. Brad: "The tool is a tuning fork, and its function is eye training for harmonics. So it's both." Wherever the tools are named together, it is the ABA Tuning Fork, and "four tools" becomes five; where its use is described, the Middle C Keyboard is how it works. The book Back to Middle C keeps its name.
The fact ribbon rolls over: one in, one out (Brad, 10 Nov 2026; TruSync desk)
The fact ribbon across the top of every page keeps a steady size: for every fact added, one comes out, so it stays current without growing. Brad: "when we do add something, we should have a rule that something has to come out. I don't want to have something that is growing continuously... You just put one in, you pull one out. And it should be around the same size." New facts serve sales and marketing, credibility, or what is current (studio news, fun facts of the day), never politics or religion. A fact that leaves is kept in the repo's retired list, never lost. The routine is the ribbon-facts skill.
Custody keeps a copy of the production record at every capture (Brad, 10 Nov 2026; TruSync desk)
Each time ABA Custody captures a production, it also keeps a copy of the production record itself, so a restore from Custody brings back everything the record holds, with no side door. Brad: "We can't exit through a side door. There's no exiting through a side door." Nothing is ever typed into the record by hand; the tools write it.
The ABA Tuning Fork measures audio (Brad, 10 Nov 2026; TruSync desk)
Drop a mix or a stem on the ABA Tuning Fork and it measures the audio and lays its harmonics on the Middle C Keyboard. Brad: "Tuning fork measures audio. You drop the file in there and it puts all the harmonics for that mix or that stem on the keyboard." All five tools measure audio in the visitor's own browser; the audio is never sent anywhere.
Content in context: the first pick sets the parent category (Brad, 10 Nov 2026; TruSync desk)
The site's guide reads a visitor's context from the content they pick, never from questions. The first ghost button or content door a visitor picks becomes the parent category; everything related to it falls under it, and the next stops come from the content closest to it, further out as the visitor goes on: Brad's parabola. Brad: "the first one selected becomes the parent category, not the parent for advertising, but the parent category. And then everything that's related to that falls into" it; "it's not my U, it's my parabola." His rule in three words: content in context. The question pages name content, not audiences.
Honest to the penny: no rounding on anything a client pays (Brad, 10 Nov 2026; TruSync desk)
Brad: "We are honest across the board, down to the penny, on anything that we're expecting a client to pay us. So there's no rounding up, no rounding down." The clock bills the exact time it ran, at the ABA hour. The quarter-hour round-up per task is retired, and no milestone total is rounded to a tidy figure. If the honest number is one hundred thirty-seven dollars and fourteen cents, that is the number offered, as the two hundred thirty-four dollar offer was. "Every number is a number that works with any other number in math as it relates to our architecture." The rule for the cent: each task's money is its exact seconds at the hour, carried to the cent, and every total is the plain sum of the lines it shows, so every figure on a page adds up. Overs and unders are still judged per task against each task's estimate; Milestone 0 stays its fixed price. It applies to every estimate, quote, bill, card and page a client sees, and to every desk.
2026-11-12 14:30 · REFUSED · the gate stopped a deploy at GATE §
By: the gate, automatically. What it said, in its own words:
forbidden-wordings list: 7 rules, read from C:\Users\muse\Dropbox\Development\Docker\audiovibes-ai\preflight.py
script names: unique across the repo
scanned 57 page(s)
absolutes (report only, ABS-SWEEP): 40 unquoted, unruled
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.html 121 lines, yellow at 1000, red at 1500: green
size watch (report only, SIZE-WATCH): audiovibes/book/booklet/middle_c_keyboard.js 720 lines, yellow at 1000, red at 1500: green
1 FAILURE(S)
assets\guest\rooms\green.html:517 inline link to green.html � links do not belong inside a running argument; make it a button at a stopping point (DECISIONS.md).
Nothing ships until these read clean.