Declare Once, Work Everywhere

2 June 2026 · Tom Cranstoun · 4 min read

Every machine reading your content right now is guessing. It guesses what your pages sell, whether they are sensitive, how much to trust them, and whether to act on them at all. It does that work fresh, on every page load, independently of every other machine doing the same thing on the same content. None of those guesses are yours to see or correct.

We change that.

The Problem

AI agents, browsers, search systems, and assistants are reading your content to serve their users. That is not the problem. The problem is that they do it by inference, and inference is private. Chrome carries internal lists - built into the browser binary, updated without notice - that decide whether an agent may act on your pages. A shopping model chops each page into hundred-word chunks and judges whether you trade. Assistants form their own read of your credibility and quote accordingly. None of it is disclosed, none of it is contestable, and none of it reflects what you have said about yourself.

The result is a web where the decisions made about your content are made without you. When they are wrong, there is no one to answer for it.

The Inflection

Two things happened in June 2026 that mark where this is heading.

Salesforce paid to acquire Contentful. The stated reason is agent infrastructure: content assembled by machines, delivered across channels, managed inside one vendor's stack. Agent-readiness is now a platform feature you purchase and a register you join. Withdraw from the platform and the signal leaves with you.

In the same month, researchers reverse-engineered the classification data Chrome ships alongside itself. More than thirty thousand domains gated from AI assistant actions. Another thirty thousand selected for semantic indexing. A live model deciding page by page whether you count as commerce. All of it written by one vendor, for one vendor's purposes, with no route to read or contest your entry.

The market has confirmed that machines need structured signals about content. The question it has not answered is who writes those signals, and whether the site has any say.

What We Do

We make content that manages itself.

A COG is a carrier-neutral record that travels with the file: what it is, who produced it, when it changed, how machines should treat it. The format is open, governed by The Gathering, published under an open licence. Any system can read it. No vendor owns the schema.

REGINALD adds the trust layer. An Ed25519 signature over the canonicalised bytes lets any reader confirm the record is genuinely yours and has not been altered in transit. The signature covers provenance and integrity. It does not make claims about editorial truth - that judgement stays with you and your readers. It gives the record an author and a date, so a machine that reads it knows whose word it is taking.

The pair - COG plus REGINALD attestation - means your content introduces itself to every system that encounters it. Not through a vendor's API, not through membership in a list you cannot see, but through a record in the file itself.

What You Get

Content that is machine-readable on your terms, not inferred on someone else's. When an agent reads your page and misrepresents it, you have a signed, dated statement of what the page actually says - and you have an accountable author, which is more than the inference has.

Content that travels. Platform lock-in is the dependency on a vendor to explain your content for you. A COG removes that dependency. The record is in the file. Move the file and you move the record.

Evidence for governance. The AI Act, accessibility regulations, and digital-records law are moving in the same direction: disclosed, attributable, auditable decisions. A structured, signed declaration is the kind of evidence those regimes expect. We make that evidence. We do not make you compliant - compliance is a legal duty - but we make the documentation that compliance requires.

How to Start

The fastest entry is an MX audit. We assess your current content against the machine-readability standard, score it against what agents and browsers actually resolve, and tell you exactly what to fix and in what order. Most organisations find the gap is smaller than it looks: the structured content work their CMS already forces is most of the journey. What is missing is the record that travels with the file.

From there we work with your team to implement COG metadata, connect REGINALD attestation for the records that carry regulatory weight, and build the content infrastructure that no acquisition can take away.

Write to us at info@cognovamx.com or read what we offer at cognovamx.com/services.