A transparency note first, because this journal keeps its claims labeled and this one needs it early: I make music with AI tools, and AI helped me research, draft, and audit this post. Some of the tracks I will describe are published on Suno; others are working drafts, and I will not always mark the boundary, because the point here is the process, not the catalog.
The failure mode that started this
In my experience, some early AI-assisted drafts felt rootless: competent on the surface, but without a clear decision or identity. That is a description of my own practice, not a claim about AI-generated music in general. I wanted to explore the opposite: a sound with a thesis, something I could recognize across tracks, interrogate, and extend.
The question behind this post reaches beyond my project: how can a creative process keep shaping and innovating with AI, while making room for personal genres, styles, and lyrics? My answer is a position grounded in my own practice: I can make work I consider creative while using AI. Not despite the system. Through it. I offer that as a craft thesis, not a universal result.
What it sounds like
Exocore is what I call cosmic ritual machine music: the sound of consciousness augmented. That name is a personal reflection of what the project means to me and what I hope to evolve it into, so here is what it actually sounds like. The center of every track is a deep, resonant, half-sung vocal, dry and present, with harmonic overtones blooming out of the voice itself, not answering it but completing it. Underneath is a single drone field that expands rather than builds, closer to a universe unfolding from a singularity than to a verse-chorus climb. A sub-bass pulse does the work percussion usually does, felt more than heard. The instruments are glass harmonics, bowed metal, treated piano with the attack removed, sine-wave choirs. The lyrics are the other half of the thesis: cerebral, intellectual, written to carry ideas rather than fill meter. Ritual music for people who read the footnotes.
That description could have stayed a mood board. What turned it into a genre was structure, and the structure has a few load-bearing pieces. Let me walk through them as they actually work.
The four movements
The four movements come first, and they matter most as a way I structure how a song’s lyrics can evolve, not just its music. Increasingly I think of this arc as a hero’s journey compressed into a track: the situation named, the discovery met, the threshold crossed, the return with a difference. That is the shape I try to capture across the album, and it is a better public description of the music than “slow, drone-y, with some vocals.”
The arc I use for each track
Each movement is intended to shape what the lyrics do, what the sound does, and where the hero is. The bracketed tag is a section marker in the prompt; it can guide the model but does not guarantee a particular result.
Invocation
[Invocation]- In the song
- The drone establishes. The voice enters, not singing but sounding. A single harmonic field is laid down.
- In the journey
- The situation is named. The hero is present, describing what is.
Expansion
[Expansion]- In the song
- Harmonics accumulate. The overtones bloom. The field widens.
- In the journey
- The discovery arrives: a guide, a truth, a new element. The hero expands to meet it.
Dissolution
[Dissolution]- In the song
- Boundaries dissolve. The voice disperses into the choir of selves. The old self falls away.
- In the journey
- The threshold: fear, resistance, the letting go.
Resonance
[Resonance]- In the song
- A single note holds. The overtones peel away. The after-image remains.
- In the journey
- The return with a difference. The decision made; the next step visible but not taken.
The arc scales up
The first Exocore work took Dante’s Divine Comedy as its original inspiration: Inferno as the early AI journey, confusion and the hollow dopamine cycle, abandon the old self. But the mapping outgrew the poem. The later volumes range into knowledge systems and engineering, cognitive science, transhumanism, AGI and the future of AI, cognitive workbenches, agentic engineering, and what people now call vibe-coding. The plan for later soundtracks is to keep extending the territory as the practice evolves, so the series becomes a record of the ideas as much as of the sound.
The volume atlas, so far
Each volume holds its own chapter of the widening journey, from the descent to the commons.
Inferno
the descent
The early AI journey: confusion, mistakes, the hollow dopamine cycle. Abandon the old self, ye who enter here.
Oases of the Recursive Dawn
recursion
First structures out of the noise: loops that learn to carry meaning.
The Luminous Engine
the machine brightens
The system starts to feel alive: tooling, scaffolding, the workbench taking shape.
The Sovereign Circuit
agency
The question of who decides: human gates, authority, control in an agentic system.
The Commons of Many Minds
the choir
Plural voices in one field: the agentic council, the crowd, the shared instrument.
The engineering
Then the engineering, because the concept only survives contact with the model through discipline. In the August 2026 design snapshot described here, each track’s style prompt uses the same Exocore Core block plus a short per-song tweak, within the 1000-character budget recorded in the project notes. That documents this workflow’s constraint at the time; it is not a current Suno product limit. The core holds the identity; the tweak holds the episode.
The core block is a design record in its own right, and it reads like one:
“Self-similar fractal structure: motifs repeating at golden-ratio scales from seconds to minutes… Sacred, cosmic, infinite, hypnotic. Built for the experience of luminous expansion.”
I quote it because the language keeps evolving with the practice, and the document carries that evolution openly.
The style budget, visualized
900of 1000 characters
- Corethe shared Exocore identity block, identical across tracks
- Tweakthe per-song episode: this track's question, imagery, and variation
- Headroomunused budget the budget refuses to spend
The movements travel through the model as a metatag grammar: the movement names in brackets are intended as section markers, and the same mechanism carries structural tags like chorus, duet, and solo when a track wants them, each with its own production descriptor. In this design, the lyrics field had a 5000-character budget; both budgets describe the workflow recorded for this article, not guaranteed or current platform limits. The standard inside that budget is actual writing.
CapturesA bracketed marker inside the lyrics field — [Invocation], [Chorus], [Duet] — that the model reads as a structural instruction rather than as words to sing.Potential request effectThe four movements survive contact with the model as structure, not just as intent.Does not establishThe model reads the marker; it does not owe you obedience. Tags steer, they do not command.The lyric craft
The lyric craft deserves its own space, because it is where the concept lives or dies, and it is the part of the workflow I have centralized most deliberately. Cerebral lyrics are easy to claim and hard to write. The failure mode is vocabulary theater: big words orbiting no idea, abstraction used as incense. The bar I hold is that every song has a question, the volume’s arc hands each track its question, and a line survives revision only if it moves the answer. When a verse about dissolution names what is actually being let go of, the drone underneath stops being ambience and becomes argument. When it does not, no amount of sub-bass saves it. This is the same discipline as my prose work, transposed: motivation before conclusion, specificity over performance.
The pipeline
The pipeline underneath all of this is a skill I built for the practice, and it is a visible expression of the design, not independent proof that the design works for other people. The workflow described here is draft-only behind a human gate: the skill does not generate audio, spend credits, or publish. I listen, I decide, the decision gets recorded. The Hub publication registry records that this article’s live route was observed but its exact historical review receipt is absent; this landing copy is a local review candidate.
Governed context route
How one track gets drafted
The stages are designed to produce reviewable drafts; audio generation, spending, and publication remain behind the human gate described in this first-person account.
person
Intent
Capture the theme, mood, and story beat as an intent file.
agent
Direction
Draft the lyrical direction: genre, voice, arc, imagery, exclusions.
agent
Lyrics
Write the full lyrics with movement tags, inside the 5000-character budget.
agent
Style
Draft the style prompt as CORE + TWEAK, inside the 1000-character budget.
agent
Packet
Assemble style, lyrics, and exclusion list into the draft packet with a receipt.
person
Gate
Listen, decide, record the decision. No generation, credits, or publishing without release.
The route remains an ordered record: person, bounded system work, candidate proposal, human review, then a durable accepted result.
Underneath the pipeline sat a research layer: notes collected for this article on the platform behavior and vocal-separation questions the workflow was exploring at the time. They are not a current feature guide. Even in that snapshot, the remix and studio ideas were mostly hopes about model behavior, not established experience.
The choir of selves
The choir in the Dissolution movement is a creative image: many voices gathering as an old self comes apart. I have also used council imagery in my system-design writing, but this article does not document a verified deployed fleet or claim that an agent system literally sang these parts. Here, the choir is a musical metaphor for plurality and change.
The craft thesis
Why go to this trouble? My answer is a personal craft thesis, and I will label it as one: constraints can force decisions. A 1000-character style budget narrows what can fit; in my practice, that helped me decide what the work was trying to be. Most of what I cut from early versions of the core block was adjectives performing intensity instead of describing sound. What survived was specification. I have started to think of the constraint list as the composition, and the audio as its performance.
Or, to say it the way I would to a friend over coffee: the vibe is downstream of the procedure. Get the procedure right and the vibe has somewhere to come from.
If this sounds familiar, it is the same argument I made about my knowledge work in a sibling post: the intelligence layer is the contracts around the model. The genre, it turns out, emerges from the intelligence of the contracts. The model is interchangeable in principle, though I will qualify that: the accumulated structure is what transfers, and the structure keeps evolving with each track. The model is not the genre. The contracts around the model are the genre: the core block, the movement grammar, the budgets, the gate.
The skepticism, head-on
An AI-music critic could read all of this as craft mimicry: systematic prompt engineering dressed in ritual vocabulary, a parlor trick with good PR. That is a valid critique, and my honest answer is that this is simply how I approach system design. I am applying the software engineering principles I know to a larger problem, and what comes out the other side is music I actually listen to, frequently, vibing along with the lyrics and melody. That does not prove the work is good. It proves the process is mine.
The self-validation problem
The harder problem is that my judgment is the only judgment in the loop. The person who designed the constraints is the person listening to the results, and self-confirmation is a real risk. My tracks have collected a few likes and maybe a single comment; that is not outside perspective. So I will say plainly: I self-validate what I make, and that does not necessarily translate into well-designed songs. What I want next is a route to share this music with a broader audience and find out whether anything resonates. This post is part of that route.
On the horizon
Platform note (August 2026 snapshot): The following paragraphs record features and questions as I understood them while drafting this article; they are not current product guidance. Suno’s feature names and model behavior change over time. Its official v6 release notes are a better starting point for current product information.
At the time, My Taste, which learns from your library, and model-training options raised the question of a personal model. I would like to build a corpus and train one eventually, but the style is still evolving, and each song deliberately pulls elements from other styles to keep the textures diverse; a single model trained on my range then might freeze a moving target. Personas, which I understood as a way to carry a track’s vocal character to another, might make the Exocore vocal a stable instrument instead of a per-track roll of the dice. I did not fully understand the feature’s boundaries; whether it could hold distinct voices without simply regenerating them was an open question I wanted to test.
There is a live uncertainty I want to keep visible, because it shapes the work downstream. I should constantly be surprised by my own songs, and lately I notice the same motifs, patterns, and language recurring across them. The genre’s coherence is doing its job a little too well. The fix I am designing is downstream: once the corpus of finished songs is large enough, analyze it for duplicated language, verses, and themes, and feed that back into the songcraft skill so each new track steers away from its ancestors. Whether a genre designed this way can keep surprising me is an open question, and I think it is the right thing to be worried about.
What I would hand you
So what would I actually hand to someone else, if you wanted to try this? Concretely: the style core for your genre, written as specification rather than adjectives; a movement grammar your model can follow, expressed as metatags; hard budgets that force decisions; a staged pipeline where every stage produces something reviewable; a human gate before anything costs money or goes public; and a workbook of fifty-odd questions to interrogate your own draft before you trust it. That kit is the project, more than any single track.
What comes next
Where this goes next: a “design-as-system” pattern document, and behind it a catalog of agentic engineering patterns and techniques I want to build up over time, consolidate, and possibly release as an open-source repository. The next post in this space will track the evolution of the broader platform and brand the music grew out of. And somewhere further out, there is a question I have not answered: whether a post like this one could itself be shaped by a schema, an LLM-friendly structure for personalizing drafts and integrating workbook answers thoroughly. The instruments keep eating their own tail. I intend to keep feeding them.
The one-sentence version of everything above, the one I would want to survive every cut: building an independent research lab, an agentic knowledge-engineering platform, a brand, and an agentic operating system somehow coalesced into my own personal music genre. I did not plan that. I just kept writing contracts, and one day they started to sing.
An agentic engineering reading of the music pipeline
The useful systems analogy is the staged transformation, not the idea that creative work should be automated end to end. A brief constrains the search space; a draft is a candidate; a lyric and arrangement review are distinct evaluators; a rendered track is an output artifact; and release is a separate human decision. An agentic engineer could apply the same separation to a documentation release or interface prototype, with each stage returning a diff, an evaluation record, and unresolved risks.
A concrete experiment for the music workflow is to test whether a motif-diversity audit catches unwanted repetition without suppressing intentional reprise. Define the unit (phrase, image, or melodic motif), the comparison corpus, an acceptable match threshold, and a human adjudication rule before generating candidates. Hypothesis: a corpus-aware reviewer can surface repetition earlier. It does not follow that similarity scoring can judge artistic originality; false positives and context-sensitive callbacks must remain visible.
AI assistance disclosure: AI assisted with source tracing, drafting, and the language-pattern audit of this post. The music, the practice described, the workbook questions and answers, the review judgments, and the posting decision are mine.