Mythwright · private beta

The shape you didn’t decide

Generative tools produce competent, anonymous work, and the usual fixes — better prompts, more fine-tuning — are all downstream. The differentiator sits upstream: whether you can state what recurs in your own work precisely enough to enforce it, and precisely enough to reject things that violate it.

Below is a reading of one of my own tracks that I could not have produced by listening harder.

Not because the reading is clever — because it depends on something outside the track. A map of how my whole catalogue relates to itself, written before that song was finished. With the map, the song says one thing. Without it, it says something considerably smaller.

That map is what I’ve been calling a mythology layer. This is what it is, what it found in a bass single called Dope Ways, and why I think it’s the missing input for anyone trying to make generative tools produce something that sounds like them.

You already have one

The claim isn’t that you have themes. Everyone knows their themes — themes are what you’d list if asked. The claim is that underneath the themes you meant, there’s a structure you didn’t decide: things that recur across years and formats without your choosing them, related to each other in ways you’d never have described.

In my case one of those turned out to be a function rather than a subject. Nearly everything I make is organised around passage through darkness rather than escape from it. Not darkness as a topic — darkness as a route. It shows up in songs written a decade apart, in a game, in how I name things. I never decided that. It was simply true, and had been for a long time before anyone wrote it down.

Once it was written down, it stopped being a description and became a test.

Inspector · why this is a constraint problem, not a prompt problem

Prompt engineering optimises within a model’s prior. Fine-tuning shifts the prior toward a sample. Neither produces a specification — a stable set of invariants a generation can be checked against by a reviewer who isn’t you.

What the layer yields operationally is closer to a schema than a style: typed entities, the relations between them, and a small number of constraints that hold across the whole body of work. That makes three things possible that weren’t before. You can enforce — write invariants a generation either satisfies or doesn’t. You can reject — evaluate a proposal against the graph rather than against taste. And you can delegate — hand the constraint set to a collaborator, human or model, without handing over your judgement.

That last one is why this matters for anyone building creative systems. Taste doesn’t scale and doesn’t transfer. A constraint set does both.

On the word “mythology.” It isn’t borrowed from Campbell, and there’s no hero’s journey in here. It’s borrowed from Roland Barthes’ Mythologies (1957), which read wrestling matches, detergent adverts and a plate of steak and chips as seriously as anyone had read scripture — on the argument that myth isn’t a stock of ancient stories but an operation: the thing that takes something contingent and historical and makes it feel natural, obvious, simply how things are. Barthes’ method was to catch that operation happening and name it, which dissolves it — once you can see the myth being made, it stops being self-evident.

The layer runs that same operation, aimed inward. A working artist’s recurring structure is exactly a naturalised contingency: it feels like taste, or like nothing at all, because it has never been stated. Writing it down performs the Barthesian move on your own material — the inevitable becomes visible as a construction, and a construction can be enforced, refused, or deliberately broken. That’s also why this reads a bass single line by line rather than reaching for archetypes. Barthes’ claim was that myth lives in the ordinary and specific, not in the grand and universal, and the readings above are only defensible at that scale. Where we part from him is intent: he demythologised to disarm what myth was doing to people. Here it’s done to get a usable specification out of it — same operation, opposite end of the tool.

The instrument, on one track

Dope Ways is a bass track with Squirrelybass that opens a three-single run. On the surface it’s a monster song — swamp creature, cosmic horror, a lot of very confident threats. It’s funny. It’s meant to be.

On the left is the whole track, with the annotated passages marked in place. On the right is the part usually left implicit: the actual graph the reading resolves against, as the vortex it is. Select a line and you travel to the entries it lands on; drag to look around the structure, or step through the resonance points in order. That lookup is the whole mechanism — the reading isn’t interpretation, it’s a query against a structure that already existed.

↓ select any marked line · drag the field to look around the structure

Better look both ways
Eyes in the back of my head like don’t say
Shit behind my back

Leave you cross eyed in a moat grave
Try to apologize but I won’t save
Even if you oath pray
Food for the fishes and the boat spray
Lost in a dope haze
Moss for my close shave
Monster in the swamp
Better hope that I don’t wave
Hope that I don’t wake

Hope I won’t kill em
Chillin in my chair like Willem
Show you how Byrgenwerth was just the beginning
Ain’t no ceiling
Otherworld dealings
Black hole leftovers congealing like
Call me the astral disaster
Hanging from the rafters
Nightmare fuel and it’s you that I’m after
Douse you in the fumes
Till your soul consumed
Sulfur gon(na) bloom
Light you aflame
Lose yourself to the pyre
Burn in the fire

Smoke spiral gettin’ higher
Yeah I spoke to the ashes
Leave behind all your earthly desires
See your soul reborn
Look what happens when you don’t confirm
Shouldve listened
Yeah you were forewarned
Hive-minded till I free the swarm
Blood through the fingers while the juice still warm
Torn from the flesh till there’s nothing left
Purgatory where you wish for death
Gotta go through (be)fore your soul gets blessed
Gotta go through hell
Gotta gotta go through
Gotta go through hell (be)fore your soul gets blessed
So let’s play chicken
Clock still ticking
Watched pot boiling
Blood be thickenin’
Flow so sickenin’
Cooking in the kitchen
Till there ain’t no competition
Sunrise dishin’ out Dawny
Drippin’ like coffee

Head popped on a zombie
Higher than the fronds on a palm tree
Realized I could be what I wanna be
So I’m gonna be
Dope

Dope
Yugh

Canon graph · the gyre

seven entries on a vortex · the waist is safe passage

full track · 4:42 · 192k AAC
The canon graph, drawn by lantern-lightSeven mythology nodes on a dark field. Selecting an annotated lyric line carries a lantern to the nodes that line resolves against; nearby nodes are dimly lit and the rest stay in shadow.fortresshibernationthe doublesafe passagenightmarehumourordinary

The readings

Each has the two fields the layer returns for any material: what it feels like from inside, and what it does in the system.

Eyes, front and back

Hypervigilance played as swagger — the boast of someone who cannot be crept up on, which is also the confession of someone who has been.

The fortress posture: protection through total watchfulness. Note the first words are both ways — the track’s original title was Both Ways x Dope. The doubling is in the name before it is in the writing.

A moat grave

A disposal image, tossed off in passing. Nasty, funny, gone in a bar.

A moat is the water around a fortress. The guarded-heart architecture keeps surfacing as literal geography without being invoked on purpose — which is what recurrence looks like when it is real rather than decided.

Hope that I don’t wake

The threat isn’t attack. It’s waking. The monster is dormant, and the danger is that it stops being dormant.

The strongest hit in the track. In the canon there is a figure for a self placed deliberately out of reach in order to survive — a heart put into hibernation. The sleeping monster and the hibernating heart are the same entity, described from outside and from inside. The song does not know it is saying this.

Byrgenwerth

A Bloodborne reference: the scholars who sought more eyes in order to see more, and were destroyed by what they saw.

Read against the opening line this is a structural rhyme, not a flex. The track begins with eyes as paranoia and returns to eyes as forbidden insight. Vigilance and the appetite for knowing too much are the same hunger — one of the graph’s recurring inversions.

Lose yourself to the pyre

Sounds like the most violent passage in the song — immolation, sulfur, ash.

It is not a killing, it is a rite: leave behind all your earthly desires / see your soul reborn. Cremation, not murder — the victim is improved. The layer flags this as the dissolution-and-rebirth gesture arriving in the register of a threat.

Gotta go through hell

Reads as a standard hardship line. Every rapper has one.

This is the thesis of the entire mythology, stated literally, four times in a row. The founding formulation is: not escaping darkness, not glorifying it, not being defeated by it — walking through it. Here it is, undisguised, in a comedy monster song. Nobody put it there deliberately.

Cooking in the kitchen · sunrise

The energy turns domestic and bright — cooking, coffee, morning.

A deliberate collapse of scale: astral disaster down to breakfast. That drop is the humour register the project uses as counterweight. And sunrise is the resolution condition of the whole nocturnal frame the track borrows from — you survive the night by reaching daylight.

So I’m gonna be — dope

A shrug of an ending. Almost anticlimactic after cosmic horror.

After collapse, passage and rebirth, the arrival is self-determination in the plainest available word. The catalogue’s namesake animal is defined as ordinary until it decides to matter. The track spends four minutes as an astral disaster and lands on dope. The scale drop is the character.

A note on how that diagram looks, because it is the shortest available demonstration of the argument. A relation graph would normally be drawn the way every tool draws one: bright nodes, even lighting, everything legible at once. This one isn’t. It sits on a dark field, most of it stays in shadow, and selecting a line carries a small light to the region that line resolves against — nodes just outside the reach go dim rather than dark, and the rest you have to trust are there.

That wasn’t an aesthetic preference. The graph’s own hub node is passage through darkness with a light you carry, and the mythology’s oldest recurring object is a lantern. A map of this particular body of work cannot honestly be evenly lit — even illumination would contradict the thing being mapped. The plainest mark on the whole diagram is the node called ordinary, for the same reason: the canon defines its namesake animal as ordinary until it decides to matter.

The shape is derived too, and this is the part I’d point a sceptic at first. The entries are strung on a vortex whose radius contracts to a throat and opens again — and the node sitting at the throat is safe passage. I didn’t put it there for the metaphor. Safe passage carries five of the graph’s nine relations, so it is the narrowest point by measurement, and the layout contracts toward whatever the topology routes through. That the most-connected node in a mythology about going through things turns out to be the place the shape narrows is not a flourish. It fell out of counting edges.

Any generic graph tool would have given me circles on a plane. The layer told me what the picture had to be, down to where it narrows — and that is the difference I am trying to describe.

Read straight through, that’s a monster brag with a redemption turn. A good one, but nothing unusual.

Read against the graph, it’s the whole dissolution-and-return sequence in miniature: hypervigilance, a sleeping thing that must not wake, escalation to cosmic scale, fire that purifies rather than kills, the thesis stated four times, a collapse from astral horror down to a kitchen, sunrise, then a plain declaration of self-determination landing on the most ordinary word available.

I did not write it that way on purpose. That’s the entire point — the graph found the shape, and the shape was already load-bearing.

Inspector · why this isn’t apophenia

The obvious objection: a sufficiently motivated reader finds any pattern in any text, and a language model is a very motivated reader. Fair. Three things separate this from a horoscope.

The graph predates the reading. The canon entries these resolve against were written months earlier, from different material, for a different purpose. The reading is a lookup against a fixed structure, not a structure fitted to a text.

It produces falsifiable misses. Plenty of lines in this track return nothing — no resonance, no function. A framework that illuminated every line equally would be illuminating none of them. The silence is the control.

It rejects. The same layer has killed proposals of mine on structural grounds, including work I liked. A framework that only validates is doing no work; the value is entirely in what it refuses.

What the graph then produced

The reason this is more than self-flattery is that the graph became an input to systems that make things.

Two recurring characters in our video work were derived rather than designed. One is a hooded figure carrying a lantern — straight from the passage function, made literal: the light you carry is small, and you go anyway. The other is a near-black, iridescent, entirely deadpan performer, from the founding emotional promise of the project — slightly disturbed, yet soothing — and the electronic-goth lineage the music descends from. Neither is a mascot somebody sketched. Each traces to a specific canon entry, and the trace is checkable by someone who isn’t me.

The rules they carry come from the same place: the lantern is never absent from frame; its amber is the only warm light in any shot that figure appears in; the other character’s purple-teal sheen never transfers to him. Those read as art direction. They’re inherited constraints.

Inspector · the rejection that proved it

We ran twenty candidate visual styles through an adversarial review — a fresh reviewer with no stake in the proposals, judging against the graph rather than against taste.

One was killed outright: well-argued, would have looked good, and failed on a structural collision between subject and style that no palette adjustment could fix. More useful was a set-level finding I hadn’t seen and wouldn’t have — the dark half of the set drew on public traditions and was therefore owned, while the comic half drew on specific living creators’ signatures and was therefore borrowed. Same body of work, two provenance classes, invisible until something checked.

You cannot get that critique from taste. Taste says “I like this one.” It requires a fixed reference the work is measured against — which is the argument for writing the graph down.

The part that matters most: it says no

The instrument can tell you your material won’t support this yet.

That verdict isn’t a failure mode — it’s the reason to trust the other verdict. A body of work needs enough pieces, made over enough time, with enough variance, before recurrence can be told apart from habit or coincidence. If you’ve made four things in one year in one mode, a mythology layer will find your influences rather than your structure, and it should say so rather than dress your influences up as a personal cosmology.

It’s also the honest answer to why the free instrument stops where it does. It walks you to the graph and the verdict and then stops on purpose. Everything past that — the forces organising the graph, what the recurring figures actually do, the structures they form — is the full instrument, and it’s paid. I’d rather say that here than have you discover it.

What I know, and what I don’t

  • The evidence is n=1. I built the instrument and I’ve run it on my own catalogue. That is exactly as weak as it sounds, and it’s the reason for this piece.
  • It has never been properly road-tested by an artist working alone, on material I know nothing about, with no shared context to lean on.
  • It needs a frontier-tier model. On weaker models the interview degrades into agreement, which produces a graph that flatters and therefore can’t reject anything.
  • I don’t know whether the structure generalises, or whether I’ve built a very precise instrument for reading exactly one person. Finding out is the only reason to hand it to anyone.

The ask: break it

20 free places · then it closes

Mythwright is in private beta. The first twenty people to run it get the full instrument — not the free tier, the whole thing: the forces organising your graph, what your recurring figures actually do, the structures they form. That normally sits behind the paywall.

You are not getting it for free. You are paying with the report.

I’d rather say that at the top than have you find it at the bottom. I need to know what this instrument does in hands that aren’t mine, and there is no other way to find out — twenty runs I can actually read is worth more to me than twenty licence fees. So the data isn’t a courtesy you extend afterwards. It’s the price, and it’s the whole price.

  1. 01Claim a place, run the interview

    Two sittings, in two separate sessions — the audit pass is not optional. You need a frontier-tier model and a real body of work behind you.

  2. 02Send the wrap-up — this is the price

    The instrument ends by generating a structured report of the run. You send it back. Not a favour, not optional, not “if you get a chance”: this is the payment, and skipping it means you took the free tier and kept it.

  3. 03Get the full instrument

    On receipt. Not automated — I read every one, which is the point of running a beta this small.

I want to know where it fails: where it flatters you, where it loses the thread, where the verdict feels wrong, and whether the graph tells you anything you couldn’t have told me yourself.

What the wrap-up contains

  1. Which model you ran it on, and its version. The single most useful field — the instrument needs frontier-tier reasoning, and knowing exactly where it degrades is what lets me fix it.
  2. The shape of your corpus — how many pieces, over how long, in what medium. Titles aren’t needed.
  3. The graph you ended with, nodes and edges, as the instrument produced it.
  4. The verdict, and the reason it gave.
  5. Where it stalled — any point the interview lost the thread, or the model started agreeing with you instead of testing you.
  6. What returned nothing. The questions that produced dead air matter as much as the ones that landed.
  7. Where you think the audit was wrong. Say so plainly; I’d rather have the disagreement than a polite score.
  8. The one thing you didn’t already know — or “nothing,” if that’s the honest answer. “Nothing” is the most valuable response in the whole report, and it costs you nothing to send it.

Especially useful: if it tells you your material can’t support a mythology layer yet. I need to know whether that lands as useful information or as a door closing.

Claim a place

Two minutes, one formTwenty places, then it closes. US residents this round; your place holds for 21 days. Tell me what you make and which model you’d run it on — that’s the whole application.

Exactly what changes hands, so there are no surprises: the structured report is required — that’s the payment. Your raw session log is requested but optional; it’s much richer data and it’s also your unreleased work, so redact anything you want or send nothing at all. Everything received goes into revising the instrument and nowhere else: not published, not quoted, not shown to other testers, not used as marketing. Your work stays yours — which is rather the point of the whole exercise. One timing term so nobody is caught out: a claimed place holds for 21 days. If the run hasn’t happened by then the place returns to the pool, because twenty is a real ceiling and a place sitting idle is one somebody else could have used. Need longer? Say so and you’ll have it — the deadline exists to keep the cohort moving, not to catch anyone out.

The page is also an output

It would be inconsistent to argue for a written constraint set and then design the page arguing for it by feel. So this page was built from the same graph — the palette, the typefaces and the diagram all resolve against canon entries rather than against my preference on the day, and the same rules that govern the video characters govern the surface you’re reading. The blend is deliberately partial, somewhere near twenty percent wet: enough that it’s recognisably the same world, not enough that atmosphere starts doing the arguing. An essay claiming a framework produces restraint has to demonstrate restraint. There are two versions of it for the same reason there are two ends to the route it describes — the control for that is in the top corner.

Inspector · the colours, and where each one comes from

You are on the lantern ground — inside the passage. These are the values in force right now.

  • ground #0c0b0f
  • brass #d7c56f
  • amber #f0a63c
  • verdigris #74b49b
  • oxblood #b85b64
  • ink #f0ead9

The ground is dark on purpose, and it is not black. The passage function says darkness is a route rather than a condition, so the page can’t read as void — a true black would stage the dark as the subject. It’s a near-black carrying olive, the colour of somewhere with air in it. Amber here is emitted: a flame, and the only warm light in frame.

You are on the sunrise ground — through it, and out the other side. These are the values in force right now.

  • ground #f2e9d9
  • brass #6f6118
  • burnt amber #8a4d10
  • verdigris #1f5a48
  • oxblood #7b2f37
  • ink #191810

The ground is light, and it is not white. This is the kitchen at sunrise, which is where the track actually lands — so it’s warm linen carrying the same olive, not paper stock. A true white would be as much of a lie as a true black: it would stage arrival as a blank. Amber here is absorbed: burnt pigment, marking where you have been rather than where the light is, because nothing on this ground needs a lantern.

There are two grounds, and they are the two ends of the same route. The switch in the corner isn’t a sun and a moon; it says lantern and sunrise, because that’s what it changes. The dark ground is inside the passage: you carry a small light and see one thing at a time. The light ground is where the track actually lands — the scale collapses out of astral horror down to a kitchen, the sun comes up, and the last word is the most ordinary one available. So the light theme isn’t the page with the lights turned on. It’s the other terminus, and it is warm linen rather than white for the same reason the dark one isn’t black: neither end of this is a blank.

Amber changes state between the two. On the dark ground it is emitted — a flame, the only warm light in frame. On the light ground there is nothing left for a lantern to do, so the same hue is read as pigment: burnt amber, absorbed rather than glowing, marking where you have been instead of where the light is. One colour, two physical behaviours, which is the distinction the mythology draws between being in the dark and having come through it.

The diagram stays dark in both. That’s the one deliberate exception on the page, and it’s the honest one: the instrument looks into the passage. Wherever you’re standing when you read this, the graph is a window back into the part you go through, so it keeps its own night and its own lamp.

Brass and amber are the lantern, and they are rationed. The hooded figure’s inherited rule is that its amber is the only warm light in any frame it appears in. That rule is honoured literally here: amber appears at exactly one place at a time — the lit node in the diagram — and brass, its cooled form, marks only structural voices, the labels that tell you where you are. Nothing decorative is warm. If a section feels like it’s glowing, that’s the lamp, and the lamp is pointing at something.

Verdigris and oxblood belong to the other character — the deadpan iridescent performer, whose sheen the constraint set forbids from transferring to the lantern figure. So they never touch the warm channel. They carry the technical register instead: the inspector panels, the exchange, the specification. The two colour families in this page are the two figures, kept apart by the same rule that keeps them apart on camera.

The typefaces are three reading registers, which is the page’s whole architecture. A serif display face for the claim, a humanist sans for the argument at musician level, and a battered typewriter face for anything that is evidence — field labels, the diagram’s captions, the terms of the trade, the footer. That last face comes from the glitch-decay register of the Goose visual canon, where it means recovered document. Wherever it appears on this page, you’re looking at instrumentation rather than prose.

None of that is a mood board. Each line above is a lookup, and any of them can be checked against the diagram — which is the only claim this page is really making about itself.