About InkReceipt

Why

Accused of handing in AI text? InkReceipt records how your text actually came together — typing sittings, pastes, deletions — and packages that process into a public, tamper-evident certificate you can link in your reply.

How the chain works

While you write, the pad saves regular checkpoints: how many characters you typed, deleted and pasted, plus a fingerprint (hash) of the document at that moment. Each checkpoint's hash also includes the previous checkpoint's hash, chaining them together. Issuing a certificate freezes the chain and stores your final text, so the record can be checked against it later.

1. Checkpoint — counts + document hash recorded while you write.
2. Chain — each checkpoint's hash includes the previous one, so any later change breaks the chain.
3. Issue — freezes the chain and stores the final text; the certificate link shows the whole record.

Tamper-evident, not tamper-proof: this proves your text was recorded and left alone afterwards, as recorded by a standard browser. It is not AI detection and does not judge the writing.

Limits

• Browser capture can miss IME and dictation quirks — some input methods may not be counted as ordinary typing.
• Stats say "as recorded" — they are a record of what the client observed, nothing more.
• No external timestamps yet (post-MVP) — times come from the server clock, not a trusted timestamping authority.
• Your text is stored publicly at the issued link, and cannot be edited or deleted afterwards.

MVP Lab Sprint 2 — a proof-of-process experiment.