From a single prompt describing the issue's theme and sections, Press handles the structural difference between a single standalone work and a periodical: issue-based layout, recurring sections, and the identifier conventions periodicals use instead of a book's. Given an optional source manuscript or back issue, it uses that as the basis instead. Trained on periodical conventions specifically, so an issue is drafted with the right section and masthead structure rather than being treated as a single long document. It is an operational reference, not an offer or investment content.
Press is not a long document with section headings added. It is trained specifically on periodical conventions — issue-based layout, recurring sections, masthead and the identifier conventions a magazine or journal uses instead of a book's — so a periodical draft comes back as an issue, not as a single standalone work.
Press returns a finished periodical draft in the shape a magazine or journal needs — issue-based, sectioned, and carrying the identifier conventions of a periodical — rather than a single long document that still needs a layout pass.
The draft is laid out as an issue — a defined set of contents with its own front matter and internal ordering — rather than as a single standalone work. The issue is the unit, not the article.
Sections that recur issue after issue — columns, features, reviews, editorial — are drafted with the recurring structure a periodical relies on, rather than each issue being assembled from scratch as an unrelated document.
The draft carries the identifier conventions periodicals use — ISSN rather than ISBN, and the metadata a periodical needs in order to be catalogued correctly by retailers and libraries — rather than a book's conventions applied to a magazine.
If you have an existing manuscript or a back issue you would rather build from, upload it alongside the prompt. Press returns the same issue-structured periodical draft, built from that source rather than from a fresh theme.
Press is trained on periodical conventions specifically, so an issue is drafted with the right section and masthead structure rather than being treated as a single long document. See usage & pricing for per-model unit costs.
Press follows the same single-prompt pattern as every model built on PUBXX 1.0: one instruction goes in — describing the issue's theme and sections, or naming an optional uploaded source to build from — the engine drafts, and Press shapes that draft into an issue-structured periodical. There is no multi-step chain to manage, and no required human pass before a draft is returned.
By default, a single prompt describing the issue's theme and sections is the only input. To build from an existing manuscript or back issue instead, that source can be uploaded alongside it.
The core engine produces the structural and language-consistent base draft that Press then shapes into the periodical format.
Press applies the issue-based layout, recurring sections and periodical identifier conventions, and returns a complete issue-structured draft.
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.
Press does not solve issue structure, 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 periodical format.
PUBXX 1.0 handles the parts of production that are skilled but repetitive: structural and language consistency, formatting logic and metadata handling. Press is what that engine becomes when specialised for the periodical — a format-specific model, built on a shared core, not a separate, unrelated tool.
Press is one of five named models sharing the same PUBXX 1.0 engine. See the full engine breakdown for how the others work.
Press 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.
Cost reduction is company-reported, against an all-human workflow, and is not a revenue claim. Press's own track record on SEW Capital's catalogue is not evidence of how any individual future issue will perform.
Press is the natural model for any publisher producing a periodical — a magazine, a journal, a newsletter with an issue structure — whether originating from a theme or building from a back issue. It is not tied to any single platform or token; it is the infrastructure underneath SEW Capital's periodical output generally.
SEW Capital owns 100% of PUBXX 1.0 Press — 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 Press 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.
This page describes PUBXX 1.0 Press, the magazine and journal 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 issue, 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.
We can take you through how the model structures an issue, what a finished periodical draft contains, and how it fits the shared engine underneath. This is documentation, not a pitch.
hello@sewcapital.co.uk See usage & pricing