Machine Experience
Make anything you publish readable by machines.
Videos, podcasts, PDFs, images, web pages — structure for machines. Explicit for everyone.
X-ray your website.
"MX is the DNA a file carries when it leaves any system."
Content Ops is the discipline of creating, managing, improving, publishing, distributing, archiving, and retiring content across every digital channel. Machine Experience (MX) is the layer that keeps that work usable when an AI agent, or any other system, encounters the file outside the environment that produced it. MX makes digital assets and documents readable by every machine that consumes them, so no machine has to guess.
Your website is a fraction of your content estate. Contracts, policy documents, product specifications, and technical reports never reach the web, but AI agents are reading them anyway, inferring what they can and guessing the rest. Being on the web and being machine-readable are not the same thing.
MX builds on what you already have. Schema.org and JSON-LD describe what entities mean, WCAG defines accessibility, Open Graph handles sharing. MX adds governance, provenance, lifecycle state, and agent affordances where those standards leave gaps, never duplicating what they already cover.
A provenance layer for machines
The web and the wider world of data files lack a provenance layer for machines. MX/REGINALD is built to be it. The industry is preparing to use AI safely inside its walls. Nobody is preparing to be read well outside them. That is the gap, and four parts close it.
The EU AI Act is the first regulatory forcing function. Other jurisdictions are following.
Training
Book a workshop
In-person or remote. Tailored to your team's platform, tech stack, and goals.
Learn MX
Self-guided. What MX is, why it matters, the core principles, and common mistakes.
Free introduction
Download MX: The Intro. The business case and the five-step action framework.
Books
MX: The Intro
The starter guide. Free download.
MX: The Handbook
Patterns you can implement this week.
MX: The Protocols
The definitive reference: architecture, standards, and the five-stage journey.
Consultancy
MX audit
What an MX audit delivers, and how to verify it. Routes engineers, clients, and auditors to the tool that fits them, plus the tools that let any reader verify the deliverable on their own machine.
Implementation
Hands-on implementation after the audit. One analysis turns into a prioritised plan, then into shipped patterns across the content estate.
Mentoring
Ongoing advisory for teams implementing MX. Architecture guidance and hands-on support.
Examples
MX in practice. Real-world implementations across different industries and platforms.
Verify it yourself
Every MX deliverable is built so any reader can verify the evidence chain on their own machine. Drop a PDF into the inspector to read the embedded provenance and conformance signals.
MX PDF Inspector
Drop any PDF into the inspector to read the embedded MX metadata, the AI provenance (attest payload), and the PDF/UA conformance declaration. Runs in your browser, nothing uploads.
What MX Compatible means
The explainer walks through the five signals an MX Compatible PDF carries: tagged structure, MX-namespaced XMP fields, conformance declaration, provenance attest pair, and embedded evidence chain.
Compliance and trust
MX makes content machine-readable. REGINALD makes it machine-trustworthy. Together they meet the provenance and accessibility requirements emerging in the EU AI Act, the European Accessibility Act, and digital-records legislation across multiple jurisdictions.
Note: This section describes regulatory frameworks in general terms only. Nothing here is legal advice. Requirements vary by jurisdiction, organisation type, and use case. Consult qualified legal specialists for guidance specific to your situation.
REGINALD
The registry that makes MX-attested content verifiable. Cryptographic provenance, narrowly scoped: this is what the publisher published, unaltered.
Learn moreWhy the agentic era needs infrastructure
Public-sector and regulated-industry content estates need an infrastructure layer, not just intelligence. MX, COGS, and The Gathering provide it.
Explore
AI Usage Declaration
Tom Cranstoun's signed statement on how AI was used in writing the MX book series. Read on the web or download the tagged PDF (ISO 14289-1 Level 2).
Ready to make your content estate work for AI agents?
Get in touch or email [email protected]