PublishLiveWeb app · one workspace per companySteward: [name]

The content engine that runs mostly on its own.

It researches what is worth saying, drafts articles and social posts with their images and SEO, reviews its own work against hard gates, publishes what passes to your website and your social networks on a schedule, and pulls the results back in. Your job is decisions, not production.

Publish

[9]

Changes shipped this quarter

[78]%

Started as a member’s problem

[5]

Open requests in the queue

[4] days

Request to decision, median

Sample values. Live figures for this product, published monthly. How the scorecard works.


Who it is for

Companies without a content team, where one person runs a weekly article and a daily social presence in about five minutes a day. Agencies and multi-brand operators with a sealed workspace per client, co-branded, never white-labelled. Creators with a YouTube channel who want scripts, thumbnails, a production board and rendered video in the same loop. Teams that need roles, an approval workflow, function-by-function autonomy dials, an emergency brake and an audit log.

Who it is not for

Organisations that want a digital asset manager. Brands that want paid-ad management. Anyone who wants an AI that writes whatever it is told without sourcing.


One loop, from research to results

A machine with a person at the gates.

Most content tools give you a blank page and a calendar. Every 30 minutes a Publish autopilot sweep discovers ideas, drafts the ones you approved, gives each article featured and social-preview images and SEO metadata, has a vision model look at every image, sources every flagged claim from live web search, applies the mechanical fixes, advances what passes, publishes on your publish day, writes and queues social posts, recycles evergreen content and syncs your results. Everything it cannot fix parks at a gate for you, with the action on the card.

Research → Ideas → Drafts → Review → Publish → Distribute → Measure

with an Inbox above it that shows exactly what is waiting on you, and Setup beneath it for the dials. An assistant sits on every page and can do nearly everything you can, asking first before anything goes out.


Why it is different


The seven stages

One screen each. A red badge on the strip means a person must act; a muted one is news.


The assistant, everywhere

It can do nearly everything you can. It asks first.

Press the Ask button in the top bar, or Ctrl+/, on any page. The assistant opens as a dock over what you are looking at, knows which page you are on, and can do nearly everything you can do in the app.

It reads everything.
The pipeline, the Inbox, ideas, articles and their checks, social posts, keywords, topics, channels, competitor outliers, connections, dials, results, reports, the live web, and the app’s own guide.

It does the work.
Finds, adds, approves and rejects ideas; discovers keywords and topics; drafts articles and scripts; writes SEO and images; runs Optimize and applies, answers or dismisses findings; verifies or drops claims; approves images; advances an article; drafts, queues, schedules and sends social posts; publishes, exports HTML or records a manual publish; changes the dials, slots, timezone and people; runs the autopilot now.

It asks first.
Anything outward-facing or hard to undo is proposed as “I’m about to… Go ahead?” and runs only when you say yes. Admin-only acts refuse for editors, exactly as the pages do. Every action is written to the audit log, and the steps it took sit under every reply.

It keeps you oriented.
Ask “what should I do next?” and it reads the whole situation and ranks the moves, offering to do each one. When a request is ambiguous it asks, with choices you can tap.

It is the research conversation.
It carries your active channel’s niche, audience, voice and memory, reads Intel channels and videos, YouTube transcripts, web pages and uploaded files, and turns a conversation into a script on the canvas when you say “turn this into a script”.

It will not
enter API keys or credentials, delete a workspace or an account, or send email. Those stay a person’s hands on the page. With no working AI key it refuses the turn rather than guessing.


Control, at the level you want


Brand and voice

Your tone, as editable rules. Not a hidden prompt.

  • Seven Motifs: your tone, as editable and versioned rules that every generation blends by weight.
  • Brand kit: colours, logo, image dimensions, and whether AI may generate imagery at all.
  • Brand context for the AI: differentiators, products and what each does, brand documents, personas. Nothing here is AI-generated, on purpose, because an invented differentiator would be repeated as fact everywhere afterwards.
  • Topics the engine writes about, guardrails it must obey, and expert profiles it quotes.
  • Co-branding for agencies: upload a client’s logo and accent colour and the app chrome follows, with the product byline kept.
  • Elsie, the in-app guide, flags what is still worth setting up and offers short tours: an overview, making content, publishing, measuring, running the install.

Works with what you already use

Every key is pasted in the app, per workspace, without touching a server. Nothing degrades silently: when a provider is missing, the app says so, on the card, in plain words.

Category Providers
AI writing Anthropic Claude and Google Gemini, with DeepSeek, xAI, Moonshot and MiniMax keys also accepted. The model is chosen per workspace and per channel.
Live web search Tavily or Serper, for claim sourcing and research
Images and vision review OpenAI gpt-image-1 or Google Gemini image generation. Vision review by OpenAI or Google.
Video, shorts, voice Google Veo renders from a storyboard. Branded shorts through HeyGen. Voice through ElevenLabs.
YouTube The Data API for research and channel linking
Social Fifteen networks through Zernio
Email A connected mailbox through Unipile, for invitations, digests and notifications
Website WordPress, or HTML export for any site
Measurement Google Search Console and Google Analytics 4
Storage Local disk or Google Drive, served only to signed-in users
API A read-only API for channels, scripts and ideas, with a per-workspace token

Setting a workspace up, once

In order; each step unlocks the next. A workspace is one company: its keys, accounts, voice, slots and content are its own, invisible to every other workspace.

Step Where What you do
1 · Give it a brain Publish Admin → API keys Paste an AI provider key and set the default model to match it. A live web search key (Tavily or Serper) is what lets it source claims.
2 · Connect where it publishes Settings → Connections Social accounts (use the app’s Connect buttons), a mailbox, your website under Publish → Website (WordPress, or per-article HTML export), analytics.
3 · Teach it your voice Brand → Tone & motifs The seven Motifs, topics, guardrails, and the brand kit: colours, image dimensions, and whether AI may generate imagery.
4 · Tell it what you actually do Brand → Brand context Differentiators, products and what each does, brand documents. Every AI feature reads this before it writes.
5 · Set the clock Settings → Schedule Timezone and posting slots, the recurring times the queue sends at.
6 · Choose your gates Settings → People Require approval holds every social post until an admin approves it. Articles always park at review. Queue on approval makes approving the last act.
7 · Set the autonomy dials Settings → Automation Articles a week and on which day, social posts, evergreen, the four function modes, or full autonomy. Start low; raise once you trust what arrives at review.
8 · Wire up measurement Publish Admin → Analytics Search Console site and GA4 property, with the service account granted on both. Until then Measure shows dashes.
9 · Invite the team Settings → People Editors write, draft, answer and propose; admins approve, publish and configure.

What it deliberately does not do

  • It never publishes, sends or approves anything on its own without the gates passing or a person’s yes.
  • It never invents a statistic, an outlier ratio or a best time to post.
  • It never overwrites metadata a person wrote.
  • It never verifies a claim on a placeholder’s word: with no real search key, the claim waits.
  • It never charges, meters or bills inside the app.
  • It never removes the product from the chrome: co-branded, not white-labelled.

The charter

What it holds, and what it will never become.

Every accepted request for Publish cites one of these lines. Every decline cites the line it would break. The steward reviews the charter with the community once a quarter.

The opinions it holds

  • Gates review as well as block. Nothing AI-made reaches an audience until metadata, slug, keyword, alt text, sourced claims and a branded preview image all pass.
  • Claims are sourced, not asserted. Live search finds a source, an independent judge confirms it supports the sentence, and an unsupported claim waits for a person with two buttons: verify or drop.
  • Every AI image is looked at. A vision model checks each render. After two failures it stops spending and asks.
  • Never an invented number. A dash means not measured, never zero.
  • Silence means all clear. A quiet morning sends no digest, on purpose, so the emails that arrive mean something.
  • Approving is a person’s act. Only approved ideas are drafted. Publishing an article and approving a social post are always an admin’s act. Full autonomy presses the buttons a person would. It does not lower what they check.
  • Bring your own keys, keep your own data. No billing, credits or metering inside the app. Co-branded for agencies, never white-labelled.

What it will never become

  • A generic AI writer. Everything it writes is grounded in brand context, motifs, expert profiles and sourced claims. There is no blank chat box that produces ungrounded copy.
  • A paid-ads platform. Organic articles, social and video only.
  • A brand-monitoring or sentiment tool. Intel measures competitor video outliers to find ideas. It does not watch the internet for mentions.
  • A white-label product. The client’s identity leads. The product stays visible.
  • A metered marketplace. No credits, no tokens, no in-app billing.

What members can ask for

In scope

  • A new network
  • A new gate or check
  • A new motif
  • A report block
  • A CMS export format
  • An Optimize finding type
  • A research source
  • A video-studio step

Out of scope

  • An ads module
  • White-labelling
  • In-app credits
  • A publish path that skips the gates
  • AI-generated brand differentiators

How it fits the family

The content and distribution layer. It distributes what Producer makes. The leads its content generates are Velocity’s to work. Editorial ideas can start in LevelUp. Workflow handoffs, not built integrations, until the changelog says otherwise.


The Publish queue · live

What members asked for in Publish, and what we did.

The problem Raised by Status Decided in Shipped
[Problem statement as the member wrote it] [Member name] Shipped [3] days [date]
[Problem statement as the member wrote it] [Member name] Building [2] days behind a flag
[Problem statement as the member wrote it] [Member name] Planned [4] days [sprint]
[Problem statement as the member wrote it]Declined by the steward: [the reason in one sentence, citing the charter line it breaks]. [Member name] Declined [6] days

Every request gets a decision within ten business days. Declines are public, with the reason. Shipped entries name the member who asked. The first entries appear as the founding cohort posts its first problems.


The routine

Five minutes a day. Half an hour the day before publish day.

The routine is a check, not a shift. If you are ever lost, ask the assistant what to do next.


Help, built in

Publish ships its own manual.

  • The owner’s guide: the whole machine on one page, a fifteen-minute read that the assistant knows too.
  • A Help Center with role-based paths, searchable answers by category, and keyboard shortcuts.
  • Hover help on every rail entry and control, in a sentence or two. Elsie’s short tours.
  • A morning digest on the days it matters, and a notifications bell for holds and failures with a link to each. Old links keep working.

Publish is included in every membership.

Your subscription funds the team that builds what you ask for. No metering, no credits, no tokens inside the app: it runs on keys you paste in, per workspace.