Use cases
Worked-case posts. Each set covers one adjacent technology or decision space, in suggested reading order.
A use-case set is a small group of posts that work through one question together. Each post stands on its own. Read in order, they make a more complete argument than any single post can carry. The last post in a set is the integrator: it ties the others together and states the line plainly.
The first set covers MX, blockchain, NFTs, and cryptocurrency. It is the question that comes up most often when MX is introduced to people who have seen the blockchain wave already, and it deserves a plain answer. The standalone posts that follow cover specific buyer scenarios where MX changes the operational picture.
MX and the blockchain world
Four posts on what MX shares with blockchain, what it does not, where it adds something to a chain-as-record-system, and where it has nothing to say. Read in order; the fourth post draws the line.
1. What Blockchain and Crypto Have to Do with MX
MX is not a blockchain or a crypto project. It uses the same primitive (public-key cryptography) for a different job, with no ledger, no consensus, and no token.
2. Is MX Useful to Blockchain?
When a chain is used as a record system rather than a currency, MX is the discovery and structure layer that makes the on-chain record's content readable by machines.
3. NFTs and MX
An NFT proves ownership of a token. It does little about whether the content the token points at still exists, is unaltered, or can be read. That gap is MX's job.
4. MX and Cryptocurrency: Drawing the Line
Cryptocurrency is the part of the blockchain world MX has the least to do with. The integrator for the set, with the line stated plainly.
Compliance and regulated publishing
Standalone posts on where MX changes the operational picture for organisations publishing under regulatory pressure.
Proving What You Published: MX as a Compliance Defence, RAG as the Reader
Under the European Accessibility Act, regulated publishers are being asked to show what they published and when. RAG reads. MX proves. The two sit on different sides of the publisher and consumer boundary.
How Agents Discover Metadata: Carrier-Neutrality, Content Negotiation, and the Optional Cog
How structured COG metadata travels from Markdown to HTML, how HTTP content negotiation serves both humans and machines, and why the .cog extension is purely an optional human marker.