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.
"Trustworthy" is a word, and a machine cannot act on a word. It can act on four separate questions, and REGINALD is built to answer each one on its own.
Attestation. Who published this, and when? A signature bound to a declared identity, not a claim in the page's own text.
Currency. Is this the version that still stands, or one superseded three revisions ago?
Freshness. Is the publisher still behind it? A record whose owner has walked away is a different thing from one they renew, and a machine should be able to tell them apart.
Corroboration. Does an authoritative outside source independently say the same thing? Attestation proves who published a claim. It never proves anyone credible agrees with it, and pretending otherwise is how a signed lie gets treated as a fact.
Here is the difference that matters, and it is the one no governance platform can offer you.
A governance platform keeps your evidence inside its own product. You query it while you hold a licence, export it at their discretion, and lose it the day you leave. Ours travels inside the file. The signature, the provenance, and the record of how it was made go wherever the document goes, and a regulator, an auditor, or an acquirer verifies them on their own machine using standard cryptographic libraries they already have.
They need no account with us. They need no permission from us. They do not have to trust us at all, which is precisely the point: verification you have to take our word for is not verification.
REGINALD signs. It does not verify. Verification is yours, and everybody else's.
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.
One of those obligations has a date on it. From 2 August 2026, EU AI Act Article 50 requires that AI-generated output is marked in a machine-readable format and detectable as artificially generated, text included. The high-risk conformity obligations follow later, from 2 December 2027, after the Digital Omnibus deferral the Council approved in June 2026. The marking duty is the near one, and the evidence chain it needs is the same one the conformity assessment will ask for afterwards, which means the work is not thrown away.
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 behind every agent's verification.
The first cohort of publishers is being onboarded by hand, and deliberately so: we confirm your publisher identity and configure your registry credentials with you rather than around you. The Professional listing covers up to three namespaces for £149 a year, plus a one-time £250 signing fee. Subscribe below and we will be in touch within two working days to set up your namespaces.
The listing includes registry-served discovery, public directory listing, and signed attestation infrastructure. Business listings (up to ten namespaces, £499 a year), Enterprise arrangements, and additional namespaces are available on request.
Prefer to talk first? Get in touch, or read the position paper.