Platform · operated workspace · human authority
Agents automate repeatable work across measurement, production, publishing, website readiness, and visual delivery. Supporting products gather evidence and package accepted work. Humans retain decision authority.
Operated through
Product architecture
They prepare observations, content, publishing work, website changes, and visual assets inside explicit human gates.
Parsing Stack gathers bounded evidence. Content Package Studio converts accepted work into a delivery that can be opened and verified.
Routing, rule compilation, proof, files, memory, handoff, and token policy stay operational machinery—not extra products in the shop window.
Solution · the Marketing Agents platform
One Marketing Operator coordinates five agents across visibility analysis, content production and quality gates, canonical publishing and distribution, technical website readiness and verification and repeatable visual asset delivery. The agents automate repeatable work; humans retain decision authority for strategy, claims, approvals, and exceptions.
Agent 01 · measures · owns visibility analysis
Comparable AI-visibility observations and governed opportunities.
Hermes preserves comparable observations and keeps mentions distinct from citations. AI Visibility Intelligence normalizes the evidence, ranks opportunities, and prepares the next governed handoff.
Open Hermes Visibility →Agent 02 · produces · owns content production and quality gates
governed content packets with visible evidence.
ContentOS carries the prompt map, source boundary, draft, metadata, schema, checks, repair history, and human approval state together. Publishing authority stays in a separate product layer.
Open ContentOS →Agent 03 · publishes · owns canonical publishing and distribution
canonical-first publishing and bounded distribution.
Content Publisher preflights the destination, runs guarded publication, proves the live route, and keeps every approved channel adaptation connected by a visible source link.
Open Content Publisher →Agent 04 · optimizes · owns technical website readiness and verification
project-bound website changes with live proof.
The workflow can repair discovery, metadata, schema, links, layout, and performance within an approved scope. Passing CI remains human-review-required, and technical proof does not become a claim of causal attribution.
Open Website Agentic Optimization →Agent 05 · designs · owns repeatable visual asset delivery
placement-specific visual assets with pixel proof.
Visual Asset Studio renders against an exact placement and verifies the final pixels before handoff. It does not invent a brand system or campaign concept when the brief is incomplete.
Open Visual Asset Studio →Supporting products · evidence and delivery
Gather evidence
Fetch bounded source material, SERP evidence, and structured facts with source-quality and uncertainty checks. It gathers evidence; it does not decide what the evidence means or publish from it.
Open Parsing Stack →Package client delivery
Turn an accepted article and quality receipt into a branded PDF package, schema deliverable, manifest, and verified client delivery. It packages accepted work; it is not a writer, CMS publisher, or generic design tool.
Open Content Package Studio →Workspace control plane
Route work, compile rules, bound tools, run proof, preserve artifacts and decisions, and write operational handoffs. Internal machinery, not a separately priced product line; Agent Governance currently runs in shadow.
Platform questions
It is an operated workspace for AI-search marketing work. Five client-facing Marketing Agents own repeatable responsibilities; supporting products gather evidence and package accepted work; the control plane routes, constrains, proves, and remembers each run.
Hermes with AI Visibility Intelligence, ContentOS, Content Publisher, Website Agentic Optimization, and Visual Asset Studio. Each has a named responsibility and a human approval boundary.
Parsing Stack gathers bounded source evidence. Content Package Studio turns accepted work into a verified client delivery. They support the operating loop without pretending to be autonomous marketing roles.
No. It automates repeatable work while people retain strategy, claim approval, prioritization, publishing authority, and final judgment.
No. Installed modules are grouped into buyer-readable product surfaces. Control-plane, internal-operations, and tenant-specific modules are not presented as separate subscriptions.
The operator approves the goal and sources, the workspace prepares and checks the work, a human approves the output, the publisher ships the canonical asset, and the proof loop verifies the live result.
We define the first responsibility, evidence boundary, approval path, and handoff to your employee before recurring work begins.