MX makes content machine-readable. REGINALD makes it machine-trustworthy. Both properties are required for machine-ready content; building one without the other is building half the system.
Content Ops is the discipline of creating, managing, improving, publishing, distributing, archiving, and retiring content across every digital channel. MX is the layer that keeps Content Ops work usable when an AI agent, or any other system, encounters the file outside the environment that produced it. REGINALD is the registry that signs it.
REGINALD is the public registry where documents are registered, cryptographically signed, and made verifiable by any machine on earth. A traditional proper name that describes exactly what it does:
The attestation is narrow and precise: this is what the owner published, unaltered. Origin and integrity only, not factual correctness, not editorial quality.
The practical effect compounds. Agents that read attested documents hallucinate less, because they have verified facts to cite rather than inferences to make. Fewer inference steps means lower token consumption and lower energy draw. As the EU AI Act, the European Accessibility Act, and digital-records legislation across multiple jurisdictions place documentation, logging, and verifiability obligations on the bodies they cover, attestation becomes the layer that makes the required documentation verifiable on request. MX and REGINALD do not grant compliance with any of these regulations; that remains a legal duty of the publishing body. What they do is make the documentation that body must produce structured, machine-readable, tamper-evident, and verifiable on request.
Note: This page 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.
The AI-readiness consensus is inward-facing. Every framework on the table asks how we use AI safely. MX asks the question almost nobody is asking: how is our team being read, retrieved, and represented by machines we will never meet? Audience: CIOs, CMOs, Heads of Digital. Companion to MX: The Handbook.
Machine-readable companions: Cog edition · Meta-cog
The Gathering ratifies the Machine Experience standard, including the contract fingerprinting note that defines how a document is canonicalised, hashed, and signed. REGINALD is one signing implementation of that standard, operated by CogNovaMX (the trading name of Digital Domain Technologies Ltd). A document with a REGINALD-issued attestation is registered against a public record any agent can verify.
For the standard itself, see the open MX drafts at The Gathering. For the broader programme, see the MX book series. For the wider infrastructure argument, see why the agentic era needs infrastructure, not just intelligence.
The REGINALD alpha registry is live at reginald.allabout.network. The Publisher Listing is an annual subscription that registers your cog file, surfaces it in the public publisher directory, and underwrites the signed attestation infrastructure every agent verifies against. The first paying cohort is being onboarded by hand; we will be in touch within two working days of your payment to confirm your publisher identity and configure your registry credentials.
The subscription includes registry-served discovery, public directory listing, and signed attestation infrastructure. Cancel anytime; one-off and bulk publisher arrangements available on request.
Prefer to talk first? Get in touch, or read the position paper.