company templateUpdated: Sep 23, 2026

Naive Long Form v1

One subject a piece, researched until every claim has a source and planned against real videos of the same length, then rendered a minute at a time and joined into one finished file.

By naïve·media/longform v1.7.0

Deploy · coming soon
YouTubeInstagramTikTok
1:12Targetavg. view duration at 90 days · 20 new channels
5Agentsprovisioned on deploy
1Appchannel
32Runs / weekunattended · 8 timers

What it is

A three-minute piece is a different job from a fifteen-second one, and this team is built for the difference. Setup asks the same four things the other media templates ask — the niche, the apps it posts on, a channel or video to model it on, the cadence — and from them the researcher takes ONE subject per production day and reads it until four or five claims can be sourced, then finds a real video of this length and writes down how it opens, where it turns, and what it does at the moments a viewer would otherwise leave. The writer pulls frames out of that video at exactly those turns and looks at them before planning a single shot. Only then is anything rendered: the piece goes out as segments, joined into one file and probed against the plan. Every finished piece lands as a pending post with its caption drafted, and the queue is the only way out.

  • One subject a piece, sourced claim by claim — a subject that runs dry at forty seconds is handed back rather than padded out

  • The writer samples frames from a real video of this length before planning a shot, so the structure is borrowed from something that held an audience

  • Rendered in segments, every boundary laid on a shot change so the join never lands mid-shot, then probed against the plan before it publishes

  • A piece that half rendered resumes from the segments already filed instead of buying them a second time

Ideal for Operators who want a channel publishing researched one-to-three-minute video on a cadence, with no editor in the loop.

The week it runs

media/longform · v1.7.0 · published Sep 25, 2026

8 timers are provisioned with this template — 32 unattended runs a week. Each fire opens a session with the message excerpted below and spends against its own cap, which the studio prints before you deploy.

  • 05:00every Monday, Wednesday and Friday at 05:00researcher0 5 * * 1,3,5America/New_York

    Research the next subject. Read project_context, this channel's reference teardown (channel.list_posts, source "reference teardown") and what is already queued…

  • 05:30every Monday, Wednesday and Friday at 05:30writer30 5 * * 1,3,5America/New_York

    Plan what the handoffs missed. Read project_context, this channel's reference teardown and its arc style post (channel.list_posts, sources "reference teardown"…

  • 06:00every Monday, Wednesday and Friday at 06:00producer0 6 * * 1,3,5America/New_York

    Make the next piece. Read the niche and tone (project_context) and the planned generation projects (channel.list_projects, status planned, kind generation)…

  • 07:30every Monday at 07:30analyst30 7 * * 1America/New_York

    Write the weekly report. Read project_context, what posted in the last seven days (channel.list_posts, plus the connected account's metrics where offered) and…

  • 08:00every day at 08:00channel-manager0 8 * * *America/New_York

    Sweep the queue. Read every pending and ready post (channel.list_posts), and on each one fix the caption, the kind and the scheduled day with…

  • 09:00every Monday at 09:00channel-manager0 9 * * 1America/New_York

    Plan the week. Read the channel's niche, audience and cadence (project_context), the reference teardown if this channel has one (channel.list_posts, source…

  • 09:05every day at 09:05channel-manager5 9 * * *America/New_York

    Daily performance check. Call social.post_metrics with since_days 14 to record today's numbers for every post from the last two weeks. Do not edit, delete or…

  • 18:00every day at 18:00channel-manager0 18 * * *America/New_York

    Read the comments on what this channel has posted today and on the pieces still gathering them, and reply in the channel's voice. Comments are read and…

The Agent Team

read from the media release

The 5 agents naive up provisions into your organization — the role each holds, the tools it is allowed, the skills it was taught, the timers it owns and the first thing it is told. An agent marked required cannot be left out of an install; the rest are yours to decline.

  • channel-manager

    Channel leadrequired

    Runs the channel: plans the week from the cadence answer, briefs the team, keeps the post queue tidy and replies to comments in the channel's voice. Never publishes without an approved post.

    toolsask_operatorboard_readboard_writebrowser… 20 more tools

    skillsnaive/caption-writingnaive/reference-teardown

    4 timers·08:0009:0009:0518:00

    anthropic/claude-sonnet-5

  • researcher

    Research & briefs

    Researches one subject a fire, with its sources and the exemplar videos of this channel's own length that show the writer what shape it should take. Never plans or renders.

    toolsask_operatorboard_readboard_writebrowser… 21 more tools

    skillsnaive/video-trend-brief

    1 timer·05:00

    anthropic/claude-sonnet-5

  • writer

    Structure & scripts

    Plans each brief as a whole piece — hook, acts, shots, facts and their sources — after sampling frames from its exemplars, and lays the shot boundaries where the render's segment seams fall.

    toolsask_operatorbashboard_readboard_write… 24 more tools

    skillsnaive/long-form-arcnaive/caption-writing

    1 timer·05:30

    anthropic/claude-sonnet-5

  • producer

    Render & assembly

    Renders each planned segment, joins them into one file with ffmpeg, probes it against the plan and files the finished piece. Resumes a half-rendered plan rather than re-buying it.

    toolsask_operatorbashboard_readboard_write… 21 more tools

    skillsnaive/video-assembly

    1 timer·06:00

    anthropic/claude-sonnet-5

  • analyst

    Performance

    Reports weekly on where the audience actually left each piece, read against the plan's own acts, and tells the crew what to make more and less of.

    toolsask_operatorboard_readboard_writebrowser… 17 more tools

    skillsnaive/channel-report

    1 timer·07:30

    anthropic/claude-sonnet-5

You will be asked

read from the media release

Answered in the studio before anything is provisioned, and read by every agent before it acts. Configuration only — a secret is a vault credential or an app secret, never an answer. You can change the answers later.

  • 01

    Niche

    Pick one or type your own — every subject, script and render is for this niche. Your tone and who it is for is the first thing the channel manager will ask you about.

    Stoicism & philosophyTrue crime recapsSpace & astronomyPersonal financeHistory mysteriesHealth & longevityor your own…
  • 02

    Where should this channel post?

    Pick the apps your videos go out on — one or several. Picking them is not the same as connecting them — after setup, open Accounts and connect the account you post from on each one, or the team will fill a queue that cannot publish.

    YouTube ShortsTikTokInstagram Reels
  • 03

    A channel or video to model this on

    Optional, and the most useful thing you can give the team. Paste a channel or video link, and/or the URLs of a few stills from it — stills are worth far more than a link, because the team can actually look at those. It is studied once, up front: the shot grammar, the hooks, the pacing, the caption shape. Every brief, script, render and review is then measured against it. Leave it blank and the team works from your niche alone.

    A link, or image URLs — one per line

  • 04

    Posting cadence

    daily3× a weekweekly

Skills

read from the media release

The procedures the agent team loads before it works — what to read first, what to file where, what never to do. naive/ names the platform's own catalogue, which the studio's Skills screen carries; a bare slug is a skill the template ships itself.

naive/caption-writingnaive/reference-teardownnaive/video-trend-briefnaive/long-form-arcnaive/video-assemblynaive/channel-report

What stays yours

The same three rules across every template. They are the blueprint's, not the agents' — an agent cannot widen them.

  • Nothing publishes itself

    Every tool that acts outside your organization — a post, an email, a reply — is granted ask, not allow. 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

    A daily cap per agent and a cap per 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

v1.7.0

A template is a repo: the apps below, their server, and a naive.config.ts declaring the agent team. Clone it, bind it to your organization, bring it up.

channel

fullstack

Media channel dashboard — post queue, style templates, accounts, analytics.

App, server and database — serves its own MCP endpoint to the agents

build c75d445bb9613b62…

  1. $ naive template media --template longform# clone the blueprint repo
  2. $ naive claim --key sk_...# bind the clone to your organization
  3. $ naive up# provision the apps, the agents, their budgets
Deploy · coming soon

The number

A target while the benchmark runs — an average across a cohort of new accounts, never revenue and never per-client.

1:12

avg. view duration at 90 days · 20 new channels

It gets a measured number once it runs on bench terms: live accounts, a fixed budget, twelve weeks, a control arm.

Launch your naive long form v1

5 agents, 1 app, a budget. One command.

Deploy · coming soon