Receipts, not detectors

Click Clack records what entered a draft. This site is for the writer who has to hand that record over, and for the publisher, editor, or platform who has to check it.

Click Clack is a writing studio for people who will be asked what AI did.

Named collaborators — Figments — propose, research, and comment. You keep the byline. Each Figment proposal and each accepted edit is signed where it happens and chained to the draft it changed. When someone asks “did AI write this?”, you download a receipt instead of arguing with a detector.

This documentation is customer-facing. It is not an internal runbook. The job it has to do:

1. Help a writer export a signed history from Click Clack.
2. Help a publisher, editor, or platform check that file without a Click Clack account, and without trusting Click Clack’s website to tell the truth.

The second of those is the point. A receipt you can only view inside the product is a claim. A receipt a stranger can check on their own machine is a check.

Check a receipt

Independently verify a signed history. No app. No account.

Export signed history

Download the JSON receipt from Activity, not the Markdown manuscript.

What a result means

What a valid receipt proves, and the claims it refuses to make.

Timestamps

Optional OpenTimestamps evidence, and why a “confirmed” label is not authority.

Who this is for

Writers who need proof — novelists, journalists, and anyone else whose publisher, editor, or platform will ask what a machine contributed. The person you hand the file to is the second reader of these pages. They should be able to follow Check a receipt without signing in.

What you will not find here

Operator runbooks, design-system internals, and working notes stay in the product repository. They are not this site.

Verification is never colour alone. In Click Clack a signed contribution shows an icon and a label. On this site, a check is an exit status from the verifier, not a green badge in a screenshot.