What an attestation can tell you.

An exact version. A signing identity. Evidence with limits. Inspect a working sample, then explore how a writer could share a record under a pen name.

Try the evidence check

Educational demo · about five minutes. No account or document connection. The fingerprint check works and compares content only; identity and publication examples are planned capabilities.

From writing to a portable record.

Planned example: how the service is designed to work, alongside a working fingerprint check below.

Step 1 of 4

Write in your document

Your work stays in your workflow.

A private prototype, which is not running, is designed to read one Google Doc the writer chooses and compute a fingerprint from the exported text.

  1. 01Observe available snapshots
  2. 02Record gaps when capture fails
  3. 03Keep saving separate from evidence

One small edit. A different fingerprint.

Check the sample, change a word, then check again. The signed reference stays the same.

Sample documentVersion 2

A draft becomes a record

This short synthetic text matches the downloadable sample evidence package exactly, including the final newline.

This check runs in your browser and compares content only. Text entered here is not sent to our servers or saved by this demo.

Evidence referenceSynthetic sample

The version is the reference.

Attribution
Key only: a server-held sample key signed this version. No independently verified person is asserted.
Time
Not established. No external timestamp proof is included in this sample.
Content fingerprint
c91b63e06a54860b7208e7a157ae7e878c43830df06bb27da69734fb0d09f587
Ready to compare

Check the text against the fingerprint in the signed sample bundle.

This browser check compares content only. It does not verify the signature, log proofs, identity or timestamp.

Who stands behind the key?

Planned example. Each level would name the identity evidence checked. It is not a score for writing quality, honesty, or how much AI was used. Stronger identity evidence does not prove human composition.

  1. Signing keyLevel 0

    A key signed this version. No independently verified person is asserted.

    Used by the synthetic sample · server-held key

  2. Account controlLevel 1

    Control of a sign-in account. This does not establish legal identity or independently portable assurance.

    Planned

  3. Public identifier controlLevel 2

    Control of a domain or profile, bound to a signing key. A pen name can use this.

    Planned · first identity method: domain control

  4. Organizational connectionLevel 3

    The specific mailbox or institutional relationship checked. No endorsement of every work.

    Planned

  5. Identity verificationLevel 4

    An issuer checked identity by a named method. A public assertion can keep the legal name private.

    Planned example · no live identity check

  6. Electronic identityLevel 5

    A supported external eID supplies its defined assurance. It still does not prove who composed a passage.

    Future · no integration promised

AI-use disclosure is a separate statement

Draft vocabulary for an author’s own statement, not detector findings or more identity levels. These policies are not implemented in this demo.

D0
No generative AI in composition
D1
Mechanical assistance
D2
Substantive assistance
D3
AI draft with human revision
D4
Substantially unedited AI output

No author’s D-level appears on the public receipt illustration.

A public pen name. A private person.

Meet Rowan Vale, a fictional writer. Compare control of a public domain with a planned check of the person behind the pen name.

Planned example. Rowan, the private details and check dates are invented. No domain or legal identity is being verified.

Identity example
View as

What a reader learns

A domain-control assertion would connect rowan.example to Rowan’s signing key. It would not establish a legal identity or certify everything on that site.

This view selector explains visibility; it is not access control. All demo details are public fictional material. A real public response must never contain the private fields, even in a hidden panel.

Planned public receipt · fictional

A draft becomes a record

Rowan Vale · rowan.example

Version
Version 2 · the synthetic sample above
Attribution
Domain control linked to a signing key. Illustrated, not checked.
Method and issuer
DNS challenge and key binding · Real Press (proposed check).
Example validity
26 September 2026–26 September 2027 · invented dates
Time
Not established from this public illustration.
Evidence details
No signature binds Rowan to the sample. This is an unsigned teaching illustration, not input for the verifier. A live receipt would disclose server-held signing custody and independently trusted issuer evidence.
Download public illustration

No legal name, private email, draft history or author AI-use statement.

A mutable display name beside a signature is not enough: a live receipt must bind the pen name to its signing key. Separate personas need separate identifiers and keys; reused domains or content can still connect them. Identity evidence never proves who composed each passage.

Sharing and being listed are two choices.

Signing and logging would not publish your work. Publishing a receipt would make it readable by anyone who gets the link. Directory listing would make it discoverable. Try those choices with the fictional receipt.

Local simulation. These controls change this example only. Nothing is published, listed or withdrawn on Real Press.

Private example

The fictional receipt has no publication or listing consent. Previewing it grants neither.

Where does the public ledger fit?

Planned example. How the layers are designed to fit together.

Private evidence
The signed held package, draft proofs and private identity linkage, which the author would share only deliberately with authorized recipients.
Public receipt and directory
A separately signed public artifact, with listing as a separate opt-in. The directory would be a removable discovery view. Payment and legacy detector scores would confer no author assurance.
Transparency log
Salted commitments and verification proofs would establish what was logged and, with independent evidence, when. They would not publish legal names or private drafts, or prove a statement true. This demo adds no log explorer.

The evidence can leave the platform.

Download the sample evidence package: a signed record with proofs for checking its place in the log and its sequence of draft snapshots. The open-source verifier and a step-by-step guide are available here, with no account needed.

These files contain test-only data. In real use, this complete package is private and may reveal draft evidence. The test log key lets the verifier check this sample only. Obtain real log keys from an independent, trusted source.

The address https://log.real.press/v1 inside these files identifies the synthetic test log. It is not a live website or log explorer, and verification does not contact it.

Download sample evidence Download test log keyOffline verifier & instructions

Evidence you can inspect. Room for honest uncertainty.

What the offline verifier checks

Whether signed evidence binds to a particular content fingerprint; whether commitments are included in a log; and whether external time evidence validates, when it is present. The synthetic sample includes none.

What it does not establish

Who composed each passage, whether AI was used, or whether every edit was captured. The demo and the sample check no one’s identity. For work without evidence, “no attestation found” is neutral; it is not a reason to distrust its author.

What you can try today

Compare the sample text here, then check the downloaded evidence offline. This is a synthetic demonstration; it does not report live pilot progress. Connecting your own documents is not available on this page, and no account or subscription is needed.