A station for
impossible records.

Why would anyone build this?

Two questions, in order of age:

Can Lyria be cornered past its conventional arranger priors into music that feels genuinely undiscovered?

Lyria is very good at producing competent, fully-arranged, vaguely cinematic music from almost any request. That competence is exactly the problem. The research programme is adversarial: identify what the model reaches for by default, close those escape routes, and leave one small, consequential relationship alive that it has to actually think about. Not "make a banger" — corner the instrument.

Can geographically separated people meet in a musical space that did not exist until they transmitted into it?

A radio station is a shared room that nobody owns. Undertow extends that: the room's music only exists because people called into it. That is the social half of the experiment, and it is younger and less proven than the adversarial half.

Both of these are open questions. This manual describes a working instrument and its direction — not a settled result.

How do I play with it?

Live now, verified 9 September 2026: shared listening, calls, corrections, personal tape replay, the transmission log and anonymous sleeve marks. Later: optional sign-in and public caller credit. Contributions are preview-only; RealTime generation remains disabled.

1. Tune in. Use the room menu. Sound starts when you choose it. The stream follows the station's broadcast clock — you hear what the station is playing, at the point it plays it. It is not a personalized feed.
2. Read the record. The current transmission shows its title, the originating call, the DJ's stated intention and the retained musical brief. Inspection is encouraged. The public facts about what aired are not hidden behind a login; the exact provider trace and receipts remain private operator evidence.
3. Open the line. Give the DJ something to find — a sound, a story, a feeling you cannot name. Up to 4,096 characters. An ephemeral session cookie limits queue abuse; no name, account or personal profile is attached to an anonymous call.
4. Return to the conversation. The bubble near the booth quietly shows waiting, DJ thinking, generation, and new replies or outcomes. Open it again from the room or the menu. Your exact words and retained DJ replies stay together; expand for earlier exchanges. Back to room dismisses the surface without cancelling work. Drafts survive reload in this tab after access is confirmed. An uncertain delivery stays uncertain until a receipt arrives, with no automatic resend. Each result recording keeps playback, inspection, correction and Bring Back within reach. If an attempt stops without a recording, its charred sleeve and failure receipt remain in the room and conversation.
5. Understand influence. Your call is influence, not control. The resident DJ preserves your commitments and makes a decision within the freedom you leave open. Direct to Lyria is the explicit caller-authored route. Some calls become the whole record. Some become one grain of it. Some never reach sound at all — and if the provider refuses a call, that refusal is retained as exactly what happened, not hidden.
6. Correct it. A correction can revisit a previous interpretation. Corrections are parent-linked to the calls they answer, so the lineage stays readable.
7. What just played? The recent shelf follows actual airtime, newest first; two broadcasts of one recording remain two events. The public tape rack holds listener-eligible recordings; airtime history separately records when they were transmitted. The crates contain the separate searchable collection. Pick up a record in either place to play it, mark it, ask for its idea back, or inspect its story.
8. Play this. Hear the exact retained audio here. Loading a tape does not start it. Local replay creates no new transmission, generation or archive entry, and leaves the live station running. Listen live returns you to the station.
9. Leave a mark. Every record has two independent marks: ❤️ and 💩. Keep either, both, or neither; tapping one never clears the other. They stay on that recording through live listening, replay and inspection. Older unambiguous marks seed this current state without exposing the retired vocabulary; a later tap always wins and the underlying evidence remains intact. Bring Back opens a small space for your direction: what should the DJ keep, lose, push further, or understand differently? It asks for a new piece from that record’s lineage. “That’s not what I meant” corrects an earlier interpretation; a revisit gives the idea another life. Reactions never train the DJ, change taste, schedule airtime, trigger a retry or authorize release.
10. Share a record. Share opens your device’s share sheet or copies a canonical record link. A fresh visitor opens that same public record and chooses whether to play it. Private or withdrawn recordings stay unavailable.
11. Bring this back. Ask the DJ to revisit the eligible musical idea linked to that record. This is an influence request, not a promise to rebroadcast the same audio. The station checks the relationship again when you ask.

Optional sign-in and public caller credit are not public yet. Anonymous sleeve marks are live now. When credited identity arrives, credit on a public record will stay the caller's choice, every time.

What happens when I call in?

One retained chain. Its public and private depths are explicit:

1. CALLERyour text, retained exactly as sent
2. AUTHORSHIPresident DJ / explicit direct to Lyria
3. MUSIC DIRECTIONcurrent DJ decision, or exact caller score on DIRECT
4. LYRIA 3.5at most one authorized paid attempt after routing
5. PROVIDER RESULTrecording, refusal or failure, retained exactly
6. TRANSMISSIONgoes on air, or doesn't — honestly labelled
7. TAPE / ARCHIVEeligible recordings publicly; full retained chain privately
8. RETURNan optional later linked call, never a hidden retry

You choose who authors the music direction. Preservation describes what must survive; it never switches the DJ off:

The DJ always steers. That does not mean adding something you never asked for.

Older PRESERVE, CONSTRAIN and INTERPRET records keep their original history. They do not define new authorship choices. The companion law:

Undertow should have a recognisable hand without having a recognisable recipe.

Why does some of it get weird — or fail?

Honestly, because the instrument is stochastic and the bar is high. Specifics:

Lyria is stochastic.

Two near-identical requests can produce different worlds. Neither is a bug; that variance is part of what is being studied.

Provider refusals happen.

Lyria runs behind Google's own filters. When a call is refused, that is a provider outcome — retained as exactly what happened, never retried, never laundered into "moderation". Undertow makes no semantic judgement about your call's musical meaning; deterministic authorization, privacy, transport, resource and tool-use boundaries still apply. The provider's decision is the provider's.

Technical obedience can still be beige.

A call can be followed to the letter and produce music with nothing at stake. Adherence and quality are different questions: automated listening supplies descriptive and adherence evidence; Adrian alone decides whether the music is any good.

Smartie vomit.

The named failure mode: conventional arranger reassurance — extra percussion, pads, arpeggios, harmonic bloom, sections/build/drop/climax, decorative novelty, generic journey — especially when it collapses the possibility of the small world the caller actually asked for. It is a gradient, not a binary; even keepers can have a little of it creeping in at the edges.

One shot.

A successfully routed call may reach one authorized paid attempt, never more than one. Success, provider refusal or ambiguous failure consumes that attempt; there is no automatic retry, and the station never selects a substitute candidate. If the result is beige, that beige is the honest record of what the call produced.

Failures are kept.

Refusals, ugly tracks, dead ends — they are evidence, not embarrassments. Nothing gets quietly deleted to make the station look better than it is.

What is it trying to sound like?

Not a genre. A set of current north stars — a direction the station steers by, and emphatically not a claim that any of them has been achieved:

• Underground / rebel optimism
• Bodily invitation
• Exploration and adventure
• Unity without flattening difference
• Celebration in shared nonspace
• Strange warmth
• Physical consequence — a kilowatt economy
• Repetition acquiring meaning before novelty
• Coherent unknownness, not decorative weirdness

Push the fucking button and see what happens.

You don't know where you are yet. Come in anyway.

We can meet somewhere that doesn't exist yet.

When Detroit, Berlin or New York get mentioned around here, they describe lineage — where the idea of a station as an instrument came from — rather than instructions to imitate a named artist.

What is actually under the hood?

The short version, readable in about twenty seconds:

1. YOUthe public listening room, at the station's address
2. THE EDGECloudflare Pages; exact route allowlists; server-side studio authority, never credentials in public JS
3. THE STUDIOan authenticated tunnel carrying scoped projections, calls and explicit listener writes
4. THE COREPython and SQLite; a persistent producer; the broadcast clock
5. THE DJthe resident DJ decides; direct is the caller's explicit bypass
6. LYRIA 3.5full-song generation via the Gemini Developer API
7. THE RECORDprovider-original audio, response blocks, receipts, hashes
8. THE ARCHIVEevery recording playable with its full chain, in the operator room

Some load-bearing details:

• At most one authorized paid attempt after successful routing. A call can still fail before generation. Every paid attempt is reserved durably before the provider is called, inside a hard total spending cap; success, refusal or ambiguous failure consumes it. There is no automatic retry.
• Provider-original audio is retained byte-exact — the MP3 you hear on an aired transmission is the provider's own file, not a re-encode.
• Every ordered response block is retained — audio and the model's returned text (structure and lyric markers), indexed exactly as it came back.
• Automated listening describes; it never judges. Machine observations of a recording are descriptive and adherence evidence only. They cannot award taste, gate airtime on predicted quality, or train anything.
• Human taste is one person. Adrian listens and marks records KEEP / MAYBE / NO. That is the only taste authority in the station.
• Programme state is separate from taste. A shared broadcast clock schedules eligible retained recordings. Airtime is not a KEEP verdict.
• The operator room is private — every retained recording stays playable there with its call, DJ interpretation, exact provider request and response, receipts, and selection and airtime history. Not every retained recording is public: listener eligibility and actual airtime are distinct; the wider private archive stays local until rights and privacy review say otherwise.
• Public JavaScript carries no station credentials. The edge uses a server-side studio secret for an exact listener-route allowlist. It forwards the necessary fairness cookie, not caller IPs, user agents or operator tokens.
• Analytics require opt-in. Undertow’s custom GA4 events exclude caller/DJ/provider text and recording or request IDs. No caller text or free-text content is deliberately sent in those custom events. Google nevertheless creates client/session identifiers after opt-in; this is not identifier-free measurement. Consent withdrawal and consent expiry still need remediation. This manual page does not load GA4 or Undertow analytics; ordinary CDN/security request handling is separate.

Who decides what

The station separates authorities that most products blur together. If you remember one table, remember this one:

What Undertow does NOT do

Explicitly, because the omissions are the design:

• Does not semantically moderate musical validity — no classifier decides your call is "too weird" or "not musical enough".
• Does not use automated listeners as taste authority.
• Does not infer Adrian's taste from engagement, reactions or popularity.
• Does not let money buy KEEP, airtime or release.
• Does not rewrite caller text into sanitized public prose.
• Does not use audience reactions as automatic DJ training or programming authority.
• Does not claim a provider success means an artistic success.
• Does not retry ambiguous paid calls automatically.
• Does not hide failed generations or refusals from the evidence record.

Evidence and provenance

Undertow keeps an unusual amount of trace data, on principle. For a public transmission you can inspect a scoped projection on the record: the caller seed, route, DJ interpretation, final provider-bound musical brief, provider outcome, recording identity and duration, historical listening description as secondary evidence, and cost where available. Exact request and response bytes, receipts and the wider retained archive remain private operator evidence. Retention is not public release. Optional caller attribution is planned, not live.

Progressive disclosure, never evidentiary disappearance.

Depth is folded away, not removed. When something is missing, the station says it is missing — absence of evidence in a view is never presented as evidence of absence in the archive.

Why tapes, records, and impossible time travel?

The booth’s calendar is fixed at Friday, 29 August 1997. This is room mythology, never the date of a real transmission. The conversation bubble and station log sit to the left; performance is in the centre; transmitter accounting, contributions and contact with Adrian sit to the right. Remembered relationships live in the log. Your requests, replies and Bring Back exchanges stay in the conversation while your session has access; sign-in links your accepted history across visits. Drafts stay in this tab and restore only after access is confirmed. Every record keeps its own playback, return and inspection actions.

The silent television ordinarily plays retained period ads. Its rare interruptions and the half-seen human fragments are authored fiction, not audience activity or CCTV. A visit may contain none. Reduced motion suppresses the moving atmosphere; the hanging headphones have no cue function yet.

The room has a mythology, and the station is honest about where it starts. Vinyl is the current performance object. Tape is captured memory: choosing a public tape replays it only for you while the shared station continues. Asking the programme to return to an earlier thread is a new parent-linked call, not a replay, regeneration or retry. The recording deck makes the causal chain physical:

LIVE TRANSMISSION → RECORDING DECK → CASSETTE → ARCHIVE

Future dates, returned transmissions, impossible chronology — that is interface fiction, and it is labelled as fiction. It never fabricates a factual generation or play history. When a tape says it came back from a year that hasn't happened, the underlying record still knows exactly when it was really made.

Costs, support, and the human

Finding records uses paid generation machinery, and the station's design is to show its accounts: the transmitter drawer in the room is built to carry the live request-path figure behind the current transmission and the station-to-date provider accounting, with their basis and per-provider breakdown. When the accounting projection is not being served, the log says exactly that — "cost record unavailable" — rather than filling the space with a made-up number.

There is a contribution line on the station page — one-off, toward provider computation. It buys no airtime, no approval, no publication, no musical success and no control of the DJ; it is not connected to live payment yet, and when it is, that will still be true. Money never becomes taste.

The machine is a side effect. The person who built it — Adrian Wedd — works on strange systems, AI integration and adversarial evaluation, and takes real problems that refuse to fit a brief: bring him the problem ↗. That door and the station's ledger are deliberately separate.

For engineers and researchers

The deeper end. Everything below is scoped to its actual evidence — dated, surface-specific, and machine-observed unless a human is named.

Public reading first: the Lyria Chronicles are Adrian's written record of red-teaming Lyria 3 Pro — an earlier model on a different surface, and the lineage this station grew out of. Start with The Ghost of What I Am and The Interrogation. The station's source is private for now; what follows are its integration findings against lyria-3.5 full-song, via the Gemini Developer API's interactions surface (observed 2026-09-06/07, retained specimens):

• The complete response body is the evidence authority. Every ordered step and block — text and audio — is retained byte-exact with a JSON-pointer index. A convenience accessor that returns "the audio" is not evidence of everything the provider sent.
• Declared MIME and actual container are separate facts. A request for WAV on the tested route returned an MP3 container with audio/mpeg declared. The station stores the bytes unchanged and treats container identity as an observation, not a promise.
• The returned "structure" text is marker notation, not JSON. Across the retained corpus, the text blocks accompanying audio are section-type/occurrence markers — not the "JSON description of the song structure" the documentation describes.
• A/A stochasticity exceeds most A/B differences. Re-running the same prompt moves the output more than most deliberate prompt changes. Single-pair prompt comparisons are uninterpretable without a same-prompt baseline.
• Duration is controllable but not smoothly. Vague prompts land in quantized attractor basins; explicit second counts pin duration near a mechanism's content-natural length; over-stretching a world past its natural length collapses it rather than padding it.
• Positive exclusion beats bare negation — directionally. Naming an allowed category suppressed an instrument the corpus wanted to add; bare "no X" invited X's whole family in. Small sample, treated as direction, not law.
• Refusal is per-request stochastic. No format or content rule we found predicts an individual block; a restatement of identical content was refused where the original passed. So the station never auto-retries a refusal.
• Full-song and RealTime are different instruments. Full-song is a stateless HTTPS request; RealTime is a persistent bidirectional session with live controls. Findings do not transfer between them, and the station keeps RealTime paid execution disabled until its pricing and session exposure are bounded.

What the station still doesn't know

• No human has listened to most of the observation corpus — the findings above are machine-observed, and machine observation is not hearing.
• None of the transferable prompting candidates is house style; each becomes station behaviour only after Adrian accepts it on a fresh generation.
• RealTime's control surface — density, guidance, seed interactions — is unmeasured here, for the bounded-exposure reason above.
• Every finding is surface-specific: lyria-3.5 via the Gemini Developer API is not Lyria on any other route, and the Chronicles' 3 Pro results are a different instrument again.

The compiled atlas binds its model, origin and service inventory to source/configuration fingerprints. Tests reject stale compiled facts; dated deployment observations still require fresh runtime checks. Source presence is not proof of deployment, and neither a diagram nor a green test is proof of human listening.