Skip to main content
Growth Engine

Run spec · six steps · one gate

How a run works.And where it stops.

Six steps, one gate. The engine handles intake, research, drafting and claim review. The fifth step waits for a named human to review the pack before handover.

The run · six steps

From paste to approved.

Every run walks the same sequence. This is the whole of it, including the step where it waits for you.

  1. Intake

    You, then the machine

    You paste your brand basics: what you sell, who buys it, how you talk. We use those details as the starting context. Unverified details become questions for you rather than being treated as facts.

  2. Research

    Machine · evidence checked

    A five-vector sweep across your brand, your audience, your competitors, your positioning and your regulatory ground. Factual claims intended for use are checked against available evidence. Unsupported claims are held, reworked or removed before handover.

  3. Draft

    Machine · drafts only

    A full content week, written native per platform. The reel script works as a reel, the LinkedIn post reads like LinkedIn, the email sounds like an email. Nothing is pasted across five channels, and everything at this stage is a draft. None of it is publishable from here.

  4. Claim review

    Independent checker

    An independent checker reviews the draft batch before handover. It is a CAP/ASA-informed review, not a rubber stamp: claims lacking adequate evidence are marked held with the reason attached for the client to see.

  5. Your approval

    You · the gate

    Your private portal shows each numbered piece in its platform preview. Leave feedback beside the work, then approve the exact saved version in a separate decision. Approved pieces and the posting calendar are handed back to you; you decide what to publish. Your edits are logged and used as context when future drafts are prepared.

    You decide here.

  6. Handover

    Client · publishes

    You get the posting calendar and a copy-paste pack: what goes where, when, and why that order. The client publishes the approved pieces; the engine does not post them.

The gate · in depth

What the human at the gate checks.

The checker follows five stated checks. Without approval, the pack stays held.

  • Voice. Does it sound like you on a good day, or like everyone's feed? Generic goes back for a rewrite.
  • Claims. Factual lines are checked against the cited evidence. They are evidenced, held, reworked or cut.
  • The look. Native formatting per platform, right lengths, right register. Nothing that smells pasted.
  • Held pieces. Each held piece re-read with its reason. It leaves held state one of three ways: evidenced, reworked or cut.
  • The open-questions list. Unresolved details are gathered in one place so the client can respond against a single list.

Without approval, it stays held. The gate fails closed.

Specimen · held pieceExample claim · invented

From a blog draft:

...switch your wholesale order and save 34% against the high-street price, which is why most of our customers...

status: held at the gate · needs a primary source

HELD, claim unverifiable
Why it is held: there is no primary source on file for that figure. The claim stays on the sheet, marked and hatched, until it is evidenced, reworked or cut. It is held, not publishable as written.
The block, mechanically
# checked before client handover
def handover(batch):
    if batch.approval.client_approved_at is None:
        raise GateBlocked("client approval required")
    return approved_pack(batch)

Publishing is not an engine action. The workflow hands the pack to you; only you decide what goes public.

Honest limits · on the record

What the engine does not do.

Publication stays with the client.

Handover is a posting calendar and approved pack. The client decides what to publish and posts it; the engine has no publication action.

Your files move through a private handoff.

After a human approves the exact kickoff, source bytes move from private storage through short-lived downloads into an isolated local operator workspace for processing by Claude. Enrolled research tools are the only research tools available. The run is instructed to use them for public research and not to put customer data into a query or URL.

The edit ledger

Your edits become drafting context.

Gate feedback is recorded in an edit ledger with the category and change. Those records are used as context for later drafts. They are a drafting aid, not a guarantee of perfect recall or fewer future corrections.

Edit ledger · specimen rowsThe shape of the record, not a live feed
piece 3 · voice    · hook softened             → logged as future drafting context
piece 5 · claims   · held, no primary source   → evidence requested, not publishable
piece 4 · the look · opening line shortened    → logged as future drafting context

Preview · intake held

See the package structure.

The same six steps, checker and human gate will apply when intake opens. For now, the package structure is available without submitting any details.

See package preview

Or download the clearly synthetic six-page sample PDF.

Current status: public requests and account creation are not open yet.