Stories A promise's telling

Magazine

Anyone in ONE can turn what they follow into a finished issue — page, email and posts — without writing it

The seven beats

Groups: A group with a site, a list and social accounts
Actors: Owner, editor agent, readers, ingest clock
Events: A schedule tick, or one sentence in chat
Things: A finished issue each day, published after one look
Paths: Follow, fetch once, rank, take, picture, page, three channels, learn
Outcome: The owner stops writing and starts approving, then stops approving
Learning: Open until a desk has run long enough to show which sources its readers open

This story carries its beats but no written telling yet — text/magazine.md has no “The story” section.

Every link here was checked against the repo when the page was built. 1 name the story uses could not be found and is shown without a link.

Each opens a chat with that agent.

Each opens the skill's page.

The flows this story walks — trigger → step → step.

schedule:cron → news:digest → news:issue → condition trusted? → human approve → news:publish
chat sentence → editor → magazine-set-up → news:desk → workflow:create from daily-magazine → news:digest preview
reader tap → news:react → mark/warn on desk→source, desk→topic → tomorrow's news:digest

Receivers and scripts it signals.

What it holds; a told promise opens its own story.

What derives from this file.

Every event is a signal; each names the path it marks or warns.

news:react · from a reader, or chat on a reader's behalf mark or warn on desk→source and desk→topic tags: news, magazine
news:publish · from the workflow, or the owner in chat mark on desk→issue when published; warn when the gate held it tags: news, magazine

opens and clicks per issue, read from agent_events_warm by the campaign key; reactions per source and topic, read from path strength