They share one memory, so nothing is said twice
Three layers: directive, orchestration, execution
Idea to published, on a schedule, with the quality gate in the middle. Agentic content operations: nothing reaches your CMS that has not cleared word count, readability and keyword placement.
The SOP, written down. Goals, inputs, the tools to use, the outputs and the edge cases — in plain language, versioned like code. When we learn an API limit the hard way it gets written here, so it is never learned twice.
The only probabilistic layer. It reads the directive, calls the tools in order, handles the errors and asks when something is genuinely ambiguous. It does not do the work itself.
Deterministic scripts. Same input, same output, every run. Ninety per cent accuracy per step is fifty-nine per cent over five, so anything that must be right lives down here instead.
The refinement pass is separate from the draft on purpose. A single generation pass produces competent, generic prose; the second pass is where the specifics and the argument arrive — and where anything generic gets rejected before you ever see it.
Also connects to
Read-only wherever read-only is enough. Nothing gets write access it doesn't need, and every write is logged.
Word count within spec and readability inside the target band.
Primary keyword present in the H1 and the title, without stuffing.
Author attribution is a real, named human — never a fictional byline.
That consistency is the whole point. The same checks and the same artifacts on every run, so when a number moves you know it moved because your site moved — not because the method did.
| Spec | Standard | Deployable |
|---|---|---|
| Where it runs | Our infrastructure | Yours |
| Who holds the API keys | Us, scoped per client | You |
| Cadence | Monthly, or weekly | Any schedule |
| Raw data retention | Rebuilt each run | Your policy |
| Artifact delivery | Your Drive and tracker | Your choice |
| Source code access | — | Full |
| Runs unattended | Yes | Yes |
| Failure alerting | Slack and email | Your channels |
Deployable hands over the software, the hosting and the keys. You run it; we stay on for support.
Between 50 and 100 published articles a month on Operate, depending on length and vertical. Each one runs the full path from keyword opportunity through brief, draft and quality gate to a live post — not a draft folder someone still has to work through.
A quality gate sits between draft and publish. An article has to clear word count, readability and keyword placement before it can reach your CMS, and anything that fails goes back rather than through.
WordPress, Shopify, Webflow and Wix, natively through each platform’s API. Nothing is uploaded by hand, and the metadata and schema go with the post rather than being added afterwards.