Show how you wrote it.
Bring the document. Nota reads what its history says — and issues a signed record with a link a teacher or editor can verify in ten seconds. Counts and dates, not a score. Nothing to install; nothing stored until you say so.
Google asks you to allow Nota to see the file you pick — that one document, nothing else in your Drive. Nota reads its revision history once and shows you the ledger. Works after the fact: the history is already in the document.
Have the Chrome extension? It reads this from inside a Google Doc today, keystroke by keystroke.
Three steps, two of them yours.
Bring the document
Upload the .docx, or — once Google Docs is switched on — pick the document in Google’s own file picker. One file. It works after the fact: the history is already in the document.
Read the ledger
What the history recorded, said as a receipt: sessions, editing time, what arrived at a typing pace and what arrived faster, what was cut, the final size. Nothing has been stored yet.
Issue the signed record
Add a declaration if you want, then sign. You get a link, a PDF and the JSON. Whoever opens the link sees what was observed and can check the document they hold against it.
A ledger, not a grade.
Every number is a count, a date or a duration the document’s history recorded. Nota’s reading of the final text is one line beneath, with its measured error rate. There is no “human score” — one number would be one thing to game, and a false certificate is as harmful as a false accusation.
Typed ≈4,100 words over 3 sessions (2 h 40 min, 12–15 May 2026) and cut ≈1,900. 310 words arrived in 2 blocks — faster than typing between saves. The final document is 2,650 words: a 1.7 : 1 written-to-final ratio.
Nota’s reading of the final text: looks like human writing · error rate 1.28%.
- Observed
- The process above; the character check
- Inferred
- The model’s reading, with the rate at which it is wrong about real human writing
- Declared
- Your statement, if you make one — signed as yours, not verified
- Signed
- Ed25519, by Know Nota; verifiable at the link against the document’s fingerprint
Who brings one.
A student who was flagged
A detector said “likely AI”. The essay was written over three evenings in Google Docs. The record shows that — signed by someone who is neither the student nor the school — and the teacher checks it in ten seconds.
A course that allows AI
The syllabus permits AI for drafting from your own notes. Declare exactly that on the record, beside the process that shows the notes went in first. Honest use gets a paper trail.
An editor or a client
Before the piece runs, the writer attaches the record. Editing time, sessions, what arrived in blocks — and a declaration of what tools were used. No interrogation needed.
Teachers: how to read a Writing Record. Writers who work in Google Docs every day: the Chrome extension issues the record from inside the document, keystroke by keystroke.
Questions people ask first.
What does Nota read, exactly?
For a Google Doc: that one document’s revision history — when it was edited, how much text arrived per save and at what pace, what was cut, how many editors. For a .docx: the properties the editing application wrote into the file — created, last saved, editing time, save count. For a PDF or text file: the words only. In every case Nota also reads the final text and puts its own reading in the record, with the measured error rate.
Does this read everything I do?
No. Nothing is installed and nothing runs in the background. You bring one document; Nota reads that document once, shows you what it found, and stores nothing until you choose to issue the record. With Google Docs the permission you grant covers the file you pick and nothing else in your Drive.
Is a Writing Record proof that I wrote it?
It is a signed statement of what was observed in the document’s own history, issued by a party that is not you and not your school — that is its weight. It is not a certificate. Typing can be scripted, file properties can be edited, and a declaration is your own word; the record says all of that in plain text so a reader takes it for what it is.
What does it never say?
It never says “human-written” or “AI-written”, never names a generator, and never scores you. The ledger is counts, dates and durations. Nota’s reading of the text appears as one line with its measured error rate, never as a verdict.
Why not Word?
Word keeps no revision history a third party can read, and the desktop app has none. A .docx does carry what Word recorded about its making — editing time, saves, dates — and the record reads that today, labelled as what it is. Google Docs keeps the document’s history on Google’s servers, which is why the deeper record is possible there.
What does it cost?
A Writing Record — one with the document’s history in it — is free to issue, share and download on every plan. Records for documents that carry no history (PDF, text) are on Individual and up, like any other Nota Record.
What if I used AI and was allowed to?
Say so, on the record. “AI drafted from my notes”, “AI edited my draft” — the declaration is signed as your statement, beside the observed process, so honest use has a paper trail instead of a suspicion.
Ready when you are.
Nothing is stored until you issue the record. Free.