<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Andrejs Leontjevs</title>
    <description>The latest articles on DEV Community by Andrejs Leontjevs (@andrejs_leontjevs_02f8325).</description>
    <link>https://dev.to/andrejs_leontjevs_02f8325</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3922144%2F99316e29-a9ea-4382-86b7-76992638ef70.jpg</url>
      <title>DEV Community: Andrejs Leontjevs</title>
      <link>https://dev.to/andrejs_leontjevs_02f8325</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/andrejs_leontjevs_02f8325"/>
    <language>en</language>
    <item>
      <title>Moving Beyond Probability: A Forensic Approach to Proving Human Authorship</title>
      <dc:creator>Andrejs Leontjevs</dc:creator>
      <pubDate>Sat, 09 May 2026 16:29:23 +0000</pubDate>
      <link>https://dev.to/andrejs_leontjevs_02f8325/moving-beyond-probability-a-forensic-approach-to-proving-human-authorship-3o4h</link>
      <guid>https://dev.to/andrejs_leontjevs_02f8325/moving-beyond-probability-a-forensic-approach-to-proving-human-authorship-3o4h</guid>
      <description>&lt;p&gt;In the current landscape of generative AI, the conversation around "authorship" is becoming increasingly fraught with errors. We’ve all seen it: a student or a freelancer submits original work, only for it to be flagged by a probabilistic AI detector.&lt;br&gt;
The problem is that most detectors (like GPTZero or Turnitin) rely on linguistic pattern matching—calculating perplexity and burstiness. This is essentially an educated guess based on word frequency. It’s a method that is prone to false positives, especially for technical writers or non-native speakers who naturally use structured, "predictable" language.&lt;br&gt;
I decided to take a different approach. Instead of analyzing what was written, I focused on how it was created.&lt;br&gt;
The Forensic Pivot: Proof of Human&lt;br&gt;
Proof of Human is a utility designed to substantiate human effort through forensic metadata analysis rather than linguistic probability. It operates as a Google Docs Add-on to provide an objective "digital heartbeat" of the creative process.&lt;br&gt;
The Technical Breakdown&lt;br&gt;
Rather than looking at the final strings of text, the tool audits the internal document metadata and revision history to identify three key forensic markers:&lt;br&gt;
• Typing Cadence Analysis: Humans have a distinct mechanical rhythm. We pause to think, backspace to refactor sentences, and have variable delay between keystrokes. AI-generated text insertion is typically instantaneous or robotic.&lt;br&gt;
• Revision History Audit: An organic document has a specific growth curve. It starts with an outline, followed by iterative drafting and refinement. By mapping these timestamped events, we can distinguish between a natural evolution of ideas and a "bulk injection" of content.&lt;br&gt;
• Manual vs. Paste Ratio: The tool calculates the volume of manually typed characters against the volume of pasted text. While pasting is normal for research, a document where 95% of the content appears in a single timestamp is a clear indicator of automated generation.&lt;br&gt;
Authorship as Insurance&lt;br&gt;
The goal here isn't to "catch" people using AI, but to provide Authorship Insurance for those who don't.&lt;br&gt;
When a freelancer or student finishes a draft, they can run a deep audit to generate a Humanity Score and a verifiable Humanity ID. This ID can be shared with clients or editors, who can then use a public lookup tool to verify the forensic logs. It settles the argument with data instead of opinions.&lt;br&gt;
Implementation&lt;br&gt;
Building this within the Google Workspace ecosystem allowed for the most granular access to revision logs. The tool parses the revisions resource to reconstruct the document's history and provide a transparent report on the labor spent "in the chair."&lt;br&gt;
I’m curious to hear from the community: As generative tools become the norm, do you think we’re moving toward a world where forensic process-verification is a requirement for high-stakes writing?&lt;br&gt;
I've made the tool available at kyrosig.com for anyone who needs to prove their process.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
