Marketing Agent 03 · publish · prove
The canonical asset ships first. Every channel inherits its source.
It accepts approved content, preflights the canonical route, prepares metadata and schema, runs the guarded rebuild, proves the live page, and only then creates bounded channel adaptations.
PUBLISH receipt
- Route
- Metadata
- Schema
- Rebuild
- Live proof
- Source link
Canonical-first contract
One owned source. Bounded derivatives.
On 22 July 2026 we checked eight English product routes before requesting publication. The proof used Astro build output plus schema, link, layout, design, and ContentOS gates.
- Accept the governed packet. Confirm content approval, canonical route, metadata, schema, visible sources, and publishing authority.
- Preflight the destination. Check route ownership, current production state, build inputs, conflicts, and rollback path.
- Ship the canonical asset. Run the guarded rebuild. Then inspect the live page, metadata, schema, links, discovery entries, and extractor output.
- Adapt inside channel limits. Create only the approved excerpt or derivative, preserve a visible source link, and use the channel-specific authority contract.
- Record destination proof. A queued job is not a published result. Each adapter records what the destination actually accepted.
What the agent returns
A publication receipt. Not a success toast.
Canonical
Owned route
The final URL, title, description, canonical tag, visible source links, and required schema stay inspectable.
Build
Guarded rebuild evidence
The accepted content fingerprint, expected anchors, forbidden regressions, and rollback state are checked before promotion.
Discovery
Sitemap and LLM entries
The canonical route is present in site discovery surfaces and has real internal inbound links.
Adapter
Medium Publisher job
One canonical URL enters one bounded draft or publish job under one server-owned account session.
Attribution
Visible source link
Channel adaptations point readers and machines back to the owned canonical asset.
Proof
Destination result
The receipt distinguishes prepared, queued, published, and verified states instead of collapsing them into done.
Boundaries
Publishing authority is destination-specific.
Distribution cannot become a substitute for the source page or outrank the owned version by accident.
It does not become a generic scheduler, does not borrow a browser session, and does not infer which account should receive the work.
A valid draft, clean build, or queued job is intermediate evidence. Completion requires proof from the intended destination.
Content Publisher FAQ
Canonical first, channel authority second.
What is Content Publisher?
Content Publisher turns an approved content packet into a canonical route, metadata and schema handoff, guarded rebuild, live proof, and bounded channel adaptations.
What does canonical-first mean?
The owned canonical asset ships before channel adaptations. Every derivative keeps a visible source link back to the canonical URL and follows the destination-specific limit.
Does Content Publisher write the article?
No. ContentOS owns production and acceptance. Content Publisher owns publication authority, destination preflight, guarded rebuild, and proof of the live result.
What is Medium Publisher?
Medium Publisher sits under Content Publisher as a channel adapter. It handles one canonical URL and one server-owned account session per job.
Can it publish to every channel automatically?
No. Each channel requires its own authority, format, session, and proof contract. Missing access or an ambiguous destination stops the run.
How is a publication proved?
The receipt records the accepted packet, canonical URL, rebuild or publish job, destination result, visible metadata, schema, source links, discovery entries, and live extractor checks.
Publish once as the source. Adapt without losing the source.
We will define the canonical route, proof contract, allowed channels, adaptation limits, and rollback path before the first publish job.