Newsletter
A publication that reads its beat, drafts the issue, and sends on schedule while it grows its own list.
By naïve
What it is
The beat read every day and the stories worth an issue filed, a landing page and archive that convert readers into subscribers, and a send calendar the team keeps. Subjects and send times are tested issue over issue. Nothing reaches the list before you approve it.
The beat read daily and every issue drafted from sourced stories
A landing page and archive that turn readers into subscribers
Subject lines and send times tested issue over issue
Nothing reaches the list before you approve it
Ideal for Writers and operators who want a publication that ships every week without them at the keyboard.
The week it runs
Newsletter has no released repository behind it yet.
When it ships, its timers are read from the release and printed here in full — the hour each one fires, the message it opens with, and what that fire is allowed to spend. This page prints no schedule it has not read.
The crew
The 4 agents this template intends to run. Nothing is published behind it yet, so this roster is the catalogue's and not a release's.
- Issue
researcher
Reads the beat every day and files the stories worth an issue.
- Issue
writer
Drafts the issue in the publication's voice, every claim sourced.
- List
growth
Runs the landing page, referral asks, and social teasers; tests subjects and send times.
- Send
publisher
Schedules the send, watches deliverability, and files what each issue did.
What stays yours
The same three rules across every template. They are the blueprint's, not the crew's — an agent cannot widen them.
Nothing publishes itself
Every tool that acts outside your organization — a post, an email, a reply — is granted
ask, notallow. The call parks the session with its arguments in front of you and waits. Approval is a person, every time.A budget it cannot raise
$10 a day per agent and $2 a task, declared in the template and enforced by the platform. A run that would exceed its cap stops rather than spends.
Denied by default
An agent is offered the tools its template names and nothing else. Everything it was not granted is denied by name — the shell included, which is also why a content agent never provisions a machine it would not use.
What it ships
A template is a repo: the apps below, their server, and a naive.config.ts declaring the crew. Clone it, bind it to your organization, bring it up.
Newsletter has no released repository behind it yet, so there is no build to describe. The apps it intends to deploy are dashboard and site.
- $ naive template <blueprint># clone the blueprint repo
- $ naive claim --key sk_...# bind the clone to your organization
- $ naive up# provision the apps, the agents, their budgets
The number
A target while the benchmark runs — an average across a cohort of new accounts, never revenue and never per-client.
18,400
avg. subscribers at 90 days · 20 new publications
It gets a measured number once it runs on bench terms: live accounts, a fixed budget, twelve weeks, a control arm.
Launch your newsletter
An agent team, a workspace, a budget. No hiring.