Writing receipts
A writing receipt shows the process behind a finished text.
A writing receipt is a shareable record attached to one sealed writing session. It connects the final text to observable process evidence instead of making a prediction from the words alone.
Bound to one text
The receipt refers to a specific sealed result rather than a general claim about an account or author.
Inspectable by readers
A public URL presents the session summary, validation state, and the boundaries of the evidence.
Narrow by design
The receipt describes an observed session; it is not an identity certificate or a universal AI test.
What goes into a receipt
HumanTyped begins with an empty controlled editor. Accepted insertions and deletions are journaled in order. When the writer seals the session, the server replays those operations and checks that they produce the same final text submitted by the browser.
The public receipt exposes a deliberately limited summary. It may show the sealed post, writing duration, edit count, evidence score, signature state, and an available replay. Private scoring inputs and raw event data are not turned into public analytics or search pages.
How a reader should interpret it
A valid receipt is evidence that the displayed text is connected to the recorded HumanTyped session. A reader can use that information alongside the content, the publisher's reputation, sources, and any disclosure of outside assistance.
The score is a summary of signals from one session, not a percentage chance that a person is human. A high score does not make a statement true, original, lawful, or free from help received before or during the session.
Where receipts are useful
Receipts are most useful when the process itself is relevant: a post is challenged, an editor wants a transparent submission trail, or a creator chooses to add evidence before a dispute begins. They are less useful when the real question is plagiarism, factual accuracy, or legal ownership.
For social publishing, the receipt can travel as a link under the original post. That keeps the claim close to the content while letting readers inspect the evidence without receiving a private draft or account access.
Evidence, not certainty