Teaching the Engine Your Brand

The Engine already starts with a lot: your brand identity, your products, and your latest visibility report. Two tabs in the Engine workspace take it further — Brand voice and Documents.

Brand Voice: Two Layers

The Brand voice tab holds the Engine’s picture of how you write, in two layers that work together:

Committed style

The voice and design the Engine writes in — captured from your site and posts, editable by you. Your edits are permanent. It has two parts:

  • Site design system — your site’s own design vocabulary (tokens, components, section patterns), so new pages match the rest of your site instead of looking bolted on. Run Analyze my site’s design to capture it.
  • Blog style — your blog’s committed house style: voice, signature devices, palette. Run Analyze my blog style to capture it from your best posts (or have one chosen to fit your brand if your blog is new). Without it, each draft styles itself from scratch.
Tip

Commit a blog style early. It’s the single biggest lever for making every draft read like one publication instead of a different writer each time.

Learned rules

Specific do’s and don’ts the Engine picks up automatically from your feedback. When you request a revision, it looks for the durable rule behind your comment — “always mention pricing in the first section”, “don’t open posts with a question” — and saves it as a lesson. Every active lesson steers future drafts alongside the committed style.

In the Learned rules section you can:

  • Review what the Engine has learned so far
  • Archive rules that no longer apply (and restore them later)
  • Consolidate to merge near-duplicate rules into one clean statement

Upload Brand Documents

In the Documents tab, upload the files you’d hand a new content writer:

  • Style guides and tone-of-voice documents
  • Example posts that nail your voice
  • Product documentation and messaging guides

Supported formats: PDF, TXT, MD, PPTX, XLSX. Upload once per brand — the Engine decides per job which documents are relevant, so you don’t need to attach them every time.

The feedback loop is the feature

The fastest way to great output isn’t a perfect first brief — it’s requesting revisions and letting the learned rules accumulate. Teams typically see draft quality converge on their voice within the first handful of jobs.