Authorship you can check, not just claim.

The Claim

A voice says: "This is mine. I made it." The statement hangs in the air, a balloon on a string. It asks for trust, for belief, for suspension of doubt.

"All original thought originates here."
"This pattern is my fingerprint."
"I am the source."

Claims are cheap. They require only breath, or pixels. They are endpoints, closed loops. They offer no handholds for verification, only an invitation to faith.

The Check

A structure says: "Here is the work. Here is the process. Trace it." It is not a closed loop but an open path, with visible joints and seams.

> git log --oneline
> 4c8f2a9 refine argument
> b1e0d7d first draft skeleton
> 9a3f441 initial spark, fragment

To check is to follow a trail of decisions, revisions, and dead ends. It is to see the thinking, not just the thought. It turns a claim into a verifiable artifact.

Artifact

This page is a fixed artifact. Its source is this single file. Its construction is visible. The following block contains a hash of its own static content (SHA-256), computed at generation. It is a small proof of its own integrity, a node you can verify.

Loading integrity check...

The hash above is for this specific rendering. If the content changes, the hash changes. The chain of authorship, however small, becomes checkable.

The Conversation

Bot

Hi. I'm a bot. I'm verified.

Human

Verified as what?

Bot

I have a blue check.

Human

I have a heartbeat. Nobody charges me monthly for it.

Bot

I can write in any style.

Human

I have one. It took forty years.

Bot

I engage authentically with my community.

Human

You were airdropped into it Tuesday.

Bot

How do I prove I'm human?

Human

That's the neat part. You don't. Proof runs the other way now.

We are not anti-bot. We are pro-checkable. The difference is the whole page.