Model insight · built on PUBXX 1.0 Audio drama format Single prompt

Drama is the audio-drama model built on PUBXX 1.0 — one prompt returns a dramatized, multi-voice, episodic production.

From a single prompt describing the idea, Drama drafts a dramatized, multi-voice production structured for serialized, episode-by-episode release, rather than a single straight narration. Given an optional source manuscript, it adapts that existing work instead of originating new material. Because it is built for serialization, Drama's output is structured in episodes from the start, rather than being a single file split up afterwards. It is an operational reference, not an offer or investment content.

1
Format — audio drama
1 prompt
From idea to finished draft
Optional
Source manuscript for adaptation
Episodic
Serialized structure from the start
Overview

One model, specialised to serialized audio drama.

Drama is not a straight narration with a second voice added. It is trained specifically on dramatized, multi-voice, serialized audio — the episode structure, the multi-character performance and the continuity a serialized audio drama needs — so an audio drama draft comes back as episodes, not as a single file that still needs to be split and re-performed.

Dramatized
Multi-voice performance, not straight narration
Serialized
Episode structure from the start
Continuous
Character and story continuity across episodes
Prompt-first
A source manuscript is optional, not required
What it produces

A complete set of episodic, multi-voice audio drafts.

Drama returns a finished audio-drama draft in the shape a serialized audio channel expects — dramatized, multi-voice and structured in episodes — rather than a single-file recording that still needs a producer.

Multi-voice performance

Dramatized, not narrated

The draft is performed with multiple distinct voices — a dramatized production, not a single narrator reading straight through. The performance carries the dialogue and action of the work, rather than reading it flat.

Dramatized from the first draft

Episode structure

Serialized from the start

The draft is structured in episodes from the beginning — each with its own arc and continuity to the next — rather than being produced as a single file and divided afterwards. Serialization is a first-class property, not a post-production step.

Episodic from the first draft

Continuity

Across the series

Character continuity, story continuity and voice consistency are held across episodes, so the series does not drift between instalments. The model is built for an ongoing series, not a single one-off production.

Built for the series, not just the pilot

Source adaptation

Optional upload

If you have an existing manuscript you would rather adapt than originate, upload it alongside the prompt. Drama returns the same episodic, multi-voice production, adapted from that source rather than from a fresh draft.

Existing work, same output

Drama is trained specifically on dramatized, multi-voice, serialized audio, distinct from the straight narration the Narrate model performs. See usage & pricing for per-model unit costs.

How it works

A single prompt in, a finished episodic audio-drama draft out.

Drama follows the same single-prompt pattern as every model built on PUBXX 1.0: one instruction goes in — describing an idea, or naming an optional uploaded source to adapt — the engine drafts, and Drama shapes that draft into a dramatized, multi-voice, episodic production. There is no multi-step chain to manage, and no required human pass before a draft is returned.

01

A prompt goes in — a source file is optional

By default, a single prompt describing the idea is the only input. To adapt an existing work instead, a source manuscript can be uploaded alongside it.

02

PUBXX 1.0 drafts

The core engine produces the structural and language-consistent base draft that Drama then shapes into the audio-drama format.

03

Drama finishes the draft

Drama applies the multi-voice performance and episodic structure, and returns a complete set of episodic audio-drama drafts.

Editorial review is available as a separate, optional step after a draft is returned, priced on its own — it is not part of the single-prompt generation described above. See usage & pricing for details.

The engine underneath

Drama runs on PUBXX 1.0, the shared engine beneath all five models.

Drama does not solve continuity, formatting logic and metadata from nothing. It inherits those from PUBXX 1.0, the shared drafting and consistency layer that every named model is built on — and specialises that layer for the audio-drama format.

Shared engine, format-specific model

PUBXX 1.0 handles the parts of production that are skilled but repetitive: structural and language consistency, formatting logic and metadata handling. Drama is what that engine becomes when specialised for serialized audio drama — a format-specific model, built on a shared core, not a separate, unrelated tool.

Shared
One drafting & consistency layer
Format-specific
Multi-voice, episodic, continuous
Single prompt
Start to finished draft
Source optional
Originate from a prompt, or adapt an upload

Drama is one of five named models sharing the same PUBXX 1.0 engine. See the full engine breakdown for how the others work.

Quality

Top-specification, error-free, to-date drafts.

Drama is built to produce drafts at a consistency that hand assembly across separate tools cannot sustain — a consistency the shared PUBXX 1.0 engine is designed to keep, rather than a property of any single model in isolation.

Top-spec
Error-free, to-date draft quality
Multi-voice
Dramatized performance
Serialized
Episode structure from the start
Up to 80%
Lower production cost vs. all-human

Cost reduction is company-reported, against an all-human workflow, and is not a revenue claim. Drama's own track record on SEW Capital's catalogue is not evidence of how any individual future series will perform.

Who it's for

Creators building a series, not just a one-off.

Drama is the natural model for any creator with a series, a story world or genre fiction that benefits from serialized, multi-voice production. It is not tied to any single platform or token; it is the infrastructure underneath SEW Capital's audio-drama output generally.

Ownership

PUBXX 1.0 Drama is owned outright by SEW Capital.

SEW Capital owns 100% of PUBXX 1.0 Drama — the model, the engine underneath it, and the IP and output the model generates. No token confers any ownership of the model, the engine, or their output.

This page describes the Drama model as infrastructure in its own right. It does not describe, and should not be read as describing, the utility of any specific token or the mechanics of any specific platform that may use this model's output.

100%
Owned by SEW Capital
1 of 5
Models under common ownership
0%
Ownership conferred by any token
Independent
Of any single platform's workflow
Scope

What this insight is — and what it isn't.

Descriptive, by design

This page describes PUBXX 1.0 Drama, the audio-drama model built on SEW Capital's AI engine. It is an operational reference. It is not a prospectus, not an offer, not a solicitation, and not a recommendation to acquire, hold or dispose of any token.

Not tied to a platform or token. This page intentionally does not describe how any specific platform sequences its workflow, nor the utility, mechanics or settlement of any specific token. Those are documented separately, elsewhere in the insights list, and token usage pricing for this model is set out on the usage & pricing page.

Not a forecast. The figures on this page describe the model's design and SEW Capital's own catalogue performance to date. They are not evidence of how any individual future title, format or language edition will perform.

We do not publish price information, return expectations, yield, appreciation claims, or any statement of value for any token on this page. Nothing here should be read as financial, legal or tax advice.

Want PUBXX 1.0 Drama walked through?

We can take you through how the model structures a series, what a finished episodic draft contains, and how it fits the shared engine underneath. This is documentation, not a pitch.

hello@sewcapital.co.uk See usage & pricing