Chains
Sourcing, filtering, writing, drafting, and publication, run end to end.
How chains work
- Sourcing runs first, then filtering over today (UTC).
- Then a halt: a wait before writing, 4 hours unless the form says otherwise.
- Skip halt ends every waiting halt; the next manager tick starts the next step.
- Then 1 writing job per top weighted unwritten summary, up to the fanout.
- Then 1 drafting job per written story: the backend draft, images and cover set.
- Then a halt per draft, 4 hours unless the form says otherwise.
- Then 1 publication job per draft.
- Each job keeps its own retries.
- A job that fails for good blocks its branch until you retry it.
Start chain
Writing waits after filtering, publication after drafting. 0 starts the step at once.
working...
Schedules
Chains the server starts on a timetable, at set times of day.
How schedules work
- A schedule starts 1 chain at each of its times, on the start date and every N days after it, up to the end date.
- Times and dates run in the server's timezone. Both dates are inclusive; no end date runs forever.
- The server checks every 30 seconds, so a chain starts within 30 seconds of its time.
- A time missed by more than 1 hour, such as during downtime, is skipped, not run late.
- Changing a time, a date, or the step, or enabling a schedule, plans the next run from now.
- Chains open the Chains page filtered to the chains a schedule started.
A chain starts at each time on every run day. Every 1 day runs daily; every 2 days runs on the start date, 2 days later, and so on.
working...
Jobs
Every job, newest first. Open Details for stages and the runtime log.
How jobs run
- The manager claims 1 job per poll, on its own clock.
- A new job waits for the next tick.
- Retry resumes a failed job at the stage that failed.
New job
working...
Summaries
Source articles the sourcing worker stored, with the weight filtering gave them.
About weight and chains
- Weight is 1 to 5, set by the filtering worker or by an edit here.
- "dropped" means filtering read the summary and kept none: a duplicate, or not worth writing.
- A dash means no filtering run has read it yet.
- Chain is the chain that owns the summary: the one whose sourcing stored it.
- During the halt after filtering, the fan out has not read weights yet: an edit here changes what gets written.
- A chain filters and writes only its own summaries; a chain that owns none uses its day.
Stories
Written stories, most recently written first.
About versions
- Each writing run adds a new story, so 1 summary can hold several versions.
- A retry of the same job replaces only that job's story.
- Publish needs a cover image.
Cover images
1 cover per story, most recently rendered first. Click one to see it full size.
How covers are made
- A model writes an HTML page from the finished article.
- A headless browser screenshots it at .
Fetched pages
The page cache the writing worker reads before fetching a URL.
About the cache
- Every fetch checks here first, so a URL is read once.
- Deleting a page makes the next fetch read it again.
Sources
BrightData collectors the sourcing worker runs.
New source
working...
| Collector | Inputs | Poll | Enabled | Actions | ||
|---|---|---|---|---|---|---|
Prompts
Article, image, and filtering prompts, with their variants.
How prompts resolve
- 3 prompts: article writes a story, image designs its images, filtering rates and deduplicates a day of summaries.
- Each resolves saved copy first and file second; an edit lands on the next run.
- A variant is a saved copy under another name, offered only for its own kind.
- 1 prompt per kind is primary: the one a run sends when its job names none.
- A disabled prompt is never primary.
- Plain ASCII only: an em dash in the context gets copied into a published story.
- Run needs a finished writing job to borrow research from.
| In use | Sends | Enabled | Chars | Note | Actions | |||
|---|---|---|---|---|---|---|---|---|
| primary - |
Run needs a finished writing job to borrow research from. There is none yet.
Users
Console admins. Every user can sign in here.
New user
working...
| Status | ||
|---|---|---|
| (you) |