Protect Authors. Prove Process.
Writers deserve real proof of their work, and the world needs honest standards for AI use. I built WritersLogic to do both: protect human authors with behavioral evidence, and give everyone a framework for responsible, transparent AI-assisted writing.Writers deserve real proof of their work, and the world needs honest standards for AI use. I built WritersLogic to do both: protect human authors with tamper-proof evidence of their creative process, and give writers, institutions, and platforms a framework for responsible, transparent AI-assisted writing. Not detection. Not accusations. Evidence and proof.
-- David Condrey, Founder
How This Started
In 2024, I watched the conversation around AI and writing collapse into a binary: human or machine. Detectors claimed to answer that question with a single score. Writers were getting fired, expelled, and discredited. But the real problem wasn't the detectors. It was the question.In 2024, I watched the conversation around AI and writing collapse into a binary: human or machine. AI detectors claimed to answer that question with a single probability score. Writers were getting fired, expelled, and discredited based on numbers that even the tool makers admitted were unreliable. But the deeper I looked, the more I realized the real problem wasn't the detectors. It was the question itself.
"Was this written by AI?" is the wrong question. Writing with AI isn't cheating. Claiming AI-authored work as your own is. The distinction that matters is between AI-assisted and AI-authored, and that distinction requires evidence, not guesswork."Was this written by AI?" is the wrong question, because it assumes a binary that no longer exists. Writers brainstorm with AI. They use it to break through blocks, to rephrase awkward sentences, to explore structures they hadn't considered. That isn't cheating. What matters is whether the writer shaped the final work, and whether they're honest about the process. The distinction between AI-assisted and AI-authored is everything, and that distinction requires evidence, not guesswork.
So I asked a different question: what if the writer could attest to their process, and the tool could back it up with behavioral evidence? Every paste event prompts the writer to declare its origin. Every keystroke, pause, and revision is captured as behavioral signal. If a writer pastes a paragraph from AI but then goes back and extensively rewrites it, the evidence shows exactly that: AI-assisted, not AI-authored. The behavioral record either supports or refutes the attestation.
That's what WritersProof does. It doesn't judge. It doesn't detect. It captures the full behavioral record of how a document was created -- your natural writing rhythm, paste declarations, revision depth -- and locks it into unforgeable proof. The proof travels with your document. Anyone can verify it. The writer stays in control of the narrative, and the evidence keeps them honest.
Why This Matters
The old binary is broken. The new standard is transparency.
A writer who pastes a paragraph from ChatGPT, then rewrites half of it, restructures the argument, and weaves it into their own narrative has done real creative work. Current tools can't distinguish that from someone who pastes and submits. WritersProof can, because it captures the revision depth after every paste.
Each time you paste something, WritersProof asks you to declare its origin: your own draft, a quote, AI-generated text, or something else. Your writing behavior that follows either supports or contradicts that declaration. Honesty is rewarded with stronger evidence.
AI detectors give you a percentage and nothing else. No methodology, no explanation, no recourse. WritersProof produces a detailed behavioral record: what was typed, what was pasted, what was revised, and how deeply. Evidence you can examine, not a score you must trust.
Students can use AI as a learning tool and prove their engagement. Freelancers can demonstrate their creative process to clients. Institutions can set clear, evidence-based policies instead of relying on unreliable detectors. Transparency serves every side of the table.
Human authors deserve protection. Responsible AI use deserves real tools. WritersLogic builds both: unforgeable proof that defends the writers who do the work, and a verification system that brings transparency to how AI fits into the process.
What We Believe
Not abstract values -- concrete commitments you can verify
Proof you can examine, not scores you must trust
We don't detect AI. We prove authorship. Our methodology is published and auditable, and every report shows exactly which evidence supports the proof.We don't detect AI. We prove authorship. Our methodology is published and auditable. Every report shows exactly which evidence supports the proof -- which behavioral signals were captured, what the confidence intervals are, and where the evidence is thin. If we can't substantiate a claim, we don't make it.
In practice: WritersProof generates a detailed Authorship Report that breaks down exactly which signals contributed to the proof -- typing patterns, revision depth, session timing, and more. The protocol is open source under Apache-2.0.
Your writing stays on your machine
WritersProof is a native desktop application. Writing pattern capture -- keystroke timing, pause patterns, revision sequences -- happens locally on your device. Your raw text and writing data never leave your machine. What gets transmitted is only the proof: a small, tamper-proof record that proves the work happened, not a copy of the work itself.
In practice: Monitor your network traffic while writing in WritersProof. You'll see proof anchoring requests -- small signed payloads -- but never your text content. We architecturally cannot read what you write, even if compelled to try.
If the science doesn't support it, we don't claim it
WritersProof is built on tamper-proof evidence of effort -- not statistical guesswork. We capture the full record of your writing: what was typed, what was pasted, what was revised, and how deeply. The writer declares their process, and the evidence either supports or contradicts it. When something can't be substantiated, we don't report it as proven.
In practice: A WritersProof Authorship Report doesn't say "87% human." It shows which content was typed, which was pasted (and what the writer declared about its origin), how extensively each section was revised, and whether the writing patterns back up that declaration. That's evidence you can examine -- not a score you have to trust.
Authorship verification needs open standards, not vendor lock-in
Proving who wrote something is too important to be controlled by any single company, including ours. That's why we submitted the Cryptographic Proof of Effort (CPoE) Protocol as an IETF Internet-Draft, why our CPoE protocol is fully open source, and why we designed for compatibility with the C2PA content authenticity standard. If WritersLogic disappeared tomorrow, the proofs you've created would still be independently verifiable.
In practice: Authorship proofs created with WritersProof are anchored to public blockchains and signed with industry-standard security technology. Anyone can verify them using the open-source reference implementation -- no account, no subscription, no dependency on us.
How WritersProof Works
Real proof of effort -- not statistical guesswork
The WritersProof Engine
Your Natural Writing Rhythm
The measurable effort that only a real person produces while writing
- •Your unique typing speed and rhythm between keys
- •Thinking pauses -- where you stop to consider, not just where you stop typing
- •Revision sequences that reflect live decision-making
- •A writing fingerprint unique to each session and writer
Multi-Layered Security
Five independent signals locked together -- tamper with any one, and the whole proof breaks
- •Document content fingerprint
- •Your writing rhythm signature
- •Author identity verification
- •Timestamped blockchain anchor
Tamper-Proof Timeline
A chronological record that proves the order and timing of your writing
- •Each writing event links to the previous, forming an unbreakable chain
- •Retroactive fabrication is mathematically impossible
- •Any insertion, deletion, or reordering invalidates the proof
- •Chain anchored to public blockchain for independent verification
Unforgeable Proof
Tamper-proof evidence of your process and effort
- •Blockchain-anchored timestamps that prove when text existed
- •Verified proof linking your text to your identity
- •Immutable audit trail showing the complete writing process
- •C2PA-compatible for integration with content authenticity ecosystems
What We're Building
Desktop applications, an open protocol, and powerful security technology -- each built for a different need, all grounded in real evidence of your writing
WritersProof
A desktop application that captures your entire writing process as unforgeable evidence. Your typing rhythm, paste events with origin declarations, revision sequences, and thinking pauses are sealed into a tamper-evident Authorship Report that distinguishes AI-assisted from AI-authored work.
Everything stays on your machine. Paste something from AI? The app asks you to declare the origin. Edit it extensively? The record shows exactly that. Honest process, verifiable proof.
Learn about WritersProofCPoE Protocol
The open protocol underlying WritersProof. Defines how writing evidence is captured, locked into tamper-proof records, and anchored to public blockchains for independent verification. Built on proven security technology designed specifically for authorship verification.
Submitted as an IETF Internet-Draft. Designed for C2PA compatibility. Apache-2.0 licensed, because authorship proof infrastructure shouldn't be proprietary. If WritersLogic disappeared tomorrow, your proofs would still verify.
View on GitHubChronograph
A research-grade writing analysis tool built for academics. Hardware-secured data, precise timing measurements, built-in privacy protections, and AI-powered cognitive analysis -- all without transmitting your content.
Designed for academic studies in cognitive science, writing process research, and writing pattern analysis. Every data point is securely signed. Forgery is physically impossible.
Learn about ChronographWritersEye
A desktop writing application with AI integrations for analysis, not content generation. Writing voice recognition, inconsistency detection, and detailed authorship reports help writers, academics, and publishers understand and verify writing patterns.
One-time purchase. No subscription. AI assists with analysis -- identifying style drift, flagging inconsistencies, generating forensic reports -- but never writes a single word of your content. Your voice stays yours.
Learn about WritersEyeStandards & Open Source
Authorship verification that outlasts any single company
IETF Internet-Draft
Cryptographic Proof of Effort (CPoE) Protocol -- submitted to the Internet Engineering Task Force RATS working group. Defines a standard for tamper-proof authorship verification that any implementation can follow.
View on WritersProof Protocol DatatrackerC2PA Compatible
Designed for interoperability with the Coalition for Content Provenance and Authenticity (C2PA) standard. As the content authenticity ecosystem grows, WritersLogic proofs plug directly into it. Your proof of authorship travels with your content.
Open Source Core
The WritersProof protocol and reference implementation are Apache-2.0 licensed. The analysis methodology is published. You can audit every line of code that touches your data. We believe trust in a verification tool has to be earned, not demanded.
View on GitHubPublished Research
Detailed writeups on the Proof of Provenance protocol, the security methodology behind WritersProof, and the writing pattern model. Not behind a paywall. Not in marketing-speak. Actual documentation you can evaluate.
Read the researchWho's Behind This
David Condrey
Founder & Protocol Author
I've spent my career at the intersection of software engineering, security, and the written word, and I brought that rigor to authorship verification.I've spent my career at the intersection of software engineering, security, and the written word. Before WritersLogic, I worked on systems where getting verification wrong had real consequences -- and I brought that same rigor to authorship verification.
I started this project because I saw writing collapse into a binary: human or machine. But writers have always collaborated. AI is one more collaborator. What was missing was infrastructure to make the human effort visible.I started this project because I watched writing collapse into a binary: human or machine. But that binary never reflected how writing actually works. Writers have always collaborated -- with editors, workshops, beta readers. AI is one more collaborator. The people AI frees are writers who have lived through real experience but lacked the craft to compete with polished imitators. What was missing was infrastructure to make the human effort visible.
So I drafted the CPoE protocol, open-sourced it, and built a desktop app that captures how you actually write -- keystrokes, paste declarations, revision depth -- and seals it into unforgeable proof.So I drafted the CPoE protocol, submitted it as an IETF Internet-Draft, open-sourced the implementation, and built a desktop app around it that captures the full record of how you write -- keystrokes, paste events with origin declarations, revision depth -- and seals it into unforgeable proof anyone can verify. Not to catch cheaters. To make effort visible.
Get in Touch
Have questions about how it works? Want to talk about the science, the standards, or how to integrate authorship verification into your platform? I'd like to hear from you.