Marketing Agent 02 · produce · gate
A draft is one field. The product is the governed packet.
It turns an approved visibility or editorial opportunity into a source-bounded brief, draft, metadata and schema handoff, quality receipt, and human approval state.
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 →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?
For client delivery, Content Package Studio turns an accepted ContentOS article and receipt into a branded PDF package, schema deliverable, manifest, and verified destination handoff.
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.