The Problem
Generative AI broke the implicit trust contract between writers and their readers.
For most of history, if someone submitted an essay, a report, or an article, you could assume a human wrote it. That assumption no longer holds. The dominant response has been AI detection — classifiers that try to determine whether text was machine-generated. Detection is the wrong framing. It's probabilistic, produces false positives, and degrades as models improve. A student who wrote their own essay can be flagged. A journalist with a genuine scoop can be accused of fabrication.
The right question isn't "did a human write this?" — it's "can this person prove they wrote this?" Proof is binary. Detection is probabilistic.
Approach
Scripli establishes authorship through process evidence rather than content analysis. The document never leaves the user's device. What gets recorded and sealed is evidence of the writing session itself — enough to demonstrate a human was at the keyboard, without revealing what they wrote.
The result is a certificate: a short, shareable identifier that maps to a public verification page anyone can check without an account.
Privacy as a Hard Constraint
Zero content storage is not a policy promise — it's an architectural constraint enforced at every layer. The system is designed so that no document text can be transmitted or stored even if a developer wanted to. A technically sophisticated user can confirm this independently without needing to trust the platform.
This constraint ruled out a large class of simpler implementations and shaped every major technical decision in the product.
Public Verification
Any certificate can be verified by anyone, without an account. A certificate identifier maps to a public page showing who issued it, when the session ran, and whether the seal is intact.
The value is not the certificate itself — it's that the certificate can be checked independently. A hiring manager, a professor, or an editor can verify without treating Scripli as a trusted intermediary. The verification path is intentionally minimal and cacheable.