Provenance
Posts on what content needs to carry to prove its own origin - signed records, readable evidence chains, and the gap between access and trust.
A machine can read a file without knowing who made it, when, or whether it has changed. That gap matters most at the moment of decision: when an agent cites a source, when a regulator asks who produced a claim, when a buyer wants to know if the price they read is the price that was offered.
These posts argue the case from concrete examples: a PDF that carries its own evidence chain, a padlock that attests the pipe and not the page, software agreeing to deals without a human in the exchange. Each post names the gap and what the next layer needs to close it.
Posts
The Padlock Attests the Pipe, Not the Page
The TLS padlock has been the web's most-misread icon for twenty years. It says the connection is encrypted; it has never said the page is true. Closing the gap takes content that carries its own evidence and a verification step that runs on the reader's side.
A PDF That Can Prove Itself
Every PDF this site produces now carries its own evidence chain inside its XMP packet. Open the file with no network and no source repo and an inspector can still read who made it, when, what it was rendered from, and what the chain is silent about. The honest absence matters as much as the present steps.
The Inspector You Can Audit Yourself
The public PDF inspector at mx.allabout.network checks one file at a time for free. The same detection core is now available as a command-line tool for accredited operators, and as a hard gate in our own publishing pipeline. Four surfaces, one source of truth, all readable in the open.
Read Is Not the Same as Trusted
Common Crawl's AI Visibility Audit confirms that reachability decides whether a site enters LLM training. It does not address whether the ingested content can prove where it came from. That is the MX layer.
Software Agreed the Deal. Who Is Accountable?
Software is starting to negotiate contracts with other software, no human in the exchange. The answer is not a human in the loop but a human in command: a signed mandate the agent executes under, and the decision, policy and attestation COGs that prove it.