Marketing Agent 02 · produce · gate
A draft is one field. The product is the governed packet.
Why this topic, which sources it may use, the text itself, its metadata and structured data, the checks it passed, the ones it failed, and what was repaired. All in one packet, all reviewable.
We write our clients' articles through it and our own pages too. Last month we measured a gate stopping this very page at 72 out of 100 — repetition and readability both below par. It went back, got fixed, and cleared 80 before it shipped.
GOVERNED packet
- Prompt map
- Sources
- Draft
- Schema
- Gates
- Approval
Before drafting
Define the answer contract. Then write.
- Map the prompt. State the primary question, target prompts, direct answer, expected citation snippets, metadata, schema, and required source surfaces.
- Bound the evidence. Separate supplied facts, verified sources, measured product behavior, and claims that still need operator approval.
- Choose the destination. Declare the canonical route, audience, language, CTA, and whether a client delivery package is also required.
- Set acceptance criteria. Define what the built page, schema, links, and proof must contain before drafting starts.
What arrives for approval
Content, metadata, schema, and proof. One governed packet.
Intent
Prompt-page map
The primary answer, target prompts, expected snippets, schema contract, sources, and destination stay explicit.
Evidence
Source boundary
Visible links and supplied facts remain distinguishable from inference and unsupported claims.
Content
Editorial draft
The draft answers the declared prompt directly and follows the approved information architecture.
Discovery
Metadata and schema
Title, description, canonical route, Article or WebPage schema, and visible FAQ parity ship together.
Quality
Receipt and repair history
Checks, failures, bounded repairs, remaining gaps, and approval state remain attached to the packet.
Delivery
Packaging or publishing handoff
Accepted work moves to Content Package Studio for client delivery or Content Publisher for canonical publication.
Open Content Package Studio →Six components assemble that packet, and each one reports its own state rather than a single green tick for the engine. When a component has nothing in it, it says so.
| Component | What it holds | State it reports |
|---|---|---|
| Tenant binding | The project, its knowledge base, the primary domain, and where an accepted packet is allowed to go. | OK |
| Knowledge base corpus | The source folder this tenant's drafts may draw on. | No data until something is ingested |
| Author / org schema | Which byline and which organisation the published page will claim. | OK |
| Language modules | The default language and the native writing paths — English, Russian, Arabic. | OK |
| Quality gates | The checks a draft has to clear: 10 in English, 19 in Russian, 13 in Arabic, plus 3 support modules. | OK |
| Drafting queue | How many drafts are being written right now and how many are waiting for a lane. | Live count, 0 when idle |
An empty knowledge base reads as empty, not as ready — the same rule the visibility side follows. A component that has never run says so instead of showing a zero.
Named gates, per language
Ten gates in English. Nineteen in Russian, thirteen in Arabic.
English is the base set: ten checks every article clears, in any language. Two of them bound the packet before and after drafting. One walks every [1] marker and confirms it points at a real source. The rest measure the draft itself — grammar, uniqueness, AI likeness, readability, fact-checking. None of those failures are specific to a language, so the ten do not change.
The extra gates exist only where the failure exists. Russian adds nine. We did not design them up front — they accumulated from editor rejections. In one August batch our editor returned 137 corrections, and 50 of them were punctuation alone. That is what ru_transcreation and ru_humanlike_patterns now catch: a fluent English sentence wearing Russian words. The author who chose the English construction is the last person able to see it.
Arabic adds three, for its own failures. Dialect creeping into formal copy and Latin words left mid-sentence are Arabic problems. They are not English ones, so no English gate looks for them.
EN10
The base set
- prewrite_readiness
- publish_readiness
- final_uplift
- citation_integrity
- aeo_per_engine
- grammar
- uniqueness
- ai_detect
- readability
- factcheck
RU19
The ten above, plus nine
- ru_transcreation
- ru_humanlike_patterns
- ru_native_source_fidelity
- ru_claim_fidelity
- ru_editorial
- ru_style
- ru_style_profile
- ru_mqm
- ru_seo_naturalness
AR13
The ten above, plus three
- ar_source_fidelity
- ar_editorial
- ar_seo_naturalness
In the workspace each set reads contract ready · run not measured until it has run against a tenant's content. That is the honest state of a gate that is defined and wired but has produced no result yet — not the same claim as “passed”, and the interface does not let the two look alike.
Boundary
Production ends at acceptance. Authority stays separate.
ContentOS can prepare a publication handoff, but it cannot grant itself CMS, deploy, or distribution authority.
The packet records the failure and either enters a bounded repair or returns to the operator. It does not silently weaken the acceptance bar.
Content Package Studio packages only accepted work and verifies the file at its destination; it does not rewrite the article to make packaging pass.
ContentOS FAQ
What the packet contains—and what it cannot authorize.
What is Workspace ContentOS?
ContentOS turns an approved opportunity into a governed packet: prompt map, source boundary, brief, draft, metadata and schema handoff, quality receipt, and approval state.
What does governed packet mean?
The work carries its sources, constraints, checks, repair history, and acceptance state together. A fluent draft without that evidence is not a complete ContentOS output.
Does ContentOS publish directly?
No. Publishing stays outside the content-generation boundary. An accepted packet moves to Content Publisher, where canonical publication and channel authority are handled separately.
Where does Content Package Studio fit?
When the work goes to a client rather than to a site, Content Package Studio turns an accepted article and its receipt into a branded PDF, the schema files, a manifest, and a confirmed handoff to the folder the client actually reads.
Does every draft pass automatically?
No. Failed checks produce a bounded repair loop or an operator handoff. Missing evidence, unsupported claims, schema mismatch, and destination failures remain visible.
What must a person approve?
A person approves the opportunity, sources, new claims, positioning, acceptance criteria, final content, and the authority to publish or distribute it.
Bring an approved opportunity. Leave with a checkable packet.
The first task is to agree the answer contract, source boundary, destination, and human approval path.