Without Cogs, No Machine Moves
In a world where machines have become the principal audience, content operations are evolving to meet the requirements of agents. As documents leave the CMS, organizations face challenges around maintaining structure and provenance that deliver vital context to machines. Here's why meshing the COGs (Community Owned Governance Standards) is the key to delivering trust and value.
Tom Cranstoun, “The MX Guy,” is the principal consultant at Digital Domain Technologies Limited, author of MX: The Handbook, and a CMS Critic contributor.
Content operations and content design are doing the right things. They're providing governance frameworks, taxonomy, structured authoring, and lifecycle management. Over time, the disciplines have matured.
Up until now, content ops has focused on human readers. Now, in an era where bot traffic is outnumbering humans, the dynamic has shifted. Machines have become the predominant audience, and they have different requirements. The gap is narrower than it looks – and more specific.
That gap is where most organizations are going to get stuck. Cogs that don’t mesh don’t move anything. They just grind. But there's hope, and it starts by understanding the crucial role of MX: Machine Experience.
What Machines Need That Humans Don’t
A human reading a page infers context. They notice tone, recognize brand, and understand that a press release from 2019 probably doesn’t reflect current pricing. They bring judgment.
Machines don’t. And they’re not one thing.
An on-device model with a small context window reads raw HTML and sees nothing beyond what’s in the initial server response. A foundation-model agent with browsing tools sees the rendered DOM. A scraper never runs a model at all. A coding agent fetches once over HTTP and moves on. Each reads a different projection of the page, and none of them sees the visual rendering. The publisher can’t know which kind arrives, so designing for a specific agent is designing for a guess.
Despite these differences, every machine type does one of two things: It finds a declaration, or it guesses. What is this document? Who made it? What’s it for? What can be done with it? What’s still accurate?
Good content ops structures pages so humans can navigate them. That’s necessary. But it’s not sufficient. The metadata is in a database that the agent can’t reach. The relationships are implicit. The provenance isn’t embedded. The agent (whichever kind it is) fills the gaps with confidence it hasn’t earned.
That’s not a failure of content design. It’s an extension that hasn’t been built yet.
Now, take it one step further. A machine doesn’t always read your content inside your environment. For example, a PDF getting ingested by another organization’s LLM, or a page being scraped and stored in a vector database. A document travels through three systems before an agent even acts on it.
At that point, the CMS is gone. The database is gone. The metadata that lived in the platform’s tables is gone. What’s left is the file. If the file carries nothing (no provenance, no authorship, no permissions, no declared scope), the agent has nothing to work with except the words. It guesses the rest.
This is the old problem, made new and urgent. Documents have always lost context when they leave their environment. MX is built specifically for that moment.
Governance Built Into the Document
A CMS isn’t just software. It’s a controller of a publishing point. It has an implicit contract with the data owner to make content visible to humans in a way that benefits the owner. That obligation now implicitly includes machines, whether anyone asked for it or not. When it fails, the data owner blames the vendor. The vendor blames the agency. Nobody owns the failure because nobody wrote machines into the contract.
A plugin doesn’t close this gap. Neither does a model upgrade or an MCP (Model Context Protocol) endpoint. Those wrap the content. They don’t change it. What makes the difference is governance built into the document itself. Not bolted on, not held in a separate system.
That’s what a COG is: Community Owned Governance. It's a portable, self-describing document standard that carries its own context wherever it travels. It includes vital details like what it is, who made it, what it’s for, and what an agent is and isn’t permitted to do with it.
Take a cog out of a machine, and it stops. Take governance out of a document, and the machine that's reading it stops working, too. It doesn’t issue an error. It hallucinates. And that's even worse.
The work that content ops and content design have already done – the taxonomy, the schema, the approval chains – is exactly the right foundation. A COG is how that work travels with the content, instead of staying behind in a CMS database that the agent can never query.
Ownership Only Works With Structure
The organizations getting real value from AI aren’t pouring content into shared infrastructure and hoping for the best. They’re running models on their own data and building agents against their own knowledge base.
That only works if the data has structure – and as stated, that structure can travel. Ownership without portable structure is a hard drive full of files nobody can act on safely. A document with provenance (where the relationships are explicit and the records are verifiable) is something you can point a machine at and trust the result.
The Asset That Compounds
Within a few years, most online content will be machine-generated. Volume is already cheap. So is velocity.
What becomes scarce is authorship. Content that a human wrote, edited, argued over, and signed off on. Content that has a history. That doesn’t depreciate when generation gets cheaper. In fact, it appreciates – because it’s the thing machines can’t produce and audiences can distinguish.
The right home for that content is a system where governance is built into every document: structured, provenance-intact, and verifiable. Pointing a model at well-governed content produces something qualitatively different from pointing it at an undifferentiated pile.
Content ops and content design got us here. COGs take it the rest of the way. The organizations that understand this aren’t waiting for the next release note. They’ve already got the cogs turning.
Is your PDF MX Compatible?
See what the gaps are in practice!
- Visit https://mx.allabout.network/tools/pdf-inspector.html
- Drop in a PDF sample where instructed. Your browser reads it locally, and the PDF never leaves your machine.
- The inspector reports what the file carries, what it lacks, and what a regulator or AI agent would find if they tried to verify it.
Upcoming Events
CMS Connect 26
August 5-6, 2026 – Montreal, Canada
The best conferences create space for honest, experience-based conversations. Not sales pitches. Not hype. Just thoughtful exchanges between people who spend their days designing, building, running, and evolving digital experiences. CMS Connect brings together people who share real stories from their work and platforms and who are interested in learning from each other on how to make things better. Over two days in Montreal, you can expect practitioner-led talks grounded in experience, conversations about trade-offs, constraints, and decisions, and time to compare notes with peers facing similar challenges. Space is limited for this exclusive event, so book your seats today.
Open Source CMS 26
October 20–21, 2026 – Utrecht, Netherlands
Join us for the first annual edition of our prestigious international conference dedicated to making open source CMS better. This event is already being called the “missing gathering place” for the open source CMS community – an international conference with confirmed participants from Europe and North America. Be part of a friendly mix of digital leaders from notable open source CMS projects, agencies, even a few industry analysts who get together to learn, network, and talk about what really matters when it comes to creating better open source CMS projects right now and for the foreseeable future. Book your tickets today.
Contentstack ContentCon 2026
September 30 - October 1, Amsterdam / October 27-28, 2026 – Chicago
Contentstack’s annual customer conference is the premier event for executives, marketing leaders, and developers to redefine their digital experience strategy. This is your opportunity to step out of the "status quo" and into "elite" status, learning exactly how the world’s most successful brands are using the technology you already own to do the impossible. Enjoy a full day of interactive workshops, certifications, and inspirational on-stage sessions designed to help you become an expert on cutting-edge digital strategies and how to turn Contentstack's CMS and adaptive personalization tools into your greatest competitive advantage. Book your seats today.