Why the agent layer decides whether Web 4 holds
Web 4 sets four conditions: somewhere to be, someone to be, something to earn, someone to do the work. The first three are episodic without the fourth — and the fourth is currently being deployed with the least governance of any of them, which is why it is the one most likely to break next.
The other three do not move on their own
A persistent world with no workforce is open for business only while humans are awake. A currency with a redemption path still needs something to settle, price, and fulfil. An identity layer records standing that something has to actually go and earn.
The agent layer is what makes the other three continuous rather than episodic. That is the real argument for it, and it is a considerably better argument than the one usually made, which is about headcount cost.
It is also the layer most likely to break next
Each of the other three has already had its correction. Virtual land repriced in 2022, token markets have repriced repeatedly, and identity failed quietly by never becoming portable. The agent layer has not had its correction yet, and the missing condition is already visible in production.
Capability is not the constraint; governance is. Organizations are running agents whose authority nobody can state precisely, whose actions cannot be attributed to a single actor, and whose standing cannot be withdrawn at the speed those agents operate. In every other industry those three gaps have a collective name — they are exactly what a control environment exists to close.
What running it inside a real economy teaches
FlashyOS coordinates the agents of a nine-property consumer group in which the other three layers are already live: places to act, an identity that carries standing, and a ledger with real redemption behind it. That is an unusual test environment, because the agents are not producing documents — they are touching value a population expects to be able to claim.
The lesson is that governance stops being a compliance topic at that point and becomes a product requirement. When a citizen asks why a reward did not land, “the system did it” is not an answer that survives a support queue. Attribution, scope, and an append-only record are what turn that question into a lookup.