What about a more flexible approach ? #18

rmdes commented 2026年03月16日 12:51:53 +01:00

I went and added AI usage metadata to my JSON-LD also added a AI usage page https://rmendes.net/ai/ and every posts on my blog have a easy to read/interpret AI usage transparency card;

{ 
 "@context": "https://schema.org",
 "@type": "Article", 
 "headline": "Cult Dynamics at the Scale of Rogue Democracies",
 "url": "https://rmendes.net/articles/2026/03/11/cult-dynamics-at-the-scale-of-rogue-democracies/", 
 "mainEntityOfPage": {
 "@type": "WebPage", 
 "@id": "https://rmendes.net/articles/2026/03/11/cult-dynamics-at-the-scale-of-rogue-democracies/" 
 },
 "datePublished": "2026年03月11日T12:55:28.065Z",
 "dateModified": "2026年03月11日T12:55:28.065Z",
 "author": {
 "@type": "Person",
 "name": "Ricardo Mendes",
 "url": "https://rmendes.net/"
 },
 "publisher": {
 "@type": "Organization",
 "name": "A Node on the Web",
 "url": "https://rmendes.net",
 "logo": {
 "@type": "ImageObject",
 "url": "https://rmendes.net/images/og-default.png"
 }
 },
 "description": "I was born and grew up inside an authoritarian Tibetan Buddhist hippie community that slowly revealed itself to be a cult. Why am I telling you this? Because on...",
 "usageInfo": "https://rmendes.net/ai",
 "creativeWorkStatus": "Text: Co-drafting, Code: AI-assisted, Tools: Claude"
 }

I use the field "creativeWorkStatus" to display if my post contains AI usage or not

I went this direction because I think, AI on blogs is not a blanket, its not ALL or nothing, it should be granular, per posts.

And just because one co-draft a tutorial or long form with an AI does not mean or equal "full AI generated"

I posit that this approach will be implemented in different ways but will ultimately be common in just a few months/years

Now I'm wondering, i think human.json is a neat idea, but is there a chance the human.json idea could be more flexible ?

I went and added AI usage metadata to my JSON-LD also added a AI usage page https://rmendes.net/ai/ and every posts on my blog have a easy to read/interpret AI usage transparency card; ``` { "@context": "https://schema.org", "@type": "Article", "headline": "Cult Dynamics at the Scale of Rogue Democracies", "url": "https://rmendes.net/articles/2026/03/11/cult-dynamics-at-the-scale-of-rogue-democracies/", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://rmendes.net/articles/2026/03/11/cult-dynamics-at-the-scale-of-rogue-democracies/" }, "datePublished": "2026年03月11日T12:55:28.065Z", "dateModified": "2026年03月11日T12:55:28.065Z", "author": { "@type": "Person", "name": "Ricardo Mendes", "url": "https://rmendes.net/" }, "publisher": { "@type": "Organization", "name": "A Node on the Web", "url": "https://rmendes.net", "logo": { "@type": "ImageObject", "url": "https://rmendes.net/images/og-default.png" } }, "description": "I was born and grew up inside an authoritarian Tibetan Buddhist hippie community that slowly revealed itself to be a cult. Why am I telling you this? Because on...", "usageInfo": "https://rmendes.net/ai", "creativeWorkStatus": "Text: Co-drafting, Code: AI-assisted, Tools: Claude" } ``` I use the field "creativeWorkStatus" to display if my post contains AI usage or not I went this direction because I think, AI on blogs is not a blanket, its not ALL or nothing, it should be granular, per posts. And just because one co-draft a tutorial or long form with an AI does not mean or equal "full AI generated" I posit that this approach will be implemented in different ways but will ultimately be common in just a few months/years Now I'm wondering, i think human.json is a neat idea, but is there a chance the human.json idea could be more flexible ?