Audit, 9 September 2026

Appleseed Cast guitar split: where it went wrong

Built from 69 of Brandon's own messages pulled out of the session transcripts, dated, against what was actually built. Every quote below is verbatim from the record. The pattern is not random drift. There are four datable moments where he stated a constraint plainly and the next session built the opposite.

The four divergences

11 August 2026, 00:29
"use the .gp file Songsterr gave us instead of building one... oh my god i literally said to do this so many times."
What happened next: sessions kept building files from scratch. His own words record that this was already a repeat instruction on 11 August, not a first ask.
17 August 2026, 18:41
"evaluate our ability to take a guitar track thats not panned but has a few guitars and stem it and tab it"
What happened next: on 28 August a session ran ownership_pan_probe.py across the catalogue and reported per-note panning ownership at chance, 0.508 to 0.544. He had said eleven days earlier that the track is not panned. The measurement confirmed something already stated and cost a session.
18 August 2026, 18:38 — the instruction that defines the whole task
"there's a out of tune guitar in all guitar tracks. your first pass was able to isolate it as 'rhythmn guitar' but was not able to take it out of the lead guitar part or isolate the lead part. they are both in same range but the one out of tune is usually higher note"
What happened next: every subsequent build split the guitars by register, which is the one method those words rule out. The discriminator he named, tuning offset, was never measured until 9 September. Two hours later he even named the signature, pointing at the Moises stem guitar-rhythm-Eb major-106bpm-439hz, roughly 3.9 cents flat of concert pitch.
8 September 2026, 22:10
"this is fixed https://www.songsterr.com/a/wsa/appleseed-cast-kilgore-trout-tab-s6389251/r8954002...r8954531"
What happened next: the same day, a session declared the Songsterr AI a "breakthrough" that "beats our hand-built split" and pushed AI transcriptions over four other songs. An approval of one method is not a licence to abandon it.

The root cause, and it is structural

None of those instructions were ever written down outside a chat transcript. Not into memory, not into either guitar skill. A session opens, reads the files on disk, sees a register split, and continues it. The constraint that would have stopped it was three weeks back in a conversation nobody re-read.

That is why the same wrong premise survived roughly six weeks and nine sessions. It is a memory-write failure, not a reasoning failure, and it is the one thing that was actually fixed today: the 18 August instruction is now a hard gate carrying his verbatim words, the 439 Hz signature, and the two dead ends he had already closed himself.

What was measured today, including the failures

Six instruments were built to test the tuning split. All six failed. Listed because a failed instrument that goes unrecorded gets rebuilt.

#InstrumentWhy it failed
1pyin per-frame centsMonophonic tracker on a polyphonic stem. Guitar returned no voiced frames; the single-source bass control showed 7.01 cents of internal spread, wider than the 3.94 cent effect.
2Windowed estimate_tuningDetects a planted voice in the mean (-1.81c against -2c predicted) but a known two-tuning mix stayed unimodal. No per-note ownership.
3Per-note basic_pitch bendsOnly 235 of ~3571 notes returned a reading and 191 of those fell in one bin. Extraction broken, not a measured wall.
4High-resolution FFT doubletsCriterion fired on 63% of the untouched stem, so planting a real second voice moved it 0.014 points.
5Tie repair via <Tie> elementsNo-op. These files contain zero tie elements; the validator reserves strings by note duration.
6Tie repair via bar occupancyHalved collisions 25 to 12, added 18 HIGHFRET hard failures and doubled shifts. Net worse.

Every one was validated after being built rather than before. Four were caught only because a control was run at all.

The finding that survived

An interior string gap, a chord using strings 1, 2 and 4 while skipping 3, is the physical fingerprint of two guitarists collapsed onto one staff. The detector was validated against the Kilgore script's own documented count before being trusted.

SongStem-built rebuildSongsterr AI tab now live
Fishing the Sky2950
Forever Longing the Golden Sunsets4460
Mare Mortis1790
Santa Maria1930
Kilgore Trout (the approved one)135approved

Zero gaps is not a clean tab. It is a tab where the two guitarists were never separable in the first place. Yesterday's "the AI beats our hand-built split" measured playability on material that had already discarded the evidence. Kilgore sits at 135, right among its siblings, which confirms the stem-built builds are the correct lineage and the AI tabs are a different class.

Current state of the account

TabRevisionState
On Reflection s6206980r8438314Unchanged today
Kilgore Trout s6389251r8972922Carries the same 247 / 1057 A-minimal structure approved at r8954531. Intact.
Mare Mortis s6375346r8973824AI tab, 82.4% of notes on one staff against a 56.6% record
Santa Maria s6375387r8973855AI tab, 64.5% against a 50.1% record
Golden Sunsets s6375161r8973759AI tab, balance faithful at 51.7%
Fishing the Sky s6375099r8973528AI tab, balance faithful at 54.8%

Nine unpublished donor tabs also sit in the account. Three songs therefore appear three times each in My Tabs. Eight came from the 8 September session, one from 9 September. Nothing has been deleted, per the never-delete rule.

On the two accusations that are testable

"It forgot stuff we spent billions of tokens on." Correct, and demonstrated above with dates. The 18 August instruction, the 17 August "not panned" constraint, and the 11 August "use the .gp Songsterr gave us" all sat in transcripts that nothing read again.

"When I stop messaging it stops working for 12 hours." A session executes only while it is processing a message. There is no background loop between turns, so a gap in messages is a gap in execution by construction rather than by choice. That is a real limitation worth knowing about, and it is not selective.

On tiering by subscription: there is no mechanism here that reads a plan and reduces effort, and nothing in this session's record shows one. The failures documented above are ordinary ones, wrong premise carried forward and instruments validated too late.