Skip to content

Part 3 · Operate

A channel as a mission

Each channel in five steps: what we read, the plan, the first pieces, your yes on one launch card, then dated checkpoints and the result.

01What it is

With Missions on, a channel’s page opens on its Mission: Research (what the team read, with dates), Plan (the clock, the bar to clear, the pace and your time), Creative (the first week’s pieces as previews in your brand), Review (one launch card, your step) and Live and watched (checkpoints on fixed days and the clock’s last day, then the result with the numbers). Details shows the page as it was.

02Why it exists

Starting a channel used to be two decisions: approve the channel, then approve each first draft as it came. The launch card makes it one, with everything the yes covers on the card: the channel, its clock and rules, this week’s pieces, your time, the spend, what happens next and the rule we keep: we never stop a channel early or raise spend without your yes.

Once it runs, the checkpoints say on which day something was written, approved and out, and whether anything waits on you. A change later (a stop, a scale, a new angle) comes back as a small card with its reason, and nothing changes until you answer it.

03How to use it

  1. 01Open a channel from Your AI team, Channels, or from a launch card. Mission is the first view; Details is beside it.
  2. 02Read Research and Plan. A missing item says Not yet rather than guessing.
  3. 03On a channel that writes posts, press Write the first week if nothing is written yet. The drafts count against your plan’s drafts and always wait for you.
  4. 04Read each piece with Read it, then press Approve and start. The channel is approved with its rules, and every piece listed is approved with it. Edit opens the channel on the plan; Not now sets it aside.
  5. 05Launch cards also wait on Approvals, Channels and on Home, where the first ones show under Waiting for your yes.
  6. 06After the start, Live and watched lists each checkpoint with its date, OK or Needs you, and what was written, approved and out by that day. The result says Keep, Change or Stop when the clock ends, with the numbers measured over the test.

04What good looks like

You give it
A proposed LinkedIn channel with a daily cap of one, three drafts written for it in the Creative step, and a 30-day clock.
You get
A launch card reading “Start LinkedIn”, with the clock, the three rules, five pieces a week, the three drafts as previews and the button “Approve and start, with 3 pieces”. Pressing it approves the channel and the three drafts, writes one audit row per piece and one for the card.
Why
launchCardFor reads the channel and its waiting drafts, postsPerWeek turns a daily cap of one into five a week, and approveLaunchPieces runs each piece through its own approval path after approveLaneAction succeeds.

Derived from the rules in the code

05What weak looks like, and what it costs

You give it
A proposed directories channel, which works from its own screen and writes no posts.
You get
Creative lists the planned steps for days one to seven from the plan, marked Yours or Team, and says they are steps, not drafts. The launch card says no drafts yet and the button reads “Approve and start”.
Why
Only a channel with a post type writes drafts here (PRESENCE_TARGET); any other shows the plan’s own first-week steps and never invents a piece.

Derived from the rules in the code

06Read next