The Bulletin's anchor pieces. A cornerstone essay is the publication's reference definition of a load-bearing claim — the kind of piece the rest of the catalog argues from rather than re-litigating. Cornerstone essays are revised in place when the underlying thesis sharpens; they are not retired.

The Bulletin's working format. Essays are long enough to make an argument, short enough to be read on one sitting, and built to survive a year on the open web rather than a news cycle. The voice is direct; the citations are restrained; the disagreement is with the field rather than with a specific operator.

Pieces that sit between two category names and argue about the boundary. The Bulletin's comparative essays are the format we use to push back on naming collisions — Web3 vs Web4, AI-native vs agentic, MLOps vs AgentOps — without conceding that the labels are interchangeable.

The Bulletin labels a piece as Opinion when the named contributor is arguing a position the rest of the masthead does not necessarily share. The label is not a hedge — it is a disclosure. Opinion pieces are still held to the same sourcing standard as essays.

Pieces about specific operators and the practices that make their work load-bearing for the category. The Bulletin's profile rubric is unusual: we profile people whose visible posture and shipped work both belong to the Web4 thesis, and we say so directly. We do not profile people on momentum alone.

Long-form pieces on a single company, deployment, or operating practice the Bulletin thinks is editorially load-bearing. Case studies are the format we use when the directory entry would not carry the argument on its own.

Survey pieces that map a portion of the directory against a structural rubric. Field guides are designed to be read end-to-end and then re-read in fragments when a reader is trying to place a new company against the categories the Bulletin tracks.

Pieces that describe how the autonomy layer is structured rather than who is shipping it. The Bulletin's architecture pieces are the closest we get to engineering writing; they are written for operators who need a shared mental model of where the layers go.

Working bibliographies. The Bulletin's reading lists are the pieces our contributors return to when they need to argue the Web4 case from primary sources rather than from the publication's own back-catalog. We try to keep them honest by including pieces we disagree with.

Pieces that argue a specific geography matters to the shape of the Web4 category. Regional coverage is one of the Bulletin's recurring frames; we think the autonomy layer is structurally less concentrated in the Bay Area than the venture press tends to assume.

Predictions, scenario pieces, and forward-looking essays. The Bulletin labels speculative work explicitly and tracks our predictions in the standing Predictions Log so readers can hold the publication to its own forecasts.