# Someone to be — condition 02 of Web 4

> The second condition of Web 4 is someone to be: an identity that carries standing — reputation, history, credentials, entitlements — across surfaces, instead of resetting at every login.

**Failure mode:** Identity without portability is a login.  
**Correction:** Identity did not crash. It failed quietly, by never becoming portable at all.  
**Supplied inside the group by:** Flashy ID  
**Canonical URL:** https://4ventures.vercel.app/thesis/someone-to-be

---

## What it means

An identity carrying standing across surfaces instead of resetting at every login.

## What happens without it

An identity that cannot leave the surface that issued it is not an identity. It is a login: useful to the operator, worthless to the person, and forgotten the moment they go somewhere else.

This is the condition that failed least dramatically and matters most. There was no identity crash because identity never got far enough to have one — every attempt was absorbed into a platform login and stopped being portable at the moment it became useful.

It is also the condition that agents make urgent. A workforce of software needs to prove what it is and who authorized it, to counterparties who have no relationship with it. That is an identity problem, and solving it for agents solves it for people as a side effect.

## What supplying it requires

1. An identifier the holder controls rather than one the platform issues
2. Standing that accumulates — reputation, history and credentials that travel with it
3. Verifiability by a counterparty who does not trust the issuer
4. Applicability to software: agents need identity for the same reasons people do

## On the definition of Web 4

The institutional definition of Web 4 is GDA Group’s published position. This studio applies it; it does not restate it. See https://gda.group/answers/what-is-web-4/