Same As You.

The premise, in plain English

An autobiography written in public, in chapters, with every load-bearing fact — date, address, employer, diagnosis, termination, signature — hashed and signed on a public ledger as it goes in. The reader can verify the facts. The author cannot quietly delete them. The narrative shape is the author’s; the attested facts are not.

The model is closer to Wikipedia than to a memoir: editorial shape lives with the author within reason. Add context, set the order, choose the emphasis, write the prose. What you cannot do is silently retract a fact the chain has already witnessed. If the record is wrong, the correction is itself a signed entry — not a revision history hidden in a private draft.

The first life on the substrate is the author’s. That is the point of starting here.

The wedge

This is the anti-LinkedIn. LinkedIn is a profile of the parts of a life that look good in a recruiter’s search. Same As You is the opposite: a profile of a life that includes the parts that get a person quietly dropped — the bipolar diagnosis, the ADHD, the job that ended badly two days ago, the things a normal professional bio is structured to bury.

The audience is not the polished. The audience is the cancelled, the recovered, the survived, the diagnosed, the fired, the people whose actual record is more interesting than the sanitized one. The thesis is that a life made legible — including the failures — is more credible than a life curated for performance. The cryptographic layer is what makes the legibility load-bearing instead of confessional.

What ships when

v1 of the book ships when the SameAsYou protocol’s identity layer (DID-key + SD-JWT VC + the AIAP handshake) is wired to the writing pipeline — so that each chapter, on commit, signs its attested facts to the same substrate any other organization or person on the platform will use. The protocol came first; the book is the first case it carries.

Until then this page is the landing. Below is a waitlist if you want the first chapter when it’s signed.

Waitlist

One email, when the first signed chapter is live. No newsletter. No drip. The form endpoint is a placeholder until the protocol’s identity layer is wired through.