Publishing is turning what was collected into finished text for readers: a channel post, a mailing issue, a feed entry. Everything here is built on one promise: nothing goes out without your approval. Even when the text is ready, it first waits for you.
What a publication is
A publication is a news draft assembled from the material of one event or a whole story. It has a title, a subtitle, the text, the source list and the language — the one you write in.
How the draft is prepared
The draft is written from the collected material and in your style: you set the language, the tone (neutral, friendly or press-release-like), the length and, when needed, a sample text to aim at.
Then comes the main safeguard. Every quote is verified on the server: it must be found in the source material. Invented quotes are discarded, and when not one is confirmed, the draft is not created at all. The product honestly answers that there is nothing to write from this material, instead of making up a story.
The “generated” signature and the source list are added by the product itself — that part is not given to the model, so it cannot “forget” to append them.
The finished draft text can be adjusted with your own Python code — for example, brought to your own formatting standard. When the code breaks, the draft is not created at all: unverified text does not go out.
The human check
The finished draft waits for you on the “Published” screen with its states: draft, approved, publishing, published, error, rejected, skipped. Sending happens only after you tell the agent “publish”. You can also approve but hold the sending for now — when you want to keep the text until the right moment.
A rejected draft does not come back on its own: it is closed for good, and a rework creates a new version.
Six publishing targets
- Telegram channel — a post into your channel with links and formatting.
- Email — a mailing issue: the title becomes the letter’s subject, and the text arrives both as plain text and as markup.
- RSS feed — the publication is not sent anywhere: it itself becomes the feed readers take from: Reader Feeds.
- Webhook — the publication’s data goes to your system at an address, with a signature.
- A file folder — the finished text file is dropped into a folder together with the published index. A ready option for a static site: take the files and publish as you like.
- Your own target — the publication is sent by your own Python code: useful for your own site-management system or a service not on the list. An honest detail: unpublishing by such code is performed by the code itself, if you taught it to.
Versions and republication
A rework does not overwrite the former text: a new version is created and the history is kept. Useful when a story develops: you see what was in the first publication and what changed in the next.
Unpublishing
Sometimes a published item must be taken back. Here it matters not to overpromise, so honestly, per target:
- Telegram — the message is deleted.
- The file folder — the file disappears, the index updates.
- The RSS feed — rebuilds itself: the entry disappears from the feed on the next read.
- Email and a webhook cannot be retracted. The letter is already with the reader, the data already went into your system. The product says so plainly in the answer instead of pretending it “removed” it.
- Your own target — unpublishing is done by your code, if you provided for it; the product is not answerable for someone else’s actions and honestly warns about it.
An unpublished item keeps its text and the unpublishing mark, is not sent again and no longer gets into feeds.
Preparation by rule or by schedule
Drafts can be prepared in two ways, and both keep your approval:
- By rule — an event matched a rule, and a draft is assembled from its material right away. Fits important topics where the reaction must be fast.
- By schedule — say, every morning: the draft is assembled from all the window’s matching stories. Fits regular issues.
A manual run does not shift the schedule: when you asked for a draft now, the next planned one arrives at its own time.
Target verification
A publishing target can be verified with a test send — a real one: the same route, the same bot, the same address. That way you know in advance that what reaches the readers is exactly what you expect.
Limits
- There is no autonomous publishing. The product does not release news on its own, however much one wants it to “work without me”.
- Without confirmed quotes there is no draft. This is deliberate strictness: better the news comes out later than with an invented phrase.
Next → Reader Feeds