Why I’d log AI content provenance in post meta today

If your client’s editors write half their product descriptions with an AI tool this year, someone will eventually ask which half. WordPress does not know, and after the latest core AI meeting it will not know centrally for a while either: the team parked the C2PA signing approach and pointed at a local origin log instead. That local log is the piece of AI content provenance you can build today, on an ordinary site, without waiting for WordPress 7.1.

What the team decided

The details are in the AI contributor weekly summary on make.wordpress.org, covering the 3 June meeting. The short version: a vendor named Encypher submitted three large pull requests for content provenance logging. The C2PA specification needs an authoritative server to sign asset manifests, and the obvious candidate was WordPress.org itself. The team worked through two problems with that. A central signer that stamps user-generated media reads as endorsement, which turns one malicious upload into a platform liability. And with no decentralized option in the PRs, merging them would funnel a core feature into a single paid signing service. Jason Adams suggested waiting for localized signing to mature, and Jeff Paul proposed the alternative that interests me: a lightweight experiment inside the AI plugin that keeps an internal history loop in post revision meta and records when content was AI-generated, human-written, or AI-assisted.

I agree with the wait, and I would go one step past the plugin experiment. The revision framework that the marker needs has shipped in core since 6.4, so you can start keeping this record on client sites now.

Why revision meta is the right home for AI content provenance

WordPress has revisioned post meta since 6.4. You opt a meta key in through the wp_post_revision_meta_keys filter and core copies the value into each revision alongside the content snapshot. That gives you the property you want: the origin marker is tied to the exact version of the content it describes, so the post carries the newest marker and every older revision keeps its own. The framework post on make.wordpress.org/core walks through the details, including the query gotchas when meta starts living on revision IDs too.

The record also travels with the site. Exports, backups and staging pushes all carry post meta, while a signing service keeps its records somewhere else and loses them when the account dies. And it answers the question site owners get asked, which is editorial rather than forensic. C2PA proves a file’s lineage to a stranger; revision meta tells your editor which draft was machine-drafted and which one a human rewrote. They are different products, and it is worth being clear with clients about which one you are delivering.

The other side has a real point, though. A local log proves nothing to a third party. Anyone with database access can rewrite post meta, and markers vanish when old revisions get pruned. If you are under a regulatory disclosure rule you still want signatures. For an internal record, meta is enough.

The code I’d ship

This is the whole pattern, minus the editor UI.

<?php
add_filter( 'wp_post_revision_meta_keys', 'bbioon_revision_origin_keys' );
function bbioon_revision_origin_keys( $keys ) {
	$keys[] = '_bbioon_content_origin';
	$keys[] = '_bbioon_origin_logged_at';
	return $keys;
}

add_action( 'save_post', 'bbioon_log_content_origin', 10, 2 );
function bbioon_log_content_origin( $post_id, $post ) {
	if ( wp_is_post_revision( $post_id ) || wp_is_post_autosave( $post_id ) ) {
		return;
	}
	if ( ! current_user_can( 'edit_post', $post_id ) ) {
		return;
	}

	// Tooling sets this before the save lands: 'ai-generated', 'ai-assisted', or 'human'.
	$origin = get_post_meta( $post_id, '_bbioon_pending_origin', true );
	$origin = $origin ? $origin : 'human';

	update_post_meta( $post_id, '_bbioon_content_origin', $origin );
	update_post_meta( $post_id, '_bbioon_origin_logged_at', time() );
}

The pending marker is what your integration sets. A block editor sidebar, or the generation step in an AI workflow, calls update_post_meta() with ‘ai-assisted’ before the save request goes through, and the hook promotes it to the revisioned key. Anything that saves without a marker logs as human. That is a guess, and it is the weak point of the whole approach: the log is only as truthful as the tooling that reports into it.

What to test before you rely on it

  • Revision pruning. WP_POST_REVISIONS defaults to keeping a bounded number of revisions, and revisioned meta is deleted along with them. If the record has to be permanent, append to a custom table or a site option instead of meta.
  • Revisions switched off. Some hosts and agency boilerplate set WP_POST_REVISIONS to false. The live post still gets the marker, but you lose the per-revision history, which is the point of the exercise.
  • REST and headless frontends. Keys with a leading underscore are hidden from the REST API unless you register them with show_in_rest, so a decoupled frontend will not see the markers without extra wiring.

If you want this connected to a real editing flow, with the generation step setting the origin flag and an admin column showing the history per post, that is the kind of build I do for store and publisher clients. Send me your setup and I will tell you where it fits.

Skip all of it if your only requirement is public disclosure. A visible byline or a meta tag does that job with none of the moving parts. Build the log when you need the internal history, and check what your host does to revisions before you trust a single entry.

author avatar
Ahmad Wael
I'm a WordPress and WooCommerce developer with 15+ years of experience building custom e-commerce solutions and plugins. I specialize in PHP development, following WordPress coding standards to deliver clean, maintainable code. Currently, I'm exploring AI and e-commerce by building multi-agent systems and SaaS products that integrate technologies like Google Gemini API with WordPress platforms, approaching every project with a commitment to performance, security, and exceptional user experience.

Leave a Comment