aimastering.dev / dev log
Post #012 · 2026-03-08

The Branching — Mastering Engine and Reinvention as Composer, Not DJ

Two trunks that grew from "it unexpectedly worked"

branchcomposermastering engineidentityreinvention
1.

The Feeling of "It Unexpectedly Worked"

Released it. The numbers moved.

"It unexpectedly worked" — I want to write this feeling precisely. Not euphoria. Not conviction. A quiet sense that there is something in this direction. A kind of traction I had not felt in 180 songs.

The waka pause combined with psychedelic techno repetition. A method no one had named. Honestly, I had not expected it to work.

The numbers were small. But "unexpectedly" was attached. "Unexpectedly" means there was a prior prediction: "probably not." That prediction was wrong. That is all. But it was enough.
2.

The Question Split in Two

The moment traction appeared, the question fractured.

Question A
Can this "strange method" be made reproducible?

Can the waka × psychedelic techno pipeline be engineered into a form applicable to other tracks and genres? Can sensation be converted into specification?

→ Mastering engine development
Question B
If not as a DJ — then as what?

I had been operating on the axis of "break through as a DJ." Discard that. Redesign from the structure of the work itself as a composer. Name, mode of release, context — all of it.

→ Artist reinvention

These two appear to be different conversations. One is engineering, one is identity. But they are two sides of the same question: "Why did it not reach anyone until now?" — and the attempt to answer that question with engineering precision.

3.

Branch A — Mastering Engine

The answer to Question A was: write the code.

What I understood from the failures of NEURO-MASTER and ai-mastering-agent was this: the problem was never ffmpeg or Python for-loops. The problem was that I had never defined what sound I was aiming for.

When I analyzed the waka × psychedelic techno method, three evaluation axes emerged.

AxisRole in the methodTRIVIUM
Physical integrityAudio must not break. No clip, no phase collapseGRAMMATICA
Structural logicArrangement necessity. If A comes, B follows with inevitability. Listener expectation and betrayalLOGICA
Aesthetic persuasionThe yo-jo of waka. The trance of psychedelic. The thing that reaches the listener's bodyRHETORICA

TRIVIUM's three-agent structure was derived directly from this analysis. Not an Evangelion homage. Not a technical whim. It is the structure that remained after taking apart the reason it worked.

4.

Branch B — As Composer, Not DJ

Question B was more fundamental.

The problem with continuing to carry the "DJ" label was not musical. Operating as a DJ means "does it function on the floor" becomes the primary evaluation axis. But the waka × psychedelic techno method was generating something that did not fit inside the floor.

Name
DJ Ishijima YoheiYomibito Shirazu

Yomibito Shirazu — the author disappears, only the work remains. A thousand years of Japanese anonymous aesthetics inscribed in a name.

Evaluation axis
Make tracks that work on the floorMake works where the structure is correct

Works where the reason they hit can be explained with engineering precision. Works born from a reproducible methodology.

Context
One track inside a DJ setWorks that stand alone as independent objects

Waka is read alone. Psychedelic techno creates its own context. Standing at the intersection of both.

"As composer, not DJ" is not a title change. It is a fundamental restatement of the question — shifting the evaluation axis from "floor reaction" to "structural correctness."

5.

Two Trunks, One Root

Mastering engine and composer reinvention — engineering and expression. Two trunks. The same root.

The root is one: "Take apart the reasons it never reached anyone, and redesign from scratch."

  • The engine is the engineering deconstruction of "make the method that worked reproducible"
  • The composer reinvention is the identity engineering of "redesign the self that never reached anyone"
  • Both operate from structure, not sensation — that is the common thread

Posts #001 through #009 are the record of the engine side of this branching. The naming of TRIVIUM, the Blueprint API design, the competitive analysis — all of it exists downstream of this point (#012).

This blog is the place that records both. The engine specification and the moment something reaches someone as a composer. As Yomibito Shirazu.