Start writing

What a certificate cannot prove

Last updated 15 October 2026

What does a certificate establish?

A certificate is evidence about one writing session. Some of what it says can be checked by anybody, without trusting iwrote:

  • The link has not been changed since iwrote issued it. It is signed with a key whose public half is published at iwrote.co/.well-known/jwks.json, so the check is arithmetic anyone can do, offline, with ordinary tools.
  • It existed by the date it states. A timestamping service iwrote does not run signs the date, so that date rests on their clock and not on iwrote's word.
  • Which text it is a record of. It carries a fingerprint of the words, so anyone holding the piece can check it is the same piece, word for word.
  • How much of the session iwrote itself saw. While somebody writes, the page asks iwrote to countersign how far the record has got, on iwrote's own clock. A certificate countersigned fourteen times across thirty-eight minutes could not have been made by replaying a finished session quickly. One countersigned once tells you iwrote saw it only at the end, and says so.
  • If the writer publishes the log, or hands it to you: every figure on the page, recomputed from every edit in your own browser, with nothing sent anywhere.

What can’t a certificate establish?

That the counts are true. They are taken by iwrote’s page, running in the writer’s own browser, and a page in a browser can be interfered with. A signature proves the link says what iwrote signed; it does not make what the browser reported into a fact. Every certificate says this on its face.

That the ideas are the writer’s. A record describes how text arrived, not where it was thought of. Something read elsewhere and retyped by hand looks like something written from scratch, and an argument worked out with a friend, a tutor or a model and then typed out in the writer’s own words is, as far as a record can tell, typed.

That a person was typing. Programs exist that type out prepared text a character at a time, with pauses and mistakes put in. The counts alone cannot tell that from a person. The countersignatures cannot either: a script can ask for them on schedule. What stands in the way is the iwrote engine’s reading of the session’s rhythm, which withholds the mark from a session it cannot place as somebody’s writing. It will not catch every such program.

Who was at the keyboard. The name on a certificate is the account that certified it. Somebody else typing on that account, or at that desk, looks the same.

Where pasted text came from. A record says that text arrived at once, and whether it was a passage replaced by a nearly identical one. It never says where it came from, because it cannot: a correction looks the same whether it came from a spellchecker, a model, a friend or the writer reading it back later. Text already in the box when recording began is marked as such, and nothing is said about it beyond that.

Where can the reading be wrong?

The mark, Written by a human, has two gates. The first is arithmetic: the record checks out, names this text, accounts for every character in it, and runs to at least ten words. The second is a reading by the iwrote engine, a model that is sent the counts and never a word of the writing. A reading is a judgment, not a measurement:

  • It has not yet been measured against a large set of real, labelled sessions. Until it has, its thresholds are set by hand.
  • Writing by dictation, with an input method for a language like Japanese or Chinese, or in a second language, has not been tested, and may read differently from how it happened.
  • A browser under load, a page closed mid-sentence, or storage the browser cleared on its own can make a session read differently from how it happened.

When the engine cannot settle between two readings, the page says both and prints the more cautious. When it withholds the mark, the certificate is still issued and says what was recorded.

How should I use a certificate?

Weigh it as evidence, alongside everything else you know. If it matters, ask the writer for the log: it checks on the certificate page itself, in your browser, and it is the difference between reading the figures and recomputing them.

Do not treat a certificate as proof of authorship, and do not treat the absence of one as grounds for an accusation. Most writing in the world was written without iwrote, by people who wrote every word of it.

What if I find a way around it?

Tell us, at arpan@iwrote.co. A limit somebody reports goes on this page, and on the certificates, in the same plain words as the rest. To see what a reader is shown, open the example certificate.