Introduction — human.cv Docs

human.cv is a protocol for verifiable, permanent ownership of what you make. It does not try to prove a human typed the keys — it proves something you can actually stand behind: that a verified human claims this work, and takes responsibility for it, forever.

The shift

For most of history, the work and the proof of who made it were the same object. Scarcity carried authorship automatically. That bond is now broken: when a machine can generate anything, the artifact is no longer evidence of anyone. Abundance dissolves attribution.

human.cv restores the missing half. It is the place to press your hand to the wall of the internet and have it stay — a permanent, verifiable trace that a specific human chose to claim a specific thing.

What it proves

A verified human claims this work as theirs, recorded on-chain, and can prove that claim to anyone, at any time, permanently. Ownership and responsibility — not authorship as a forensic fact, but authorship as a deliberate, accountable choice.

What it does not

It never claims a machine wasn’t involved. Proving the absence of a tool is unprovable and adversarial — and beside the point. We never asked a photographer to prove their camera didn’t help.

The positioning, in one line

Not “a human, not a machine, made this” — that’s a trap. But “this verified human claims this, and will be known for it.”

Try the core idea

Everything is built on contributing under keys that are detached from your identity until you choose to link them. The same primitive powers files, posts, and code:

Upload anything, anchor it forever

Drop a file and it is stored permanently on Arweave, with an attestation on Base that binds the content hash to a derived key. The artifact outlives any platform.

Claim

Claim later: prove the upload was yours without re-uploading — the content hash already matches your derivation tree.