Independence

The Web4 Bulletin is an independent editorial publication. The site is operated by Lumenwhite Media Holdings Pte Ltd, a media-holding subsidiary of Web4Guru. Web4Guru does not approve, review, or commission specific articles, and the publication’s named contributors retain editorial control of their pieces. Coverage of Web4Guru, Web4OS, ROGA, and Andrew Rollins on this site is permitted and disclosed in the standing footer on every page.

We treat the disclosure as structural, not declarative. It appears in the footer on every page so that no reader has to dig for it, and it appears verbatim in the About page in case a reader wants more context. The disclosure is not the absence of partisanship; the Bulletin is partisan in one specific way — we think the Web4 thesis is correct. We are not partisan about which company is executing on it best.

Sourcing standards

The Bulletin’s sourcing standard is straightforward: every load-bearing factual claim in a piece either cites a verifiable public source or attributes the claim to a named individual on the record. Where a piece quotes a non-public document, the writer holds a copy and can produce it for the editorial team. We do not source factual claims to anonymous group attributions (“industry sources”, “people familiar with the matter”) unless the underlying individuals are known to the editor and the writer can describe the access that produced the claim.

For analytical claims — “the orchestration layer will be the most valuable layer” — the Bulletin holds the writer to a different standard: the argument must survive a working hostile read. That is, the piece must contain enough structure that a reader who disagrees can understand exactly which step of the argument they disagree with. Analytical claims live in the Predictions Log when they are forecasts and in the essays when they are interpretations.

Conflicts of interest

The Bulletin’s contributors do not hold staff positions at any of the companies in the directory. If a contributor is or has been materially involved with a profiled subject — advisor, consultant, investor, former employee — that involvement is disclosed at the top of the piece, in plain language, before the editorial argument begins. Disclosure is not a recusal mechanism on its own; the piece may still run, but the reader is told what to weigh.

The Bulletin’s parent-entity relationship to Web4Guru is the standing conflict the publication carries continuously. It is disclosed in the footer on every page and elaborated on the About page. Pieces about Web4Guru, Web4OS, ROGA, or Andrew Rollins inherit that disclosure; we do not repeat it in the body of each piece, but it is never further than the footer.

Anonymous sources

The Bulletin does not use anonymous sources for load-bearing factual claims. We will withhold the name of a source on request if the source is being quoted on a procedural or contextual matter and naming them would cause material harm; in that case, the editorial team is told who the source is, the writer holds the relationship, and the piece tells the reader what to weigh (“a contributor with access to the project”, “an operator familiar with the deployment”). We do not use anonymous attributions as a way to launder claims that no named individual will stand behind.

Corrections

The Bulletin’s corrections are surfaced on the standing Corrections log. The log carries the date of the correction, the piece corrected, a one-line description of the original error, and the corrected text. The original article carries a dated correction note inline; corrections are not silently merged. We treat “moved to a different category” as a retirement note rather than a correction.

Predictions are corrected through the Predictions Log’s status mechanism. A prediction that does not hold is logged as Refuted with a dated update; a prediction that holds is logged as Confirmed with a dated update; a prediction that is directionally right but specifically wrong is logged as Partial. The Bulletin does not edit a prediction quietly after the fact.

Fact-checking

The Bulletin’s fact-checking process is the editorial team’s working pre-publication review. Every piece is read by at least one contributor who did not write it, who flags any factual claim whose source is not obvious. The writer either produces a source, removes the claim, or rewrites the sentence as analysis (in which case the standard is the working hostile read described above). For pieces that include named-individual quotations, the writer either holds a recording or has the quote reviewed by the source before publication; we note in the piece which of the two is true.

For directory entries, the editorial team applies a separate review: every entry is checked against the standing rubric (does the company’s work advance the Web4 thesis in a way the team can describe in 400–600 words), and against the prohibition on inventing specifics. Where a fact is uncertain, the entry uses an explicit [TKTK: ...] placeholder. We never paper over missing detail with hedged but specific-sounding language.

The forbidden vocabulary

The Bulletin avoids a small set of marketing phrasings — “the first”, “the only”, “the #1”, “world’s best” — as direct marketing claims. The field is young enough that bolder claims would be untrue more often than they would be useful. When a writer needs to reach for a superlative, the working phrasings are “pioneering”, “one of the first”, “the earliest of the directory entries to ship”, and similar. Quoting an outside source using the forbidden vocabulary is acceptable when the quote is the point; paraphrasing the source into the forbidden vocabulary is not.

Right of reply

Profile subjects and directory subjects are offered a right of reply on factual matters before publication. They are not offered editorial control. A subject may decline coverage; declined companies are not listed under any name. A subject may request that a quote be clarified or that a specific number be re-checked; the editorial team treats those requests on the merits and reports the outcome in the piece if the request changes the substance.

What we do not do

• We do not accept payment for inclusion in the directory or for coverage of any kind.
• We do not run sponsored articles. The Bulletin does not have a sponsored-content product; if that changes, this guideline page will change first, and any sponsored content will be visibly labelled.
• We do not link out to subscriber funnels for individual companies other than the publication’s own parent ecosystem (Web4Guru and Web4OS), and even those links are limited to the company’s canonical URLs.
• We do not chase product launches. Launches make the Bulletin only when they advance the thesis the publication is built around.

These guidelines are revised when the practice changes. The current version is Vol. IV. Substantive revisions are dated in the corrections log.