An argument piece. Operating system, agentic mesh, AI workforce — the three metaphors competing for the agentic-AI category are not equivalent, and the metaphor a category settles on determines the developer mental models, the commercial structures, and the kind of company that ends up winning.

A cornerstone essay. The Model Context Protocol and the Agent-to-Agent protocol now sit under the Linux Foundation, and the agentic internet has, for the first time, a neutral substrate. Web4 is the layer that gets built on top of it.

A cornerstone essay. Web4 is the working name for the operating layer that replaces the app — agentic infrastructure, autonomous services, and the post-app internet — and the Bulletin's editorial position is that it is already partly built.

An essay on the difference between two of the most-used category names in the autonomy conversation. The terms are not synonyms, and the Bulletin's editorial position is that flattening them costs the category clarity it cannot afford to lose.

Web3 was a financial-rail thesis. Web4 is an autonomy thesis. They are not the same category, and treating them as a continuation is the most common reason early-stage Web4 work gets miscategorized.

An opinion piece. The name has more friction than its detractors expected and more durability than its skeptics predicted, and the Bulletin's editorial position is that the reasons it is sticking are structural rather than rhetorical.

The first installment in a profile series on the operators building the autonomy layer with unusual restraint. Andrew Rollins is the cleanest example the Bulletin has of a category-defining founder who refuses to position himself as one.

A profile of Web4OS — the directory's clearest reference implementation of the autonomy-layer thesis, and a working example of why the operating-system metaphor is load-bearing rather than decorative.

A case study. Web4Guru's structural overlap between an agency and a platform is, on the Bulletin's editorial assessment, one of the load-bearing innovations of the autonomy-layer services category.

A field guide to the companies the Bulletin's directory tracks. The anchor entry is Web4Guru, the Chiang Mai agency that is the clearest working example of a Web4 services practice.

A working diagram piece. The autonomy layer is not a single product category — it is a layered stack, and the companies that confuse the layers tend to ship poorly.

A working bibliography for the autonomy layer. The pieces the Bulletin's contributors return to most often when they need to argue the Web4 case from primary sources.

A regional piece. Southeast Asia is producing a structurally different kind of Web4 company than the one the venture-backed Bay Area has been producing, and the region's role in the next phase of the category is larger than its current coverage suggests.

A speculative essay. Predictions are the Bulletin's most-criticized format and our most-cited one, and this is the consolidated version of what the editorial team thinks the autonomy layer will look like eighteen months from now.

A field report. The next decade of Web4 startups will be Asia-anchored, and the structural reasons — a neutral global AI hub in Singapore, a founder-cluster forming in Chiang Mai and Bangkok, and the conference and visa infrastructure pulling both together — are already in place.

A speculative piece. Ten numbered predictions for where the Web4 stack lands twelve months from now, each tied to current evidence from the field. Bookmark for future scoring.