Protocol overview
The protocol connects ordered edits to one sealed writing receipt.
HumanTyped is built around a narrow technical promise. A receipt should not be issued merely because a browser submits finished text; the server must be able to rebuild that text from the recorded operation sequence.
Ordered operations
Insertions, deletions, selection outcomes, and relevant integrity events form a journal for one session.
Independent reconstruction
The server replays the journal from an empty document instead of trusting only the browser's final copy.
Signed receipt
The sealed summary and validation state are bound into a receipt that can be checked later.
1. Observe the controlled session
The editor begins with an empty document and accepts direct editing operations. Paste and drop are rejected before they change the controlled text. The client records ordered changes and session context needed for continuity checks.
This observation window is deliberately limited to the HumanTyped editor. It does not inspect unrelated tabs, applications, clipboard contents, camera, microphone, location, or activity on another device.
2. Freeze and reconstruct
When the writer seals the session, editing stops and the operation journal is submitted for server validation. The server starts from an empty text and applies the recorded changes in order.
The reconstructed result is compared with the final text supplied at sealing using a digest. Missing, reordered, or altered operations that prevent a match also prevent the session from producing an ordinary valid receipt.
3. Score and seal the evidence
The system summarizes session-level evidence such as duration, revision behavior, cadence variation, continuity, and blocked transfer attempts. Exact private feature values are not published as a behavioral identity and should not be exposed to analytics.
The receipt contains the public fields required for verification, signature status, and clear limitations. Media is handled separately and bound by file hashes and metadata when attached; that proves the attachment set, not who created each file.
Evidence, not certainty